While integrating, you have access to a sandbox account during user acceptance testing. Use this account to test fake payments to verify your integration.

📘

In sandbox, it's impossible to test the entire debit flow for A+, Payflex, ZeroPay, Mobicred, and FinChoicePay.

For EFTsecure, your account must be in test mode.

Test cards and credentials

Use the following test cards and credentials to test integrations.

Card payments

🚧

Card payments are only available on Checkout.

Test cards are available for both versions of 3-D Secure.

For 3-D Secure 1, https://peachpayments.docs.oppwa.com/reference/parameters#testing contains a set of test cards. You can also use the following test cards:

📘

For all the test cards in the table above:

• For Visa, Mastercard, and Diners cards, the CVV is any three digits. For American Express cards, the CVV is any four digits.
• For the expiry date, any future date is acceptable.
• These test cards simulate a successful transaction.

For 3-D Secure 2, https://peachpayments.docs.oppwa.com/tutorials/threeDSecure/3DSTestCards contains a set of test cards. A subset of these cards is available below:

Capitec Pay

To test Capitec Pay against a simulator in the sandbox environment, include "customParameters[enableTestMode]":"true" in the request body.

Use the following cellphone numbers to test certain Capitec Pay payment request scenarios:

Use the following cellphone numbers to test certain Capitec Pay transaction status scenarios:

🚧

• To execute tests against the actual endpoints, contact support.
• Testing this way requires manual intervention and synchronisation between you, Peach Payments, and Capitec.

EFTsecure

🚧

When testing in the sandbox environment, EFTsecure transaction amounts must be R10.00 or less, or equal to R101, R1001, R10001, or R100001.

View sandbox transactions and manage sandbox webhooks in the Peach Payments Console.

Scan to Pay

1. Download any Scan to Pay app available in your region on your phone:

   • Android: Nedbank Masterpass, Standard Bank Masterpass, Absa Masterpass, Capitec Masterpass
   • iOS: Nedbank Masterpass, Standard Bank Masterpass, Absa Masterpass, Capitec Masterpass

2. Switch to the Scan to Pay test environment in the app by scanning this QR code.

3. Add any of the following test cards to your Scan to Pay wallet:
   • Debit cards:
     • Any 18-digit card starting with 50010001000105 with any bank PIN = 00 response (success)
     • Any 18-digit card starting with 50010001000101 with any bank PIN = 51 response (insufficient funds)
     • Any 18-digit card starting with 50020001000103 with any bank PIN = 91 response (issuer or switch inoperative or bank unavailable)
   • Credit cards:
     • Any 18-digit card starting with 50020001000105 with any bank PIN = 00 response (success)
     • Any 18-digit card starting with 50020001000101 with any bank PIN = 51 response (insufficient funds)
     • Any 18-digit card starting with 50020001000103 with any bank PIN = 91 response (issuer or switch inoperative or bank unavailable)
4. Select Scan to Pay as the payment method and scan the QR code presented to you on the payment page.
5. Pay for your order using one of the stored cards in your wallet.
6. Do not close the browser after completing the payment in the app.

Apple Pay

🚧️

Apple Pay is only available on Checkout.

Test cards for sandbox are available on https://developer.apple.com/apple-pay/sandbox-testing/.

🚧️

You must have an Apple developer test account to test Apple Pay.

M-PESA

To test M-PESA, contact support for test credentials.

blink by Emtel

To test blink by Emtel against a simulator in the sandbox environment, use the following phone numbers to test certain blink by Emtel payment request scenarios:

Use the following phone numbers to test certain blink by Emtel transaction status scenarios:

🚧

• To execute tests against the actual endpoints, contact support.
• Testing this way requires manual intervention and synchronisation between you, Peach Payments, and Emtel.

Go live

When you have completed integration and testing and your payments integration is working in the sandbox environment, you can contact support to request the go-ahead to go live.

If approved to go live, the support team provides you with a new set of authentication credentials.

❗

Live credentials and API endpoint

• Your live credentials differ from your sandbox credentials. You must swap these credentials before going live.
• The live API endpoint differs from that of the sandbox API endpoint. Ensure that you have updated to the live API endpoint in your code.