Chris Crabtree

So I tried to clarify further with PayPal, sending them this:

1. So it sounds to me like I should use the Express Checkout API for PayPal-using customers to do the recurring billing for the subscriptions. Correct?
2. Can I also use the Express Checkout API to process credit card-using customers as well?

Thanks!

PayPal’s response:

Those are good questions.

You would use the Payflow Gateway Version of Express checkout to create a billing agreement (see chapter 2 of the guide: https://cms.paypal.com/cms_content/US/en_US/files/developer/PFP_ExpressCheckout_PP.pdf). Then you can create a profile off the BAID (Billing Agreement ID)that is generated through that process to create the recurring profile in Payflow.

You cannot use the Express Checkout to create profiles with a credit card, they would have to have a PayPal account.

-Graham

I’m hoping this will be more helpful for you guys than it is to me, but thought I should pass it on. I’m not getting from this that there is anything I need to do as far as *configuring* s2Member or PayPal goes. But I’m happy to try things if you have suggestions. Hopefully looking through the logs will be the ultimate answer.

Thanks!

I sent the PCF as well just now. Thanks!

Actually, the funding sources were all over the map (visa credit, mastercard credit, discover credit, debit, checking, checking primary credit secondary, etc.), so I didn’t find any common denominators there.

However, PayPal finally responded and after a bit of back and forth, this is what they told me:

That is completely understandable. I do have to apologize though, I just realized how it was that you were attempting to set up these profiles with .

With Payflow you can only set up profiles with credit card transactions. You could use the recurring options through the standard Express Checkout APIs or use the Express Checkout through Payflow to create Billing Agreements, then bill accordingly. I think the options to do it through the standard APIs would be the easiest to develop.

The profiles that have been created will fail when PayPal is used as the funding source. The profiles can be created but the way Payflow references credit cards for the recurring portion will not work with PayPal as the funding source.

So does this mean s2Member should be doing something different, or does this point back to the workaround we discussed of simply removing the Payflow API parameters and letting s2Member fall back to the older APIs? Or something else entirely?

Thanks!

The server check script is a great idea. I ran it and it found that PHPMailer throws an exception: possible email delivery failure, and in fact, the email did not arrive, so that is definitely a problem although obviously it isn’t related to “Invoice has already been paid” or “User registration is not currently allowed” messages.

The only other issue was a notice that the WP_MEMORY_LIMIT was only 32M instead of the 64M.

So I asked WPEngine to help me correct these two, and also to turn off caching on the signup page. I think disabling the caching may help the real issues here, but we’ll see.

No users have accounts at this point on the site, so the already-logged-in scenario doesn’t exist, so we can safely rule problems related to that out of the picture.

Is there a way (outside of s2member) you know of with WordPress to “follow” a user’s path through the site so I can see that they arrive at the signup page, click to go to PayPal and then, sometime later perhaps, show back up on the registration page, proceed to login, etc.? Is there a plugin that will do this or would I have to set up Google Analytics or CrazyEgg or something to do this?

Thanks!