Paymentwall Integration Checklist

Last updated on 2012/08/22 Paymentwall Widget Call Checklist: Pingback Processing Checklist: a) Virtual Currency API b) Digital Goods / Subscriptions / One-Time Payments API

Paymentwall Widget Call Checklist:

1. Place the widget on a test page of your website. 2. Log into your Paymentwall developer account - this will allow you to load the widget until application is approved. 3. Go to the test page where the widget is placed. 4. Make sure that the widget is placed properly: a. its not overlapped by any elements of the site b. its fully visible and accessible to the user 5. Make sure, that you replaced [USER_ID] placeholder in uid parameter of the widget with an identifier of the end-user who is viewing the widget in your system. Heres an example: when youre logged into a website like Gmail.com, it displays you your email address in the top right corner. Each user who is logged into Gmail sees his own email address. In a similar way, [USER_ID] needs to be replaced on your website with an identifier of the end-user (id, username or email) who is currently viewing the widget. Make sure, that: a. the same end-user comes with the same value of uid parameter whenever he visits the widget b. each user comes under unique uid parameter 6. If you need to pass any additional parameters such as order id - please let us know by emailing devsuppo rt@paymentwall.com. 7. If email address of the user is used as the uid and upon receiving pingbacks the product details will be delivered only to the email address, the email address has to be verified by sending a confirmation email to the user.

Pingback Processing Checklist:

1. Make sure that the pingback URL / email address is set up correctly in Pingback section of the application. 2. Use the Test Pingback tool from the Pingback section: a) Virtual Currency API

Parameter

Platform User ID uid parameter from the widget call uid parameter from the widget call

Currency Amount 10

Type

Reference

Chargeback Reason (type=2) -

Test 1

bt1111

Test 2

-1

bt1111

Test 3

uid parameter from the widget call

bt2222

Result

balance of the user should be 14 credits (10 + (-1) + 5 = 14). The pingbacks should be shown as successful in the Test Pingback tool.

b) Digital Goods / Subscriptions / One-Time Payments API

Parameter

Platform User ID

Product SKU ID

Product Length (if applicable )

Product Period (if applicable )

Type

Reference

Chargeba ck Reason (if type=2)

Test 1 Test 2 Test 3 uid parame ter from the widget call From Products section of your application

0 0 2

bt1111 bt2222 bt1111

Result Wrong result

the user should receive 2 products and then got 1 cancelled. The pingbacks should be shown as successful in the Test Pingback tool. both products got cancelled

Please feel free to contact devsupport@paymentwall.com if you have any questions. We are here to help.