Testing the Payment Process
The Payment Form integration should be tested in the Sandbox before going live.
The Sandbox provides full functionality but it only emulates processing, no actual bank transactions are made.
When using PaySuper JS SDK ensure that:
- Handlers for the events are displayed properly.
- The PaySuper object is created with all required parameters or a token.
If you’re using the PaySuper API in your server-side code then ensure that:
- All API errors are handled accurately.
- Webhooks contains properly URL configured in the Functional URL section on the Project webhooks page.
Test card numbers
To test a bank card payment in the Sandbox enter arbitrary expiry date (the format is MM/YY), a Secure code (CVC/CVV, the format is 3 digits) and a cardholder name (the format is first name last name).
You can also specify incorrect details (card number, expiration date, or CVV) to generate an error.
You will be redirected to the Sandbox page to select the desired results for success or failure. After you click the result button the current page will be closed and you will be redirected to the Checkout Form to view the purchase status.
Note, that when Merchant chooses to fail the authentication, then the payment is always declined, no matter what PAN has been used.
Use any of the following test card numbers:
Note that the
Authorizedcards must only be used to test the antifraud system reaction with a compulsory transfer payment to preauthorization.
3-D Secure test cards
3-D Secure is emulated with a page that doesn’t require any passwords and shows two buttons instead. One button is for a successful authentication, another is for a failed authentication.
4000 0000 0000 0002Click to copy
5555 5555 5555 4444Click to copy
4000 0000 0000 0044Click to copy
Non 3-D Secure test cards
4000 0000 0000 0077Click to copy
5555 5555 5555 4477Click to copy
4000 0000 0000 0051Click to copy
You can choose a fixed set of currencies which will be actual for all products in your project on the Project settings page.
The full list of currencies that are supported for testing:
|Code||Country and Currency|
|USD||United States Dollar|
|EUR||Euro Member Countries|
|GBP||United Kingdom Pound|
|VND||Viet Nam Dong|
|KRW||Korea (South) Won|
|NZD||New Zealand Dollar|
|CNY||China Yuan Renminbi|
|Code||Country and Currency|
|ZAR||South Africa Rand|
|HKD||Hong Kong Dollar|
|TWD||Taiwan New Dollar|
|SAR||Saudi Arabia Riyal|
|ILS||New Israeli Sheqel|
|CRC||Costa Rica Colon|
|CZK||Czech Republic Koruna|
Configure Webhooks for your Project in PaySuper Dashboard and handle them on your server.
Testing the webhook notifications:
Before going live, check that your server responds with status code 200 and empty body to webhook notifications to acknowledge about success (or any status code from 400 for failure) for all types of the order:
- Go to Project Webhooks page.
- Under Webhook Settings section choose the tab with the order’s type: Simple checkout, Virtual currency, Virtual items, Game keys.
- Enter the payment order data from your project: customer ID, transaction ID, virtual item ID (if any). You can test success and failure responses using a valid data or non-existing values.
- Click Test and view the temporary logs below with the PaySuper notification and your server response.
Learn about the different ways you can customize your Checkout.
You can inspect this checklist before going live to ensure you’ve implemented all the significant setup steps.
Our salespeople are pleasant and friendly. Leave your contact details, and we’ll be back to you in no time.
We are always happy to help with a code, improve a guide or consider a feature.
The PaySuper Checkout Form, the JS SDK and even the server are available as a source code on our GitHub. You’re welcome to explore the code and help us make PaySuper even better.