Before your solution can go live, your account manager will have to verify your transaction flow and receipts in order to ensure that everything complies with the rules and regulations set by the acquirer and the card schemes.
To make this step as smooth as possible, this page explains how you can make sure that your solution will pass all tests.
Before you get started, make sure that you have a Test Card available and are running all transactions against the
TEST
gateway:
- For the PayClient: Use
environment.TEST
when connecting.- For P3: In the
LOGIN_MERCHANT_REQUEST
message, set"providerMode": "TEST"
.
Testing Receipts (Signature On Paper Receipt)
Go through the tests below if you capture the customer's signature on the merchant's paper receipt. This is the most common workflow.
Test Case | Description | Required Testing |
---|---|---|
R1 | Every receipt must contain all the required elements. | |
R2 | For every approved transaction that requires a signature from the customer, your solution must print a Merchant Receipt that includes a signature line. Your solution must also provide printed Customer Receipts. |
|
R3 | For every other approved transaction, your solution must print a Merchant Receipt. Your solution must also provide printed Customer Receipts. |
|
R4 | If your solution supports refunds, your solution must print a Customer Receipt for the refund. Your solution can optionally provide a printed Merchant Receipt for the refund. |
|
Testing Receipts (Signature Digitally Captured)
Go through the tests below if you capture the customer's signature digitally, e.g. on the screen of a tablet.
Test Case | Description | Required Testing |
---|---|---|
RD1 | Every receipt must contain all the required elements. | |
RD2 | For every approved transaction that requires a signature from the customer, your solution must electronically capture the signature. Your solution must also provide printed or email-based Customer Receipts. |
|
RD3 | For every other approved transaction, your solution must provide printed or email-based Customer Receipts. |
|
RD4 | If your solution supports refunds, your solution must provide printed or email-based Customer Receipts for the refund. Your solution can also provide a Merchant Receipt for the refund. |
|
Testing Standalone Refunds
Test Case | Description | Required Testing |
---|---|---|
S1 | Solution must protect Standalone Refunds from misuse. |
|
S2 | Standalone Refunds must be only used for refunds. |
|
Submit your solution for approval
Once you've tested your integration yourself, please drop us an email at support@payworks.com containing:
We will provide you with an approval shortly or let you know what still needs to be changed.