Jason (Lead Developer)

@ Joseph Sellers

The test site you mentioned in this post:
http://www.s2member.com/forums/topic/error-generic-processor-error-11581/#post-32249

It doesn’t seem to match up with the site you sent us access to privately? The site that I just reviewed privately was running a custom theme, 24 active plugins, and it does not have the Payflow patch installed? Just checking to see if we missed something from you?

Please submit a Dashboard/FTP login for the test install you setup.
See: s2Member® » Private Contact Form

Thanks for the heads up on this thread.

@ Mary Sullivan

Thanks for reporting this.

I just finished reviewing the test site that you sent over to us privately.

I tested your site in Chrome (no JavaScript errors).
I tested your site in Firefox v12 (no JavaScript errors).
I tested your site in IE9 (no JavaScript errors).

I was unable to reproduce the error that you reported under IE9 as described in the original topic in this thread. This test site seems to be functioning properly. However, I did receive the following error from the PayPal API upon clicking the PayPal button in all browsers.

Error #10002. Security error. Security header is not valid.

This indicates that your installation of s2Member is not properly configured in this section (e.g. your PayPal API Credentials need to be entered properly, matching those provided to you by PayPal). Please see: Dashboard -› s2Member® -› PayPal® Options -› Account Details

I had a colleague test it and he says it did work for him (he has IE 9) but I can’t duplicate that no matter how long I wait. It’s like the button is dead.

It seems to be working fine from my end as well. If problems persist during your own testing, I would start looking at your installation of IE9. Do you have any plugins/add-ons installed together with IE9? If so, one of those IE9 add-ons could be causing JavaScript errors for you, which would be user-specific (i.e. only you are having this problem)?

Thank you VERY much for the follow-ups here.

@ Joseph Sellers

Interesting response from PayPal. All of the characters in that snippet are in ASCII. What character encoding have you configured for your WordPress installation? UTF-8 (the default)? Or something else?

See also: http://www.robelle.com/smugbook/ascii.html

Please send me a Dashboard login to this test installation so we can run diagnostics for you.
Please use: s2Member® » Private Contact Form

This sounds to me like a character encoding issue, but let me have a look at your installation to be sure please.

Hi there. Thanks for the heads up on this thread.

Regarding payment gateway integrations. I’m sorry but we do not work directly in partnership with any specific payment gateways. s2Member currently integrates with PayPal, PayPal Pro, Authorize.Net, ccBill, ClickBank, and Google Checkout. While we have every intention of integrating with additional payment gateways in the future, we will be adding support for these additional payment gateways on a schedule of our choosing.

If you would like to integrate your payment gateway with the current release of s2Member (on your own, or with help from a WP developer), please consult the documentation made available in the s2Member Dashboard under:

Dashboard -› s2Member® -› PayPal® Options -› PayPal® IPN Integration
› IPN w/ Proxy Key ( optional, for 3rd-party integrations )

Any payment gateway integrated with s2Member will require that payment gateway to POST simulated PayPal IPN’s back to s2Member. The instructions on how to accomplish this have been provided in the aforementioned section of your Dashboard. Please let us know if you have any questions about this.

Thanks for the heads up on this thread.

s2Member Pro creates an ARB (Automated Recurring Billing profile) in it’s integration with Authorize.Net. Once the billing amounts are established and agreed to by your customer, Authorize.Net does not allow these values to change. See: https://support.authorize.net/authkb/index?page=content&id=A507&actp=search&viewlocale=en_US&searchid=1353491994827

See also: https://support.authorize.net/authkb/index?page=content&id=A660&actp=search&viewlocale=en_US&searchid=1353491994827

That being said, you are certainly capable of processing transactions manually through the Virtual Terminal provided to you by Authorize.Net. It’s also possible to charge a credit card programatically through the Authorize.Net AIM API. Here are two possible scenarios that I can see for you.

1. You could have an s2Member Pro form to collect the customer’s credit card information each time you want to receive funds. However, based on your explanation, I don’t see this fitting the business concept you’ve presented.

What you’re trying to accomplish is geared more toward Automated Recurring Billing. In other words, you’re looking for billing to occur automatically, and not require the customer to come back to your site each time you need to be paid. While s2Member Pro does integrate fully with Authorize.Net’s ARB service, the $ amount that is charged automatically, is established when the customer agrees you pay you (at checkout), and cannot be changed each month unless the old ARB is terminated and a new one is created by you manually, or by your customer – at a different amount.

2. Regarding Virtual Terminal use, or one-time charges submitted through the Authorize.Net AIM API.

In the case of a manual transaction where you charge the customer X number of dollars using the Virtual Terminal provided by Authorize.Net, you will need the customer’s credit card number and expiration date (along with their permission of course). The same goes for any API driven routine (you still need the credit card details on file, stored in a database on-site).

For security purposes, s2Member Pro does NOT store any of your customer’s credit card information on-site. The customer’s credit card details DO pass through an s2Member Pro Form, and over to Authorize.Net. However, the Authorize.Net ARB service stores the customer’s credit card details securely at Authorize.Net, and s2Member does NOT store them in your WP database; because from this point on, future billing occurs on the Authorize.Net side of things, and is not controlled by your WP installation. It doesn’t need to be.

