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 card schemes.

This information is provided to make this process easy by explaining how you can make sure that your solution will pass all tests.

R1	Every receipt must contain all the required elements.	For PayClient-based integrations, check that you have included all required receipt information. For PayProtocol (P3)-based integrations, check that you have included all required receipt information.
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.	Run an approved CHARGE transaction with the Test Card for amount 10.00 Provide us with a scan of the printed Merchant Receipt .It must contain a line for the customer's signature. Provide us with a scan of the printed Customer Receipt .
R3	For every other approved transaction, your solution must print a Merchant Receipt. Your solution must also provide printed Customer Receipts.	Run an approved CHARGE transaction with the Test Card for amount 40.00 and enter 1234 when asked for a PIN. Provide us with a scan of the printed Merchant Receipt .It must not contain a line for the customer's signature. Provide us with a scan of the printed Customer Receipt .
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.	Run an approved REFUND transaction for the CHARGE from Test Case R1 If offered by your solution: Provide us with a scan of the printed Merchant Receipt . Provide us with a scan of the printed Customer Receipt .

If you capture the customer's signature digitally, such as on a tablet, perform the tests described in the table.

RD1	Every receipt must contain all the required elements.	For PayClient-based integrations, check that you have included all required receipt information. For P3-based integrations, check that you have included all required receipt information.
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.	Run an approved CHARGE transaction with the Test Card for amount 10.00 Provide us with a scan of the printed (or emailed) Customer Receipt .
RD3	For every other approved transaction, your solution must provide printed or email-based Customer Receipts.	Run an approved CHARGE transaction with the Test Card for amount 40.00 and enter 1234 when asked for a PIN. Provide us with a scan of the printed (or emailed) Customer Receipt .
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.	Run an approved REFUND transaction for the CHARGE from Test Case RD1 If offered by your solution: Provide us with a scan of the printed Merchant Receipt . Provide us with a scan of the printed Customer Receipt .

If you process standalone refunds, perform the tests described in the table.

S1	Solution must protect Standalone Refunds from misuse.	Only authorized staff (like the store owner or supervisor) must be allowed to perform Standalone Refunds. This can be achieved for example by offering user roles. Before using Standalone Refunds, the authorized staff member needs to authenticate. This can be achieved for example by asking for a PIN or password.
S2	Standalone Refunds must be only used for refunds.	The user interface wording must be make clear to the merchant staff that Standalone Refunds are only to be used to refund a previous transaction. Under no circumstances may Standalone Refunds be offered to pay out money to a shopper without a relationship to a previous card payment.

Scanned images of the custom customer and merchant receipts that 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.
If you offer standalone refunds, include a link to a video or include screenshots that show how your solution is fulfilling requirements
S1
and
S2
that are described in the above table.