Statistics: Posted by Raam Dev — January 11th, 2012, 11:51 am
Statistics: Posted by tokyoterri — January 10th, 2012, 4:45 am
Statistics: Posted by Raam Dev — January 4th, 2012, 6:06 pm
Statistics: Posted by tokyoterri — January 4th, 2012, 7:17 am
Statistics: Posted by Raam Dev — January 3rd, 2012, 5:18 pm
Statistics: Posted by tokyoterri — January 3rd, 2012, 7:16 am
Statistics: Posted by Jenine — December 28th, 2011, 4:30 pm
Statistics: Posted by Jason Caldwell — December 20th, 2011, 11:11 am
Statistics: Posted by jesseAe — December 20th, 2011, 3:29 am
Statistics: Posted by Cristián Lávaque — December 18th, 2011, 9:04 pm
Statistics: Posted by jesseAe — December 16th, 2011, 10:38 pm
Statistics: Posted by divagrrl27 — December 12th, 2011, 2:49 am
Statistics: Posted by Jason Caldwell — November 22nd, 2011, 2:42 am
Statistics: Posted by Cristián Lávaque — November 12th, 2011, 2:15 am
Statistics: Posted by Cristián Lávaque — October 12th, 2011, 8:10 pm
Statistics: Posted by LinkedInNinja — October 11th, 2011, 4:36 pm
Statistics: Posted by timjcarter — October 8th, 2011, 4:48 pm
Statistics: Posted by dskallman — August 31st, 2011, 10:17 am
IPN w/ Proxy Key ( optional, for 3rd-party integrations )
If you're using a 3rd-party application that needs to POST simulated IPN transactions to your s2Member installation, you can use this alternate IPN URL, which includes a Proxy Key. This encrypted Proxy Key verifies incoming data being received by s2Member's IPN processor. You can change [proxy-gateway] to whatever you like. The [proxy-gateway] value is required. It will be stored by s2Member as the Customer's Paid Subscr. Gateway. Your [proxy-gateway] value will also be reflected in s2Member's IPN log.
http://yoursite.com/?s2member_paypal_notify=1&s2member_paypal_proxy=[proxy-gateway]&s2member_paypal_proxy_verification=xxxxxxxxxxxxxxxxxxxxxxx
Any 3rd-party application that is sending IPN transactions to your s2Member installation, must ALWAYS include the custom POST variable, and that variable must always start with your installation domain ( i.e. custom=yoursite.com ). In addition, the item_number variable, must always match a format that s2Member looks for. Generally speaking, the item_number should be 1, 2, 3, or 4, indicating a specific s2Member Level #. However, s2Member also uses some advanced formats in this field. Just to be sure, we suggest creating a PayPal® Button with the s2Member Button Generator, and then taking a look at the Full Button Code to see how s2Member expects item_number to be formatted. Other than the aforementioned exceptions; all other POST variables should follow PayPal® standards. Please see: PayPal's IPN/PDT reference guide for full documentation.
Statistics: Posted by Jason Caldwell — April 12th, 2011, 10:48 pm