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

View sandbox transactions and webhooks in the Peach Payments sandbox Dashboard.

Test cards and credentials

Use the following test cards and credentials to test integrations.

Card payments

🚧

• Card payments are only available on Checkout.
• When testing multi-currency processing in sandbox, you must use either 92.00 or 15.99 as the transaction amount to simulate a successful transaction.

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

3-D Secure 2

3-D Secure 1

📘

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

When testing in the sandbox environment, use the Capitec Pay testing credentials to test Capitec Pay.

To test Pay by Bank for other EFT payment methods in Checkout in the sandbox environment (in a simulator), when the bank's user interface appears, click the DEVELOPMENT SERVER title, select the status to simulate, and click Continue.

Capitec Pay

To test Capitec Pay against a simulator in the sandbox environment, include "customParameters[enableTestMode]":"true" in the Payments API request body; this is not required when testing on Checkout.

🚧

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.

Peach EFT

Test Peach EFT in Payments API in a simulator in the sandbox environment.

When the bank selector user interface appears, click SIMULATOR, select the status to simulate, and click Continue.

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: 9503095194084
• 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: 0123456789
• OTP: 911911

ZeroPay

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

• ID number: 9512235170089
• OTP: 0000

Float

To test Float against a simulator in the sandbox environment, include "customParameters[enableTestMode]":"true" in the Payments API request body; this is not required when testing on Checkout.

When testing in the sandbox environment, use the Visa or Mastercard test cards to test.

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 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/.

Google Pay

🚧

Google Pay is only available on Checkout.

To test Google Pay in the sandbox environment (in a simulator), use any live card. Your card is not charged because you're in the sandbox environment. Click Google Pay, select your card, click Continue, select the status to simulate, and click Pay.

1Voucher

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

Mobicred

You must request test credentials directly from Mobicred.

RCS cards

To test RCS cards against a simulator in the sandbox environment, include "customParameters[enableTestMode]":"true" in the Payments API request body; this is not required when testing on Checkout. In the sandbox environment, the payment process bypasses the OTP and success screens, redirecting the user to the shopperResultUrl.

Use the following amount values with the card.number set to 6010240000000000 to test certain payment request scenarios:

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 Payments API request body; this is not required when testing on Checkout.

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:

📘

When testing the successful payment scenario on sandbox using the 51100000 number, when you get to the confirmation message screen, wait for the confirmation request to expire to simulate a successful payment.

🚧

• 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 Payments API request body; this is not required when testing on Checkout.

🚧

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 endpoints

• Your live credentials differ from your sandbox credentials. You must swap these credentials before going live.
• The live API endpoints differ from that of the sandbox API endpoints. Ensure that you have updated to the live API endpoints in your code:
  • Embedded Checkout
  • Hosted Checkout
  • Shared Checkout functionality
  • Payment Links
  • Payments API
  • Reconciliation API