Jason (Lead Developer)

PayPal wrote…

Error 10422 has to do with the funding source that the buyer selected. For live transactions, I will suggest you contact PayPal customer support to verify why the system is preventing the buyer to use that funding source to make a payment.

Below are the numbers to contact customer support:

US/CA: 1-888-221-1161
UK: 08707 307 191
Australia: 1-800-073-263
Germany: 0180 500 66 27
Other: 1-402-935-2080

Here’s another related thread at PayPal developer support:
https://www.x.com/developers/paypal/forums/general-support/new-and-confused#answer-181193

@ Tony Schwartz

Exact same issue on your installation. Credit card transactions succeed, Express Checkout transactions fail with:

'TRXPNREF' => 'EXHPA1DA6C70',
'TRXRESPMSG' => 'Referral: 10422-The customer must return to PayPal to select new funding sources.',

Investigation continues on our end.

Thanks for the heads up on this thread.

Please send an IPN with txn_type=subscr_signup, just as you would for a new customer. To tell s2Member that this is an existing user of the site, please add the following two variables to your POST data in the IPN that you send to s2Member.

option_name1=upgrade
option_selection1=123

Where 123 is the existing user’s ID in WordPress.
http://codex.wordpress.org/Function_Reference/get_current_user_id

@ Mike Whitney

I just took a look at your s2Member installation, and I poked through your /s2member-logs/paypal-payflow-api.log file. I’m seeing the exact same issue on your installation. You have integrated PayPal Pro (Payflow Edition), and it appears that your account also has Recurring Billing service enabled, because like Chris Crabtree, credit card transactions ARE being processed properly on your site (indicating that Recurring Billing service IS enabled in your PayPal account). However, PayPal Express Checkout transactions on your installation (e.g. a credit card was NOT used – a PayPal account was used instead) are also resulting in the following error.

'TRXPNREF' => 'EQCP7C468C4F',
'TRXRESPMSG' => 'Referral: 10422-The customer must return to PayPal to select new funding sources.',

I think it’s a good idea for both of you to request PayPal assistance in this matter. Asking them to review some of the transactions (like the one I posted above – 'TRXPNREF' => 'EQCP7C468C4F'), so they can offer you some insight about why the funding source is being rejected in these specific cases.

That being said, since both of you are reporting the same issue, I think it would be irresponsible for us not to investigate this further on our end as well. With your permission, I’d like the opportunity to perform some test transactions against your installation, in the hopes of finding a resolution.

Please reply back and give me the OK on this. Also, please keep me updated about any replies that either of you get from PayPal in this matter. We will be sure to investigate them extensively on our end as well.

Regarding your comment about DPRP…

BTW – Here’s what happens when I try and enable recurring payments:
Your version of Website Payments Pro is not compatible with the Direct Payment Recurring Payments feature.
Now PayPal told me that in order for this feature to work you have to apply to get reference transactions enabled which they would not approve me for.

From my own communication with PayPal, it is my understanding that DPRP is NOT possible with a PayPal Pro (Payflow Edition) account (not possible due to technical issues). Instead, Recurring Billing service works together with the Payflow portion of your account. This is why s2Member Pro MUST integrate it’s recurring billing routines with the Payflow portion of your PayPal account. So it’s not a surprise to me that you heard this from PayPal. If you have a PayPal Pro (Payflow Edition) account with Recurring Billing service enabled, you just need to tell s2Member by filling out the Payflow portion of your s2Member configuration. This way s2Member will use the Payflow API to facilitate recurring billing, instead of trying to use DPRP under the normal PayPal Pro API.

Personally I think it’s Paypal’s issue not understanding their products but I cannot get anybody to figure it out.

While I’m not convinced yet, that this issue is entirely PayPal’s fault (my investigation on this will continue), I do agree with you. PayPal already had several different types of service (which brought with it some confusion for everyone). Then, a few months ago they started issuing PayPal Pro (Payflow Edition) accounts on a regular basis, they renamed some of their other services, and this just further confused everyone even more. Including some confusion on the part of PayPal customer support. In my experience with PayPal, it has been very difficult for them to offer site owners assistance, because there is confusion on their part about which API is being used, and how a particular API is being used (because each of their APIs provide several options). These issues are VERY technical by nature, and PayPal support seems to have trouble keeping up with their own products at times. Some experiences are different from others. It really just comes down to WHO you speak with over there, and how high up the chain that person is. The PayPal MTS agents seem to have the most knowledge. https://www.x.com/developers/paypal/forums

