Testing Payment on Sandbox

Sandbox Environment can be used to create "testing" transactions (usually performed from your development/testing environment). All transaction made within this environment mode is not "real", and does not require "real payment/fund". This environment is created automatically when you are signing up, and free to use.

In the Sandbox environment, Midtrans uses web-based simulator to simulate a response from payment provider or bank's system. This helps to test different scenarios that can happen on production, without actually doing real payments.

This is the list of payment credentials that you can use on Midtrans Sandbox environment. Please note that, it will not work on Production environment.

---

Card Payments

The table given below lists the details to be entered for simulating credit card transactions. All cards listed below already support 8 digit BINS.

General

FDS refers to our Fraud Detection System. "Denied by FDS" means to simulate a transaction that is being denied because it is suspected as fraudulent.

📘

Note

Not every acquiring banks might be able to accept JCB and Amex card. You can use BNI & BCA acquiring for JCB. BCA acquiring can accept Amex.

Bank-Specific

This is useful for Installment/Promo scenario which require bank specific card.

Accepted 3D Secure Card

Denied Card

Offline Card

It is used for testing a specific scenario where the card is not eligible for online transactions, which result in Deny transaction status.

📘

Note

• General card number is used for general feature testing of card payment.
• Bank specific card number is useful for testing advanced card features (on-us/off-us installments, whitelist BIN, promo, and so on) that require card from specific bank.

3D Secure Version Specific

📘

3DS 2 Behavior Change Notice

To reflect the changes that has been applied to our Production Environment, on 31st January 2023 similar changes is applied to Sandbox Environment. The changes are summarized as follows:

• Most/all acquirer bank MIDs within merchants’ sandbox accounts is upgraded to allow accepting 3DS 2. The previously MIGS acquirer MID's channel will be replaced with MPGS. Which will change the transaction's value of channel_response_message and channel_response_code. As explained in this notice.
• All sandbox testing cards (that were previously 3DS 1) are upgraded to 3DS 2. Including cards listed under General and Bank Specific tabs.
• These changes are supposed to be seamless, not cause breaking, and not require changes of implementation from the merchant side (except IF merchant is still using a very old pre-2019 card integration flow, then card transaction will be treated as 3DS 1).
• Background context: 3DS 1 has been phased-out & upgraded to 3DS 2 in Production Environment & industry wide. Hence the same are applied to Sandbox.

3D Secure 2

Specific cards for testing 3DS 2 card payment scenario.

3D Secure 1

Specific cards for testing outdated 3DS 1 card payment scenario, which will be rejected due to no longer supported.

---

E-Wallet

📘

Note

On Sandbox, Midtrans uses web-based payment simulator. So, payment that requires app deeplink like GoPay, will use web simulator instead of real app deeplink. To test real app deeplink use cases, please use Midtrans Production Environment.

---

Bank Transfer

---

Convenience Store

---

---

Cardless Credit

---

Note & Limitation

Sandbox Env Should Not be Paid with Real Payment

📘

Note

Do not attempt to pay with a real-world payment-provider/bank to a transaction created in the Sandbox environment. Sandbox transactions cannot be paid with real payment, and should only be paid with the Sandbox Payment Simulator/Credentials explained in this page.

​​Midtrans will not be responsible and may not be able to help you recover any real-world payment funds if you do such an action.

Explanation: A payment reference generated on Midtrans Sandbox environment (VA number, QR image, etc.), may possibly be the same reference that is also active on the payment provider’s real environment. If you make a real payment to it, the funds will be routed to the real payment provider’s environment instead, which often the funds will not reach Midtrans. So please keep the environmental difference in mind.

QRIS Specific

For QRIS payment method, usually the sandbox reference will refer to the same Merchant ID you have in your Midtrans Production environment, real payment made there can possibly be routed to your Midtrans Production account. You can try to login to your Midtrans Production account, and may find payment with Order ID formatted as: QRIS-{generated_id}, which you can also try to refund.