Test your Payment Integration

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.
  • For PayClient-based integrations, double check here that you have included all required elements.
  • For P3-based integration, double check here that you have included all 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.
  • 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.

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.
  • For PayClient-based integrations, double check here that you have included all required elements.
  • For P3-based integration, double check here that you have included all 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.
  • 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.

Testing Standalone Refunds

Test Case Description Required Testing
S1 Solution must protect Standalone Refunds from misuse.
  • Only authorised 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 authorised 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.

Submit your solution for approval

Once you've tested your integration yourself, please drop us an email at support@payworks.com containing:

  • Scans of the custom Customer and Merchant Receipts you have implemented
  • Link to a video showing a payment process from start to finish. It must include the two status lines that your POS system must display throughout the payment process
  • When offering Standalone Refunds: Link to video or screenshots showing how your solution is fulfilling requirements S1 and S2

We will provide you with an approval shortly or let you know what still needs to be changed.

Can we help you?

If you cannot find your answer, contact us and we'll get in touch with you soon.

© Copyright 2017 Payworks GmbH. Legal.