About: Marvin Cummings

Client URL: http://getfit-atlanta.com/membership/?_s2member_seeking%5Btype%5D=page&_s2member_seeking%5Bpage%5D=21&_s2member_seeking%5B_uri%5D=L3JlZ2lzdHJhdGlvbi8%3D&_s2member_req%5Btype%5D=level&_s2member_req%5Blevel%5D=0&_s2member_res%5Btype%5D=page&s2member_seeking=page-21&s2member_level_req=0

Here’s an example from one of the forms I’m using:

[s2Member-Pro-PayPal-Form level="2" ccaps="" desc="New Run/Walk Members / Description and pricing details here." ps="paypal" lc="" cc="USD" dg="0" ns="1" custom="mydomain.com" ta="0" tp="0" tt="D" ra="0.01" rp="1" rt="M" rr="1" rrt="" rra="2" accept="paypal,visa,mastercard,amex,discover,maestro,solo" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]

I know the client received an email from PayPal stating PDT was enabled but I’ll contact them to confirm if both DPRP and PayPal Flow is active on the account? So there’s nothing else I need to configure within s2 on the client site?

tia

Under PayPal Options I originally had the API Username, Password, and Signature. I’ve since removed it after speaking with PayPal. The only thing remaining is the email address and for the behavior I have Real-Time / Direct Pay. It looks like I have to have this info. Do I need to add the API info for this PayPal Standard account?

I do have pro-forms created for each of the paypal buttons, totaling six (6). The forms are necessary because they allow registration information to be entered and waivers accepted before payments are made. Three of the forms are for recurring memberships and three are non-recurring. Are you saying that because the client has a PayPal Standard account she must use buttons and can’t use the pro forms? If this is so then she’ll have to be instructed to consider upgrading to PayPal Pro in order to use the forms? Using the buttons without the ability to have a form attached would defeat the purpose for this particular request.

Any responses appreciated.