I’m looking into adding 2CO as a payment option for a digital app that sells advertising, but I’m a bit unclear on a few things:
1.) There seem to be 2 parameter sets available when passing info to the checkout – 3rd party (x_login) vs proprietary (sid). Is it ok to use either, or is there a particular one I should look to use?
2.) The knowledgebase indicates that information about the product must be passed (eg. c_prod parameter). Do these parameters have to match products setup in the 2CO account area, or can they be created on-the-fly from my app’s internal settings?
3.) If the parameter “x_Receipt_Link_URL” is set when sending the user to the checkout, is the user then redirected back to that url along with the notification data, or can I set the user to go to one page, and the data to go to another?
4.) I couldn’t seem to find much info on the INS feature that allows recurring billing notification, and so I’m unclear on how it differs from the normal callback procedure when setting up an integration, other than the user needing to opt-in to it from their account?
Many thanks in advance for your help!
3 Comments »
+0
-0
2Checkout supports 3 different parameter sets: Plug and Play (the set used with our built-in systems), Third Party Cart and Authorize.net (the sets used by software designed for our purchase page). Any of these parameter sets can be used as long as they are not mixed. However, if your digital app will be offering recurring products only our Plug and Play Parameter set can be used.
If your application uses our one of our Third Party Cart parameter sets the Product Identification parameters can be used to pass the product information on the fly. If the Plug and Play parameter set is used the products must be created in your 2Checkout account prior to passing the product_id into the purchase routine.
The customer and sale parameters are returned to your approved url at the end of each sale. If you don’t want to send the customer to your script you can send the customer to the approved url and use the INS order_create POST to populate your database.
The parameters sent back on INS messages differ from those sent on the initial order post back to your approved url. Please review the INS documentation for a full listing of the parameters that are passed on each INS message.
As always please feel free to submit a support ticket for further integration support.
+0
-0
For the demo, does the payment notification work the same way as in the case of the live system ?
I ask this because i completed two transactions, and have not yet received any notifications to the URL i have specified for the postback notiification.
How much time does it usually take for a notification of successful payment ?
Thanks!
+0
-0
saurab,
INS notifications aren’t sent for orders placed in demo mode.
You may send test posts to the url’s that you have set up in the Instant Notifications area by clicking the Notifications tab, and then the Test sub tab. All test notifications will post the same values to the url they are sent to regardless of the Message Type selected on the test tab. Please review this article for more information on INS features.
Generally, notifications for a new sale will be received within a few minutes of a successful sale.