Integrate Liberty Reserve Payment gateway into a forex signals provider website. The forex website manages membership data using AMember. The website has monthly plans . The user should be signed up directly into the website upon purchase of a plan.
Liberty Reserve payment gateway did not support the creation of recurring plans. The various plans were created inside the merchant login. The product ids were mapped on the order form to the product ids created in AMember admin. The store account id, store name, were also passed as hidden fields in the order form.
The payment form did not have fields to capture the user information, hence before posting the data to the Liberty Reserve server, the name, email , mobile were captured on the order form itself and passed as hidden fields to the Payment URL.
The success and cancel URLs were defined, the Post Payment Notification URL was also defined in the merchant login. The data sent there was used to create the membership account of first time customers. In case of existing members their records were updated.
PS: Sometime in 2013 LR was shutdown after alleged charges of money laundering. A lot of genuine customers who had their money in their accounts became bankrupt overnight. As of now the domain name and assets are seized by the US Global Illicit financial team. The matter is being investigated.
Integrate Swreg Payment gateway into a forex signals provider website. The forex website manages membership data using AMember. The website has monthly plans and each plan will be of recurring type. The user should be signed up directly into the website upon purchase of a plan.
The recurring plans were created in the SWREG merchant login. The product ids were mapped with the product ids defined in the Amember admin.
The order form was created with the plan buttons and the various hidden fields for the payment form. On click of any plan the user was redirected to the SWREG server. The user information was collected along with his credit card information and user was redirected to a success or failure page depending on the status of the payment. The success and failure page URLs were defined in the merchant login.
The post payment notification data URL was also defined in the merchant login. The data was sent to this URL in XML format. A PHP parser script was implemented on this URL to read the payment data and create the user membership account. In case of recurring payments the users plan details were renewed. Various simulations tests were conducted in the sandbox account to test the various payment completion and cancelled scenarios.
Integrate Esellerate Payment gateway into a forex signals provider website. The forex website manages membership data using AMember. The website has monthly plans and each plan will be of recurring type. The user should be signed up directly into the website upon purchase of a plan.
The Esellerate Merchant login provided two keys for integrating the payment gateway. They were defined as hidden variables s and pc in the order form. The recurring plans for each product was created inside the merchant login. The product code was assigned as the product ids from Amember.
Each plan had a unique id which needed to be defined into a hidden variable on the order form _cartitem0.skurefnum.
The payment URL was defined as the form action and on click of the plan button the user was redirected to the Esellerate web server. The users profile information was captured in the page and on post payment the user was redirected to the Success or Cancel/Failure page. The URLs for these pages were defined in the merchant login.
The payment notification URL was also defined in the merchant login and post payment information was posted on that URL. The data returned was in XML format. The data was parsed by the XML parser program written in PHP and user was registered as a member in the Amember database.
In case of the recurring users the plan was renewed. There are also tools for posting mock data while development to the payment notification URL in the merchant login. These tools were used to test out the various cases of payments being made.
Some General Points
Esellerate as a payment gateway is very strict in taking action against websites which receive complains of selling ponzi schemes/plans, MLM ideas, abusive substances etc. They do not promote any of these activities and you should take each customer complaint very seriously else there is a good chance your account will be blacklisted. Do inquire with their support about the details of your business plans before you go ahead and purchase their gateway plans.
Integrate G2S Payment gateway into a forex signals provider website. The forex website manages membership data using Amember. The website has monthly plans and each plan will be of recurring type. The user should be signed up directly into the website upon purchase of a plan.
The details of the payment gateway were taken from the client. The G2S gateway provides the merchant id, merchant site id, secret key, payment URLs to redirect the user. The monthly recurring plans along with their frequency were defined in the G2S merchant login. Each plan has a product id and rebilling id. The product ids were mapped with the amember product plans.
On the Order page the POST buttons were created for each of the plans. When a particular plan was selected , the information associated with the plan was posted to the G2S payment URL. This URL also needed a valid checksum generated for security purpose which was composed of secret key, merchant key, rebilling product id, rebilling template id, time stamp. Upon successfully posting the data to the G2S server the user would see a payment form. On that form the personal information of the user and the credit card / banking information was captured and payment was completed.
G2S was provided with 3 URLs of the website. These were the
1) Success URL (called on post payment success)
2) Cancel / Failure URL (called on post payment failure)
3) Payment Notification URL (called on post payment)
The data captured from the Payment Notification URL was used for updating the records into the website database. The user profile information (name,email,mobile) was also captured from it and he was registered as a member with a random password, with the information sent on email and sms . In case the Post payment notification had information that the record was of type recurring then the database was updated accordingly. The logic was also built to capture each notification from the G2S server for every recurring payment made successfully or cancelled. Validations were done to ensure that while signup, the users email is unique in the system.
The client benefited with a huge number of sales of his monthly recurring plans by integrating G2S gateway with amember on his forex website.