Regarding this comment…

However, I still contend that s2Member is not using the standard Express Checkout API when Payflow Account Details are filled out. Why?

Yes, I believe you are correct to a certain extent. Or, perhaps there is some confusion here about which API s2Member Pro is actually designed to work with on the PayPal end of things. Based on the response you received from PayPal support, I think that’s probably the case. Confusion on their part, that is.

In s2Member Pro, if you leave the Payflow configuration fields empty in your Dashboard, s2Member Pro will integrate with the PayPal Website Payments Pro API (e.g. nothing special here), you just need a PayPal Pro account to integrate with s2Member Pro.

If you intend to charge on a recurring basis, you will need to ask PayPal to add DPRP to your PayPal Pro account. That is their Recurring Billing service for PayPal Pro accounts; which is what makes it possible for s2Member Pro to integrate recurring payments made possible by s2Member Pro, with your PayPal Pro account. This is simply a matter of asking PayPal to add the Recurring Billing service to your existing PayPal Pro account. This will cost you an additional $30/month, for a total of $60/mo.

End of story, you’re all done.

However…

There are some newer PayPal Pro accounts (it’s still a slight mystery to us about who exactly gets these by default, or perhaps by request – still not sure… PayPal support has been rather vague about this with us).

Anyway… some site owners (like YOU for instance), will NOT have the normal PayPal Pro account flavor.

Instead, you (like many others), have a PayPal Pro account operating under the Payflow Edition. This is NOT to be confused with a pure Payflow Pro account, that’s NOT the same thing. What you have is a “PayPal Pro (Payflow Edition)” account, which is a mixture of both the PayPal Pro and Payflow APIs.

Under this type of integration, s2Member Pro will use the normal PayPal Pro API portion of your account, for everything except Recurring Billing transactions. Under a PayPal Pro (Payflow edition) account, s2Member MUST integrate Recurring Billing with the Payflow API portion of your account. This is achieved by filling out the Payflow configuration details for s2Member to use, as seen in your Dashboard with s2Member Pro installed.

In addition, you will still need to ask PayPal to enable Recurring Billing service for your PayPal Pro (Payflow Edition) account. Everything is the same with your account, except instead of s2Member Pro using the normal PayPal Pro API for Recurring Billing, it will use the Payflow API portion of your account. It’s a behind-the-scene communication change, from one API to another.

Therefore, you SHOULD fill out the Payflow details in your s2Member configuration. Based on your log files, it appears that your PayPal account has already had Recurring Billing service enabled. So you’re already paying for that, and it’s working properly when you have the Payflow details filled in for s2Member.

That is, it’s working when a credit card is used, but it’s NOT working for you when a PayPal account is used, which is indicated by your log files. So the problem here comes back to the use of PayPal Express Checkout under the Payflow API, which is what s2Member is using; because the transactions you’re attempting to process are implementing a Recurring Profile, and not just a one-time transaction.

The response that you received from PayPal support…

The reason it is not working is that they are leaving out a step. The Profile cannot be created without getting a BAID (Billing Agreement ID). This is done after the ‘ACTION = G’ step. To finalize the Express Checkout transaction you would either do an ‘ACTION=D’ to complete with a payment in addition to setting up the profile or ‘ACTION=X’ if you are only setting up a profile. Once the BAID is created you can then run the call to set up the Profile. If you try to do that without finalizing the Express checkout process and getting that BAID it will fail every time.

This is incorrect. I would ask you to clarify for them that s2Member Pro is NOT using Merchant Initiated Billing. s2Member Pro Forms are integrating with the Payflow API via Express Checkout for a BILLINGTYPE=RecurringPayments, which does NOT require a BAID to be processed at all. Not to achieve what s2Member needs to.

What this support rep is referring to (regarding a BAID), is a different type of transaction, whereby s2Member would be responsible for maintaining the future billing schedule. s2Member does NOT integrate this way. s2Member creates a configurable Recurring Profile within your PayPal Pro (Payflow Edition) account, which you and s2Member can configure and monitor now and in the future. The future billing cycle is maintained by PayPal, and NOT by the s2Member software. Thus, a BAID is not necessary.

Resolving the issue with Express Checkout and your Payflow API…

I’m seeing errors in your paypal-payflow-api.log file with details like this:

