Using PayPal Saved Buttons
Posted: July 8th, 2011, 2:51 pmIs is possible/practical to use PayPal Saved Buttons with s2Member? That is, the button configuration (price, trial period, etc) are stored at PayPal. My site then only needs a short form which references the unique ID of the button.
This prevents fraud, because otherwise there are a bunch of hidden fields that users could manipulate to tell paypal what they want to pay. (Encrypted buttons are another attempt at preventing button modification fraud, but I have yet to get that to work (in the Sandbox)).
I thought I read about this somewhere in s2Member, but I cannot find the instructions. Initial investigation shows (thanks to your great logging) that I need to add a couple "Advanced" custom fields to the button: reply_url and custom. Or, I could probably just add these to the HTML form as hidden fields, augmenting the referenced button fields (or would PayPal reject that).
However, s2Member cannot recognize the customer of the resulting IPNs. It looks like s2Member also includes a bunch of other hidden fields, which identify the customer (and other stuff?) needed to modify users. My specific use case is subscription modification (Level 0 upgrade to Level 1).
Is there any good way to use saved (pre-configured) buttons, or is this just not advisable with s2Member?
This prevents fraud, because otherwise there are a bunch of hidden fields that users could manipulate to tell paypal what they want to pay. (Encrypted buttons are another attempt at preventing button modification fraud, but I have yet to get that to work (in the Sandbox)).
I thought I read about this somewhere in s2Member, but I cannot find the instructions. Initial investigation shows (thanks to your great logging) that I need to add a couple "Advanced" custom fields to the button: reply_url and custom. Or, I could probably just add these to the HTML form as hidden fields, augmenting the referenced button fields (or would PayPal reject that).
However, s2Member cannot recognize the customer of the resulting IPNs. It looks like s2Member also includes a bunch of other hidden fields, which identify the customer (and other stuff?) needed to modify users. My specific use case is subscription modification (Level 0 upgrade to Level 1).
Is there any good way to use saved (pre-configured) buttons, or is this just not advisable with s2Member?
