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 Authorized cards 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.

Confirmed

4000 0000 0000 0002

Click to copy

Declined

5555 5555 5555 4444

Click to copy

Authorized

4000 0000 0000 0044

Click to copy

Non 3-D Secure test cards

Confirmed

4000 0000 0000 0077

Click to copy

Declined

5555 5555 5555 4477

Click to copy

Authorized

4000 0000 0000 0051

Click to copy

Currencies

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:

Webhooks

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:

1. Go to Project Webhooks page.
2. Under Webhook Settings section choose the tab with the order’s type: Simple checkout, Virtual currency, Virtual items, Game keys.
3. 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.
4. Click Test and view the temporary logs below with the PaySuper notification and your server response.

Next steps

After the payment

After a successful payment, you have to fulfil the customer’s purchase. You can use webhooks or the Transactions to accomplish the purchase.

Customizing the Checkout

Learn about the different ways you can customize your Checkout.

Going live checklist

You can inspect this checklist before going live to ensure you’ve implemented all the significant setup steps.

Questions?

Not a developer?