'TRXPNREF' => 'ETJPA1763B30',
  'TRXRESPMSG' => 'Referral: 10422-The customer must return to PayPal to select new funding sources.',

This suggests one of the following to me:

1. Your PayPal account needs to be reviewed by PayPal support.
2. Your customer attempted to use a PayPal account via Express Checkout, funded by a checking account; but your PayPal account is configured NOT to accept checks?
3. Your customer attempted to use a PayPal account via Express Checkout, funded by GiroPay; but your PayPal account is configured NOT to accept GiroPay?

Or perhaps there is another issue that none of us are seeing. PayPal could help point us all in the right direction on this. Please submit this back to PayPal for further review. I would ask them to look at this specific transaction ('TRXPNREF' => 'ETJPA1763B30') and find out why the funding source was declined in this instance. That might help all of us find a resolution for you quicker.

Related articles:
https://www.x.com/developers/paypal/forums/paypal-sandbox/directpayment-how-i-know-if-client-have-enough-fund#answer-78900
https://www.x.com/developers/paypal/forums/general-support/new-and-confused#answer-181204
http://www.s2member.com/forums/topic/urgent-error-36-transaction-failed/

Documentation snippet regarding Merchant Initiated Billing:

Thanks for the follow-up.

This would most likely fall under what we consider to be “custom coding”. However, you might take a quick look at s2Member’s built-in Registration Notification to see if that helps you further. See: Dashboard -› s2Member® -› API / Notifications -› Registration Notifications

If not, you could certainly use one of s2Member’s MANY built-in hooks/filters to accomplish this.

Here is a quick example that serves to point you in the right direction.
Create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
( these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins )

http://www.s2member.com/codex/stable/overview-summary/#src_doc_overview_description
See also: http://codex.wordpress.org/Function_Reference/update_user_option

Thanks for the heads up on this thread.

@ Joseph Sellers

That’s the first time we’ve seen that error come back. According to the PP docs, it indicates there is a mismatch between the original description used to setup this PayPal Express Checkout transaction, and the subsequent API call which is represented by the log entry you posted here.

While we continue to investigate this, please post the previous log entry (e.g. the one before this one). It should be a TRXTYPE=S, ACTION=S and also should have this number 1354482839 in the PROFILENAME.

I’d like to see what the original value of the description was set to on your installation, so we can compare it during testing on our end. With your help we should have a resolution for you soon.

Is there a way to make the variables passed back from CB global or at least available so that I can auto-populate on the register page?

In the case of a “Buy Now” transaction via ClickBank (e.g. no recurring fees), the value of ctransreceipt from ClickBank, is stored by s2Member Pro as the Paid Subscr. ID value, and is tied directly to a customer’s profile in your Dashboard. Please check the Users menu in your Dashboard, for a User you’d like to see information for.

This Paid Subscr. ID (i.e. the ClickBank Receipt Number), is the only financial information that s2Member Pro needs to make it’s integration with the ClickBank return-page communication and IPN communication function properly; and it allows s2Member to remain more secure, since additional financial details are not being stored on the server side, but left in storage with your payment gateway.

In cases where there ARE recurring fees, s2Member Pro generates it’s own Paid Subscr. ID, which it sends to ClickBank, and ClickBank uses the Paid Subscr. ID generated by s2Member Pro in all future communication with s2Member Pro. Therefore, in the case of recurring subscriptions via ClickBank, the ClickBank receipt identifies only a specific transaction among many that may occur over the life a subscription. The value that remains constant throughout all future payments is the Paid Subscr. ID, which was originally generated by s2Member Pro, and is stored in a customer’s account profile, visible from the administrative Dashboard for WP.

If you’d like to collect the ClickBank Receipt for either one-time or recurring payments, you may connect to s2Member’s API Notification for payments, which is processed ANY time a payment occurs on the ClickBank side of things (including initial and recurring payments). In s2Member’s API Notification for payments, the ClickBank receipt value is obtained with the s2Member Replacement Code: %%txn_id%%

With s2Member’s API Notifications, you can collect and process your own custom code, storing these values, or use them for any other purpose you see fit. Some experience with PHP is required to integrate with s2Member’s API Notifications. See: Dashboard -› s2Member® -› API / Notifications -› Payment Notifications

I replied to this in your other thread:
http://www.s2member.com/forums/topic/subscription-with-paypal-ipn-w-proxy/#post-30421