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

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 2, https://peachpayments.docs.oppwa.com/tutorials/threeDSecure/3DSTestCards contains a set of test cards. A subset of these cards is available below:

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.

Pay by Bank

Use the Capitec Pay testing credentials to test Capitec Pay, the Nedbank Direct EFT testing credentials to test Nedbank Direct EFT, and the EFTsecure testing credentials to test all other EFT payment methods.

Capitec Pay

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

🚧

High-risk merchants must provide verified ID numbers that the customer cannot edit. They cannot offer the phone number option.

Use the following ID or phone numbers to test certain Capitec Pay payment request scenarios:

Use the following ID or phone 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.

Nedbank Direct EFT

Use the following username and password when testing Nedbank Direct EFT on the sandbox environment:

• Username: apimtestuser3
• Password:IamN3db@nk123

The test account has three accounts, with the following balances:

• Current account: R996.28
• Savings account: R13913.52
• Credit card: R500.20

The following table describes certain scenarios and their result codes:

EFTsecure

🚧

• Your account must be in test mode.
• 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 webhooks in the Peach Payments sandbox Dashboard.

Payflex

📘

Payflex must add you to their allowlist before you can test.

When testing in the sandbox environment, use the following details:

• Email: Any email address
• ID number: 8611100768080
• Test card number: 4111 1111 1111 1111
• Test card name: Anything
• Test card CVV: Any three digits
• Test card expiry date: Any future date
• Phone number: 0722303869
• OTP: 911911

View sandbox transactions in the Peach Payments sandbox Dashboard.

ZeroPay

When testing in the sandbox environment, use the following details:

• ID number: 9512235170089
• OTP: 0000

View sandbox transactions in the Peach Payments sandbox Dashboard.

Scan to Pay

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

   • Android: Nedbank Scan to Pay, Standard Bank Scan to Pay, Absa Scan to Pay, Masterpass Scan to Pay
   • iOS: Nedbank Scan to Pay, Standard Bank Scan to Pay, Absa Scan to Pay, Masterpass Scan to Pay

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 Hosted Checkout.
• You must have an Apple developer test account to test Apple Pay.

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

1Voucher

When testing in the sandbox environment, request test vouchers from support.

Mobicred

You must request test credentials directly from Mobicred.

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, include "customParameters[enableTestMode]":"true" in the request body.

Use the following phone numbers to test certain 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.

MCB Juice

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

🚧

You cannot test a successful transaction end-to-end.

Use the following amounts to test certain failure scenarios:

Go live

When you have completed integration and testing and your payments integration is working in the sandbox environment, switch to your live credentials to begin accepting live payments.

❗

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:
  • Checkout
  • Payments API
  • Embedded Checkout