Welcome to Xendit’s latest documentation. For legacy content, access the previous version here.

Simulate card scenarios

Prev Next

To facilitate testing of card transactions, we provide a range of test card numbers. These numbers vary based on the country of operation and your live connection. For specific guidance on which test card numbers to use for your integration, please contact Xendit Customer Support.

Test card numbers

The following tables detail the available test card numbers, their brands, applicable countries, and simulated scenarios.

Card Number

Brand

Countries

Scenario

4000000000002503

VISA

Indonesia, Malaysia

3DS Challenge, authentication is successful if OTP is correct.

4000000000001000

VISA

Indonesia, Malaysia

3DS Frictionless, authentication is successful.

5200000000002151

MASTERCARD

Indonesia, Malaysia

3DS Challenge, authentication is successful if OTP is correct.

5200000000001005

MASTERCARD

Indonesia, Malaysia

3DS Frictionless, authentication is successful.

4440000009900010

VISA

Indonesia, Malaysia

3DS Challenge, see list of simulated options on the next table.

4440000042200014

VISA

Malaysia

3DS Frictionless, authentication is successful.

5123450000000008

MASTERCARD

Malaysa

3DS Challenge, see list of simulated options on the next table.

5123456789012346

MASTERCARD

Malaysia

3DS Frictionless, authentication is successful.

4200350000000801

VISA

Thailand

3DS Challenge, authentication is successful if OTP is correct.

For frictionless flow, use amount < THB 20.

5413530000000501

MASTERCARD

Thailand

3DS Challenge, authentication is successful if OTP is correct.

For frictionless flow, use amount < THB 20.

4000000000002503

VISA

Thailand

Failing transaction

5200000000002151

MASTERCARD

Thailand

Failing transaction

Simulating failed charge payments by amount

You can simulate specific failed charge payment scenarios using these amounts. Simulated numbers are applicable for all countries except Vietnam.

Amount

Simulated code

Applicable country

Scenario

10051

EXPIRED_CARD

10052

ISSUER_SUSPECT_FRAUD

10053

DECLINED_BY_PROCESSOR

10054

INSUFFICIENT_BALANCE

10055

STOLEN_CARD

10056

INACTIVE_OR_UNAUTHORIZED_CARD

10057

PROCESSOR_ERROR

10058

INVALID_CVV

10059

DECLINED_BY_ISSUER

Simulate a 3DS challenge authentication flow result

To test different outcomes for 3DS challenge flows:

  1. Create a token request with should_authenticate = true.

  2. Navigate to the URL provided by payer_authentication_url.

  3. On the MPGS ACS Simulator page, select one of the following options:

Authentication option

Status

Scenario

AUTHENTICATED

SUCCESS

Authentication is successful.

UNAUTHENTICATED

FAILED

Authentication is unsuccessful.

CANCELLED_AUTHENTICATION

FAILED

AUTHENTICATION_NOT_AVAILABLE

FAILED

AUTHENTICATION_REJECTED

FAILED

AUTHENTICATION_SERVER_ERROR

FAILED

API_GW_ASM_POLICY_ERROR

FAILED

Test cards for authentication flow

These cards are specifically for simulating 3DS challenge authentication results:

Card number

Brand

Scenario

4200350000000801

VISA

3DS Challenge, authentication is successful if OTP is correct.

For frictionless flow, use amount < THB 20.

5413530000000501

MASTERCARD

3DS Challenge, authentication is successful if OTP is correct.

For frictionless flow, use amount < THB 20.

Simulate a FAILED Charge Payment

Amount

Simulated code

Scenario

10.05

DECLINED_BY_ISSUER

05 - Do Not Honor

10.14

INVALID_CARD

14 - Invalid card number

10.30

PROCESSOR_ERROR

30 - Format Error

10.51

INSUFFICIENT_BALANCE

51 - Insufficient Balance

10.65

DECLINED_BY_ISSUER

65 - Exceeds Withdrawal. Only applicable for VISA Cards only.

BCA payment gateway test cards

For testing BCA payment gateway integrations:

Card Number

Brand

Scenario

1889800000000171

BCA

3DS Challenge, authentication is successful if OTP is correct.

Note: BCA does not support the testing of failing transactions.