Testing

Before your solution can go live, you must test it and send the results to us. Your account manager will review your payment flow and receipts to ensure that everything complies with the rules and regulations set by the acquirer and the card schemes. The following information is provided to help you make sure that your solution will pass all tests.

Testing the Integration Using Mock Mode

Your app must display the correct transaction status to the merchant and correctly implement signature and identity verification.
You can test the correct integration by using the Mock Mode. In this mode, the SDK simulates a transaction workflow without connecting to the card reader or to the platform.
  1. When initializing pass
    MPProviderModeMock
    on iOS or
    ProviderMode.MOCK
    on Android.
  2. Change the
    MPAccessoryFamily
    to
    MPAccessoryFamilyMock
    on iOS or change
    AccessoryFamily
     to MOCK on Android.
  3. Complete each test case by using the amount stated in the test case.
Make sure to disable the Mock Mode before you submit the app to the app stores or give it to your merchants.
Test Case
Description
Amount for Mock Mode
CV1
The app must provide a way to electronically capture the signature of the shopper. This is only relevant to merchants who print receipts.
108.20
CV2
During electronic signature capture, the shopper must have a way to abort the transaction. Not relevant if receipts are printed.
108.20

Testing Receipts

Your solution must send out compliant receipts. The following test cases enable you to test receipt functionality.
Test Case
Description
Recommendation
R1
It must be possible to print or send a receipt to the shopper via email or SMS for approved charges.
After the transaction has been approved, ask the merchant, whether the shopper wants a receipt. If yes, print the receipt or ask for the email of the shopper and send the receipt.
R2
If you support refunds, it must be possible to send out a refund receipt for approved refunds.
If you support refunds, make sure it is possible to send a shopper receipt after an approved refund.
R3
The receipts must contain all required information.
See required receipt informationand how to get them from the receipt API.
R4
If the signature is required and it is not electronically captured, then the signature line must be shown on the merchant receipt.
Check whether the shopper's signature is required and then make sure you capture it on the printed receipt.

Testing Standalone Refunds

The following test cases enable you to test standalone refund functionality.
Test Case
Description
Required Testing
S1
Solution must protect Standalone Refunds from misuse.
  • Only authorized staff (such as the store owner or supervisor) must be allowed to perform Standalone Refunds. This can be achieved by offering user roles.
  • Before using Standalone Refunds, the authorized staff member needs to authenticate. This can be achieved 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 can Standalone Refunds be offered to pay out money to a shopper without a relationship to a previous card payment.

Submit your solution for approval

After you have tested your integration, contact us and include the following information:
  • 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.
We will review and approve your solution or provide information about what must be done in order to receive approval.

Related information