In short, this is NOT possible with a default installation of s2Member Pro. If you wanted to accomplish this, you would need someone to assist you in writing custom code that collects and stores credit card details submitted by your customer, and a custom routine that would later come back and charge specific amounts that you set.

Reference article: Automated Recurring Billing service from Authorize.Net.

Regarding JW Player v6

There is nothing in s2Member that would prevent compatibility with JW Player v6. However, it will require you to change the way you integrate s2Member with JW Player (changes in the code snippet that you use).

We will see about adding code samples into the next maintenance release for JW Player v6. Until then, here is a quick example that should help you out. This example assumes that your /jwplayer/ directory contains the files from JW Player v6 instead of v5.

<?php
// Configuration.
$s2_jw_config&#91;"jwplayer"&#93; = "/jwplayer/"; // Relative URL path to JW Player files directory.
$s2_jw_config&#91;"mp4_video_file_name"&#93; = "video.mp4"; // Name of your MP4 test file.
// Don't edit anything else below unless you know what you're doing.
?>

<div id="jw-container">JW Player® appears here.</div>
<script type="text/javascript" src="<?php echo $s2_jw_config&#91;"jwplayer"&#93;; ?>jwplayer.js"></script>

<?php /* A direct URL to the RTMP source; counting the file against the current User in real-time. */
$cfg = array ("file_download" => $s2_jw_config["mp4_video_file_name"], "url_to_storage_source" => true, "count_against_user" => true); ?>

<?php /* API Function `s2member_file_download_url()` returns false if access is denied to the current User. */
if (($mp4 = s2member_file_download_url ($cfg, "get-streamer-array"))) { ?>

    <script type="text/javascript">
        jwplayer("jw-container").setup(
                {playlist:[
                        {sources:
                                [
                                    {type: "rtmp", file: "<?php echo $mp4&#91;"streamer"&#93;; ?>/<?php echo $mp4&#91;"file"&#93;; ?>"},
                                    {type: "mp4", file: "<?php echo $mp4&#91;"url"&#93;; ?>"}
                                ],
        /* Set video dimensions. */ width: 480, height: 270
                        }
                ]});
    </script>

<?php } else /* Access is denied to the current User. */ { ?>
    Sorry, you do NOT have access to this file.
<?php } ?>

Thanks for the follow-ups here.

Thanks for your patience. Our investigation has come to an end on this report. Unfortunately we’ve been unable to reproduce this issue in our lab after the patch we posted previously was applied. However, we did find another issue reported in a separate thread related to PayPal Express Checkout under the Payflow API, which has been fixed in the development copy, and will be included as part of the next maintenance release.

Related thread where patch was posted:
http://www.s2member.com/forums/topic/paypal-error-36-transaction-failed/page/2/#post-31490

Suggestions…

You can try applying the patch that we posted here:
http://www.s2member.com/forums/topic/paypal-error-36-transaction-failed/page/2/#post-31505

Or you can wait for the next maintenance release (coming in the next day or two). If the problem continues after the next maintenance release, please update this thread and we will re-open this investigation for you at that time. Also, please report back about what Cristian mentioned. Have you been able to reproduce this issue on a clean installation of WordPress running only the default theme and no other plugins in a test environment?

Thanks for the heads up on this thread.

Regarding coupon code integration with iDevAffiliate. I became aware recently that iDevAffiliate has brought forth a new feature in v7 that can accomplish this for you. However, s2Member is NOT yet integrated with this feature.

That being said, even before iDevAffiliate added this new feature, s2Member already supported this functionality through a slightly different method of integration with iDevAffiliate. So… while you’re awaiting a release of s2Member that supports the iDevAffiliate 7 protocol for this, you’re welcome to integrate this functionality with s2Member alone, following the instructions presented in this section of your Dashboard.

@ Mike Whitney

Thank you.

A test transaction has been performed on your live site against the PATCHED version. In my test, a monthly recurring subscription to your site was paid for via PayPal Express Checkout and the Payflow API. The test was successful, and the results are recorded in the log file: /s2member-logs/paypal-payflow-api.log

Please refer to my earlier post and let me know if you have any further trouble.
http://www.s2member.com/forums/topic/paypal-error-36-transaction-failed/page/3/#post-31638

@ Chris Crabtree

A test transaction has been performed on your live site against the PATCHED version. In my test, a monthly recurring subscription to your site was paid for via PayPal Express Checkout and the Payflow API. The test was successful, and the results are recorded in the log file: /s2member-logs/paypal-payflow-api.log

@ Tony Schwartz

A test transaction has been performed on your live site against the PATCHED version. In my test, a monthly recurring subscription to your site was paid for via PayPal Express Checkout and the Payflow API. The test was successful, and the results are recorded in the log file: /s2member-logs/paypal-payflow-api.log

@ Mike Whitney

I was unable to run a test transaction on your site today. The WP Dashboard login that I have for your site is no longer functional. If you’d like us to run a test transaction on your site, please submit a new Dashboard login for me here: s2Member® » Private Contact Form

Regarding OPTIONALTRX.

My test transactions were submitted with OPTIONALTRX=S in the final API call, and in agreement with the underlying API documentation, this is being submitted correctly. It’s a Sale amount, and OPTIONALTRX should be set to S, as it is being set by s2Member Pro. No issue here that I’m aware of.