Testing
Your solution must be tested before going live. Your account manager must 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.
Make sure that you have a test card available and are running all transactions against the
TEST
gateway:
- For the PayClient: Useenvironment.TESTwhen connecting.
- For P3: In theLOGIN_MERCHANT_REQUESTmessage, set"providerMode": "TEST".
The following information is provided to make this process as easy as possible by explaining how you can make sure that your solution will pass all tests.
Perform the following tests if you capture the customer's signature digitally such as on a tablet.
Perform the following tests if you process standalone refunds.
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.
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 for Digitally Captured Signatures
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
S1 | Solution must protect Standalone Refunds from misuse. |
|
S2 | Standalone Refunds must be only used for refunds. |
|
Submitting Your Solution for Approval
After you have tested your integration, send us an email containing:
- Scans of the custom customer and merchant receipts you implemented.
- A link to a video showing your payment process from start to finish. The payment process must include the two status lines that your POS system must display throughout the payment process.
- When offering Standalone Refunds: A link to a video or screenshots showing how your solution is fulfilling requirementsS1andS2.
We will provide you with an approval or let you know what needs to be done to obtain approval.