Home  ›  How Easy to Get Approved by Adyen

How Easy to Get Approved by Adyen

Written By Wednesday, 5 October 2022 Add Comment Edit
Testing POS payments?

We provide a physical test card for use with our test payment terminals. For more information, see our point-of-sale test cards.

Before accepting live payments, you can use the cards and payment method details on this page to test your integration. These are only valid on our test platform, and will not result in a real transaction or transfer of funds.

You can check the status of test payments in your Customer Area > Transactions > Payments.

When you use RevenueProtect, test payments might be blocked because they can appear fraudulent. To continue testing, you can temporarily add the test card and shopper details to a trust list.

The test card numbers are only valid on the Adyen test platform and will not work anywhere else.

Credit and debit cards

Here we provide test card numbers for the following credit and debit cards:

  • American Express
  • Bancontact
  • Cartes Bancaires
  • China UnionPay
  • Dankort
  • Diners
  • Discover
  • Elo
  • Hipercard
  • JCB
  • Maestro
  • Mastercard
  • UATP
  • Visa
  • Visa Electron
  • V Pay

We also provide information on how you can test:

  • 3D Secure authentication
  • Address Verification System (AVS)
  • Real Time Account Updater scenarios
  • Submitting encrypted card details
  • Submitting Level 2/3 data

Some test cards do not require a security code. These are tagged with security code optional.

When you make a test payment with these card details you'll receive a resultCode of Authorised. To test how your integration responds to other payment scenarios, such as refused or invalid payments, see Result code testing.

American Express (Amex)

Card Number Issuing Country Expiry Date CID
3700 0000 0000 002 NL 03/2030 7373
3700 0000 0100 018
security code optional 		NL 03/2030 7373

Bancontact (BCMC)

Card Number Card Type CVV2/CVC2 Username Password Issuing Country Expiry Date
6703 4444 4444 4449 BCMC / Maestro None user password BE 03/2030
6703 0000 0000 0000 003 BCMC / Maestro None user password BE 03/2030
4871 0499 9999 9910 BCMC / Visa Debit BCMC: None
Visa: 737		 user password BE 03/2030

Cartes Bancaires

Card Number Card Type Issuing Country Expiry Date CVV2/CVC3
4035 5010 0000 0008 Visa Debit / Cartes Bancaires FR 03/2030 737
4360 0000 0100 0005 Cartes Bancaires FR 03/2030 737

China UnionPay

ExpressPay Credit Card (cup)

Card Number Expiry Date CVC Issuing Country
8171 9999 2766 0000 10/2030 737 CN
8171 9999 0000 0000 021 10/2030 737 CN
6243 0300 0000 0001 12/2029 737 CN

Dankort

Card Number Expiry Date CVV2/CVC3
5019 5555 4444 5555 03/2030 737

Diners

Card Number Issuing Country Expiry Date CVV2/CVC3
3600 6666 3333 44 US 03/2030 737
3607 0500 0010 20
security code optional 		NL 03/2030 737

Discover

Card Number Issuing Country Expiry Date CVD/CID
6011 6011 6011 6611 US 03/2030 737
6445 6445 6445 6445 GB 03/2030 737

Elo

Card Number Issuing Country Expiry Date CVE
5066 9911 1111 1118 BR 03/2030 737

Hipercard

Card Number Issuing Country Expiry Date CVV2/CVC3
6062 8288 8866 6688 BR 03/2030 737

JCB

Card Number Card Type Issuing Country Expiry Date CVV2/CVC3
3569 9900 1009 5841 Consumer US 03/2030 737

Maestro

For online Maestro payments, 3D Secure is mandatory. See Test 3D Secure 2 authentication.

Card Number Issuing Country Expiry Date CVV2/CVC3
6771 7980 2100 0008 US 03/2030 737

Mastercard

Card Number Card Type Issuing Country Expiry Date CVC3
2222 4000 7000 0005 Commercial Debit CA 03/2030 737
5555 3412 4444 1115

security code optional

Consumer NL 03/2030 737
5577 0000 5577 0004 Consumer PL 03/2030 737
5555 4444 3333 1111 Consumer GB 03/2030 737
2222 4107 4036 0010 Corporate NL 03/2030 737
5555 5555 5555 4444 Corporate GB 03/2030 737
2222 4107 0000 0002 Corporate Credit NL 03/2030 737
2222 4000 1000 0008 Credit CA 03/2030 737
2223 0000 4841 0010 Credit NL 03/2030 737
2222 4000 6000 0007 Debit CA 03/2030 737
2223 5204 4356 0010 Debit NL 03/2030 737
2222 4000 3000 0004 Fleet Credit CA 03/2030 737
5100 0600 0000 0002 Premium Credit US 12/2029 737
2222 4000 5000 0009 Purchasing Credit CA 03/2030 737

UATP

Card Number Card Type Expiry Date CVV2/CVC3
1354 1001 4004 955 UATP 03/2030 None

Visa

Card Number Card Type Issuing Country Expiry Date CVV2
4111 1111 4555 1142
security code optional 		Classic NL 03/2030 737
4111 1120 1426 7661
eight-digit BIN 		Debit FR 12/2030 737
4988 4388 4388 4305 Classic ES 03/2030 737
4166 6766 6766 6746 Classic NL 03/2030 737
4646 4646 4646 4644 Classic PL 03/2030 737
4000 6200 0000 0007 Commercial Credit US 03/2030 737
4000 0600 0000 0006 Commercial Debit US 03/2030 737
4293 1891 0000 0008 Commercial Premium Credit AU 03/2030 737
4988 0800 0000 0000 Commercial Premium Debit IN 03/2030 737
4111 1111 1111 1111 Consumer NL 03/2030 737
4444 3333 2222 1111 Corporate GB 03/2030 737
4001 5900 0000 0001 Corporate Credit IL 03/2030 737
4000 1800 0000 0002 Corporate Debit IN 03/2030 737
4000 0200 0000 0000 Credit US 03/2030 737
4000 1600 0000 0004 Debit IN 03/2030 737
4002 6900 0000 0008 Debit AU 03/2030 737
4400 0000 0000 0008 Debit US 03/2030 737
4484 6000 0000 0004 Fleet Credit US 03/2030 737
4607 0000 0000 0009 Fleet Debit MX 03/2030 737
4977 9494 9494 9497 Gold FR 03/2030 737
4000 6400 0000 0005 Premium Credit AZ 03/2030 737
4003 5500 0000 0003 Premium Credit TW 03/2030 737
4000 7600 0000 0001 Premium Debit MU 03/2030 737
4017 3400 0000 0003 Premium Debit RU 03/2030 737
4005 5190 0000 0006 Purchasing Credit US 03/2030 737
4131 8400 0000 0003 Purchasing Debit GT 03/2030 737
4035 5010 0000 0008 Visa FR 03/2030 737
4151 5000 0000 0008 Visa Credit US 03/2030 737
4571 0000 0000 0001 Visa Dankort DK 03/2030 737
4199 3500 0000 0002 Visa Proprietary FR 03/2030 737

Visa Electron

Card Number Issuing Country Expiry Date CVV2/CVC3
4001 0200 0000 0009 BR 03/2030 737

V Pay

Card Number Issuing Country Expiry Date CVV2/CVC3
4013 2500 0000 0000 006 PL 03/2030 737

Test 3D Secure 2 authentication

If your default dynamic 3D Secure rule is set to Prefer Not, then the following test cards will not trigger 3D Secure. You can either set your default dynamic 3D Secure rule to Always or force 3D Secure by passing authenticationData.attemptAuthentication in your API request.

To test how your integration handles different 3D Secure 2 authentication scenarios, use our test card numbers.
When prompted for 3D Secure 2 text challenges, use the following credentials:

  • For native mobile integrations, use password: 1234
  • For web and mobile browser integrations, use password: password
Card Type Card Number Expiry Date Security Code (CVC/CVV/CID)
American Express 3714 4963 5398 431 03/2030 7373
Cartes Bancaires / Visa Debit 4035 5014 2814 6300 03/2030 737
China UnionPay (Credit) 6250 9470 0000 0014 03/2030 123
China UnionPay (Debit) 6250 9460 0000 0016 03/2030 123
Diners 3056 9309 0259 04 03/2030 737
Discover 6011 1111 1111 1117 03/2030 737
Maestro 5000 5500 0000 0029 03/2030 n/a
Visa 4917 6100 0000 0000 03/2030 737

When you make a payment request with these cards, you'll receive the following result codes depending on your integration:

  • RedirectShopper: You'll receive this result code if you are using the Redirect authentication.
  • IdentifyShopper: You'll receive this result code if you are using the Native authentication.
  • ChallengeShopper: You will get this result code after you submit the 3D Secure 2 device fingerprinting result in a Native authentication, unless you specify a frictionless flow.

To test the web-based flow where the device fingerprinting step is skipped (because the issuer's ACS has not configured a threeDSMethodURL), and you get a ChallengeShopper resultCode immediately after submitting the payment request, use the following card:

Card Type Card Number Expiry Date Security Code (CVC/CVV/CID)
Visa 4212 3456 7891 0006 03/2030 737

To test the frictionless flow, in which you perform a fingerprint but no challenge, use the following test card number:

Card number Expiry Date Security Code (CVC/CVV/CID) Authentication scenario
5201 2815 0512 9736 03/2030 737 Fingerprint but no challenge

App-based integration

To test different authentication scenarios for app-based integration, use the following test cards:

Card number Expiry Date Security Code (CVC/CVV/CID) Authentication scenario
5201 2855 6567 2311 03/2030 737 Basic text authentication
5201 2874 9905 2008 03/2030 737 Basic single select
5201 2815 9233 1633 03/2030 737 Basic multi select
5201 2888 2269 6974 03/2030 737 Basic out-of-band (OOB) authentication
5201 2895 0084 3268 03/2030 737 HTML OOB authentication
5201 2861 5377 1465 03/2030 737 App single select then text authentication

Other scenarios

Card number Expiry Date Security Code (CVC/CVV/CID) Scenario
4199 3500 0000 0002 03/2030 737 The card is not enrolled for 3D Secure transactions.
5201 2829 9900 5515 03/2030 737 There was a technical error. This test card simulates a timeout during the 3D Secure 2 authentication flow on the issuer side. Depending on your configuration, the transaction might still proceed to a successful authorization.

Test 3D Secure 1 authentication

Card Type Card Number Country Expiry Month Expiry Year Security Code (CVC/CVV)
American Express 3451 7792 5488 348 International 03 2030 7373
International 6731 0123 4567 8906 NL 03 2030 737
JCB 3569 9900 1009 5833 US 03 2030 737
Maestro 6771 8309 9999 1239 GB 03 2030 737
Maestro 6771 8300 0000 0000 006 GB 03 2030 737
Mastercard 5212 3456 7890 1234 JP 03 2030 737
Visa 4212 3456 7890 1237 CA 03 2030 737

When prompted for 3D Secure authentication, use the following credentials:

  • Username: user
  • Password: password

Card not enrolled in 3D Secure 1

To test a scenario where the card is not enrolled for 3D Secure transactions, use the following card:

Card Type Card Number Expiry Date Security Code (CVV2)
Visa 4199 3500 0000 0002 03/2030 737

Liability Shift Testing

If 3D Secure is offered, but the issuer is unavailable, no liability shift will occur. To test this, use a 3D Secure Enabled card with the default username and the password NoLiabilityShift.

Additional MPI Testing

Other testing flows may be conducted using different available password patterns as represented by the following regular expression:

"TestMpi([YNU]|DASH)([YANU]|DASH)"

Use DASH to pass an empty or unavailable value for VERes or PARes.

That means a password "TestMpi" followed by a combination of VERes and PARes values.

  • VERes possible values are Y, N, U or DASH.
  • PARes possible values are Y, A, N, U or DASH.

Examples of valid passwords: "TestMpiYY", "TestMpiYA", "TestMpiUDASH", "TestMpiDASHDASH", etc.

Test Address Verification System (AVS)

Use the following shopper details to test AVS:

Card Number Card Type House Number Address ZIP Code Country Expiry Date Security Code (CVV/CVC/CID)
5555555555554444 Mastercard 10 Downing Street, London. SW1A 2AA GB 03/2030 737
374251018720018 Amex 1600 Pennsylvania Ave NW Washington, DC. 20500 US 03/2030 7373
374251021090003 Amex 1 Infinite Loop Cupertino, CA. 95014 US 03/2030 7373
374101012180018 Amex 10 Downing Street, London. SW1A 2AA GB 03/2030 7373
374251033270007 Amex 8-10 Broadway, Westminster, London. SW1H 0BG GB 03/2030 7373
4400000000000008 Visa 1 Infinite Loop Cupertino, CA. 95014 US 03/2030 737
4444333322221111 Visa 8-10 Broadway, Westminster, London. SW1H 0BG GB 03/2030 737

Refer to the list of the avsResult values you can receive.

Test Real Time Account Updater scenarios

To test how different Real Time Account Updater scenarios work for your integration, use the following test card numbers in your payments request.
You can only use our standard Real Time Account Updater services if all of the following conditions are met:

  • You are tokenizing with Adyen.
  • The amount specified in the payment is not zero.
  • The shopperInteraction parameter is set to ContAuth.
  • The payment does not contain CVC.

You will receive the corresponding status in the additionalData.realtimeAccountUpdaterStatus field of your response.

Status Card number Expiry Date
CardChanged 5454 5476 9908 4950 03/2030
CardExpiryChanged 5454 5418 5840 6567 Any date except 03/2030
CloseAccount 5454 5415 8031 1093 03/2030
ContactCardAccountHolder 4111 1131 5971 2925 03/2030

If you are not fully PCI compliant and unable to process raw card data, add a prefix of test_ to the credentials. This allows you to test using encrypted card details.

Test submitting encrypted card details

If you would like to test API calls from your server but your client-side integration is not ready yet, add a prefix of test_ to the test card credentials.

For example, to use Mastercard test card 5555555555554444, specify the following in your /payments request:

          { ... "paymentMethod": {     "type": "scheme",     "encryptedCardNumber": "test_5555555555554444",     "encryptedExpiryMonth": "test_03",     "encryptedExpiryYear": "test_2030",     "encryptedSecurityCode": "test_737"   } }

Test submitting Level 2/3 data

To verify that you are correctly sending Level 2 or Level 3 data, submit a /payments request with one of the following card numbers. The card numbers correspond to a type of response:

Card number Expiry Date CVC Response
4444 3333 2222 1111 03/2030 737 VGIS
2222 4107 4036 0010 03/2030 737 L2
5555 5555 5555 4444 03/2030 737 L3

If you receive one of the above responses in an additionalData object (for example, "cardSchemeEnhancedDataLevel" : "L2") , you have successfully set up your account to handle Level 2 or Level 3 data.

3x 4x Oney

France

Test card number Expiry date CVV
4970 1015 5874 4789 Any date less than 3 years from now Any value
4970 1090 4680 2374 Any date less than 3 years from now Any value
4970 1090 0325 6200 Any date less than 3 years from now Any value

You can test the different responses by changing the amount to be paid:

  • Authorised: Between EUR 150.00 and EUR 999.99
  • Pending: Between EUR 1000.00 and EUR 1499.99
  • Refused: Between EUR 1500.00 and EUR 2000.00

Spain

Test card number Expiry date CVV
4907 2720 1107 2841 Any date less than 3 years from now Any value
5410 0800 0888 8005 Any date less than 3 years from now Any value

You can test the different responses using different Documento Nacional de Identidad (DNI, Spanish ID card) numbers:

  • Authorised: DNI 05696340E
  • Refused: DNI 75914068S

ACH

Account Owner's Name Bank account number Bank routing number Account Owner's Address
Any name Any correctly formatted account number. Example: 123456789 011000138 or 121000358 Any correctly formatted US address.

Alipay

Username Pin
sandbox_forex1@alipay.com 111111

Alipay Hong Kong

Username PIN Payment PIN
hkbuyer_9709@alitest.com a111111 b111111

Apple Pay

Card Type Card number Expiry date CVC/CID
Discover 6011 0009 9446 2780 11/2022 111
Mastercard 5204 2452 5000 1488 11/2022 111
Visa 4761 1200 1000 0492 11/2022 533

For a full list of test cards and instructions how to add these to your test device, see Sandbox testing on Apple's Developer website.

BACS

Account name Account Number Sort Code
David Archer

40308669

 560036

BillDesk

For card payments processed through BillDesk, use the following details to test different responses.

Card number Static OTP Expiry CVV Response Type Country 3DS enrolled Allows create mandate
4242420100058007 112201 12/2029 123 PGS10001 Success Visa - Credit IN -white_check_mark- -white_check_mark-
4242420100058064 112207 12/2029 123 PBE10002 Insufficient funds Visa - Credit IN -white_check_mark- -x-
4343430200036090 112249 12/2029 123 PGS10001 Success Visa - Debit IN -white_check_mark- -x-
5252520200034008 112217 12/2029 123 PGS10001 Success Mastercard - Credit IN -white_check_mark- -white_check_mark-
5252520200034065 112223 12/2029 123 PBE10002 Insufficient funds Mastercard - Credit IN -white_check_mark- -x-
5353530200033106 112260 12/2029 123 PGS10001 Success Mastercard - Debit IN -white_check_mark- -x-

Boku

Format: Country Code + Resultcode Example success: "GB00" Example refusal: "DE11".

Boleto Bancário

Shopper Name Social security number Billing address Delivery date Shopper statement
Any name Any CPF or CNPJ number, for example, 56861752509 Any correctly formatted BR address Any ISO 8601 date and time in UTC format, for example, 2023-12-31T23:00:00.000Z Any. If left blank, the statement will be populated with default Portuguese text.

Brazil vouchers

Card type Card number Expiry Date CVC
Ticket (Edenred) 6033 4225 5384 5003 01/2023 418

Cash Ticket

Card Number
0000 0000 0990 3188

Doku

Here are the simulators you can use to test payment completion via Indonesian bank transfers and convenience stores.

  • Alfamart
  • BCA
  • BNI
  • BRI
  • CIMB Bank Transfer
  • Danamon Bank Transfer
  • Indomaret
  • Mandiri Bank Transfer
  • Permata Bank Transfer

Alfamart

The Alfa Simulator allows you to test the part of the payment flow where the shopper completes the payment in cash, at a convenience store. When you create a test payment for Alfamart, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the Alfa Simulator.
  2. Select the Inquiry tab.
  3. Append 00000002 to the 16-digit reference code and enter the new value in the Customer field.
  4. Select Submit. An Inquiry Success response confirms the payment has not expired.
  5. Make a note of the value for the Agent Trx ID in the response. You will need this in the next steps.

Complete the test payment

  1. Go to the Alfa Simulator.
  2. Select the Payment tab and enter:
    • Customer — the vaNumber.
    • Amount — the value of the payment in minor units.
    • Transaction Id — the Agent Trx ID.
  3. Select Submit.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

Continue to the Commit tab below to get a notification from us that the shopper completed the payment.

Get a notification of the completed payment

This step simulates the notification that the shopper completed the payment.

  1. Go to the Alfa Simulator.
  2. Select the Commit tab and enter:
    • Customer — the 16-digit action.reference value.
    • Transaction Id — the Agent Trx ID.
  3. Select Submit.

A Commit Success response means you can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

BCA

The BCA Simulator allows you to test the part of the payment flow where the shopper completes the payment using an ATM, online banking or mobile banking. When you create a test payment for BCA, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the BCA Simulator.
  2. Select the Inquiry tab and enter:
    • Company code — the first 5 digits of the action.reference value.
    • Customer number — the last 11 digits of the action.reference value.
  3. Select Submit. An Inquiry Success response confirms the payment has not expired.
  4. Make a note of the value for the Agent Trx ID in the response. You will need this in the next steps.

Complete the test payment

  1. Go to the BCA Simulator.
  2. Select the Payment tab and enter:
    • Company code — the first 5 digits of the action.reference value.
    • Customer number — the last 11 digits of the action.reference value.
    • Request ID — value of the Agent Trx ID from the Inquiry tab response.
    • Name — shopper's first and last name.
    • Amount - the value of the payment in minor units.
  3. Select Submit.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

BNI

The BNI Simulator allows you to test the part of the payment flow where the shopper completes the payment using an ATM, online banking or mobile banking. When you create a test payment for BNI, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the BNI Simulator.
  2. In the VA Number field, enter the 16-digit action.reference value.
  3. Select the search icon.
  4. In the Payment Amount field, enter the value of the payment in minor units.
  5. In the Direction field, select Credit.
  6. Select Flag.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

BRI

The BRI Simulator allows you to test the part of the payment flow where the shopper completes the payment using an ATM, online banking or mobile banking. When you create a test payment for BRI, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the BRI Simulator.
  2. Select the Inquiry tab.
  3. Enter the 16-digit action.reference value.
  4. Select Submit. An Inquiry Success response confirms the payment has not expired.

Complete the test payment

  1. Go to the BRI Simulator.
  2. Select the Payment tab and enter:
    • Customer — the 16-digit action.reference value.
    • Amount — the value of the payment in minor units.
    • Transaction Id — any value.
  3. Select Submit.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

CIMB Bank Transfer

The CIMB Simulator allows you to test the part of the payment flow where the shopper completes the payment using an ATM, online banking or mobile banking. When you create a test payment for CIMB Bank Transfer, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the CIMB Simulator.
  2. Select the Inquiry tab and enter:
    • Company Code — the first 5 digits of the action.reference value.
    • Customer Key 1 — the last 11 digits of the action.reference value.
  3. Select Submit.

An Inquiry Success response confirms the payment has not expired..

Complete the test payment

  1. Go to the CIMB Simulator.
  2. Select the Payment tab and enter:
    • Company Code — the first 5 digits of the action.reference value.
    • Customer Key 1 — the last 11 digits of the action.reference value.
    • Amount — the value of the payment in minor units.
  3. Select Submit.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

Danamon Bank Transfer

The Danamon Simulator allows you to test the part of the payment flow where the shopper completes the payment using an ATM, online banking or mobile banking. When you create a test payment for Danamon Bank Transfer, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the Danamon Simulator.
  2. Select the Inquiry tab and enter:
    • BIN NUMBER — any 7-digit number.
    • VIRTUAL ACCOUNT NUMBER — the 16-digit action.reference value.
  3. Select Submit. An Inquiry Success response confirms the payment has not expired..
  4. Make a note of the following values you get in the response:
    • User Reference Number
    • Virtual Account Name

Complete the test payment

  1. Go to the Danamon Simulator.
  2. Select the Payment tab and enter:
    • BIN NUMBER — any 7-digit number.
    • VIRTUAL ACCOUNT NUMBER — the 16-digit action.reference value.
    • USER REFERENCE NUMBER — the value from the Inquiry tab.
    • VIRTUAL ACCOUNT NAME — the value from the Inquiry tab.
    • PAYMENT AMOUNT — the value of the payment in minor units.
    • PAYMENT ACCOUNT — any number.
  3. Select Submit

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

Indomaret

The Indomaret simulator allows you to test the part of the payment flow where the shopper completes the payment in cash, at a convenience store. When you create a test payment for Indomaret, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the Indomaret simulator.
  2. Select the Inquiry tab and enter:
    • PAYMENT CODE — the 16-digit action.reference value.
    • PRODUCT CODE — 6588.
    • STORE ID — 97865123.
    • SHARE KEY — 66PXUFvr1jp7.
  3. Select Submit.
  4. Make a note of the TRACKING REF you get in response.

Complete the test payment

  1. Go to the Indomaret simulator.
  2. Select the Payment tab and enter:
    • PAYMENT CODE — the 16-digit action.reference value.
    • AMOUNT — the value of the payment, with two decimal places (add .00 to the end of the sum).
    • STORE ID — 97865123.
    • TRACKING REF — the value from the Inquiry tab, with no spaces.
    • PRODUCT CODE — 6588.
    • SHARE KEY — 66PXUFvr1jp7.
  3. Select Submit.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

Mandiri Bank Transfer

The Mandiri Simulator allows you to test the part of the payment flow where the shopper completes the payment using an ATM, online banking or mobile banking. When you create a test payment for Mandiri Bank Transfer, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the Mandiri Simulator.
  2. Select the Inquiry tab and enter:
    • Company Code — any 5-digit number.
    • Virtual Account Number — the 16-digit action.reference value.
  3. Select Submit.

An Inquiry Success response confirms the payment has not expired.

Complete the test payment

  1. Go to the Mandiri Simulator.
  2. Select the Payment tab and enter:
    • Company Code — the 5-digit number you used before.
    • Amount — the value of the payment in minor units.
    • Virtual Account Number — the 16-digit action.reference value.
  3. Select Submit.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

Permata Bank Transfer

The Permata Simulator allows you to test the part of the payment flow where the shopper completes the payment using an ATM, online banking or mobile banking. When you create a test payment for Permata Bank Transfer, the response will have an action.reference value which is the 16-digit reference code you need below.

Check the status of the payment

This step checks if the payment has expired or not. The shopper cannot make the payment if it expired.

  1. Go to the Permata Simulator
  2. Select the Inquiry tab and enter:
    • INST CODE — any 3-digit number.
    • VIRTUAL ACCOUNT NUMBER — the voucher code.
    • TRACE NUMBER — any 6-digit number.
    • Date — the transaction date, in the MMDDHHmmss format.
  3. Select Submit.

An Inquiry Success response confirms the payment has not expired.

Complete the test payment

  1. Go to the Permata Simulator
  2. Select the Inquiry tab and enter:
    • INST CODE — any 3-digit number.
    • VIRTUAL ACCOUNT NUMBER — the voucher code.
    • TRACE NUMBER — any 6-digit number.
    • Date — the transaction date, in the MMDDHHmmss format.
    • Amount — the value of the payment in minor units.
    • CURRENCY — IDR.
    • CHANNEL CODE — your Doku Mall ID.
  3. Select Submit.

A Payment Success response confirms you successfully simulated the shopper completing a payment.

You can expect a webhook notification with "eventCode":"AUTHORISATION" and "success":"true" from us.

Doku Wallet

Doku id Password PIN
1790586273 doKU**88 1234

EPS

Before accepting live EPS payments, test your integration by making payments using the following EPS issuers (paymentMethod.issuer).

Bank name Issuer ID
Bank Austria e6819e7a-f663-414b-92ec-cf7c82d2f4e5
BAWAG P.S.K. AG ba7199cc-f057-42f2-9856-2378abf21638
Dolomitenbank d5d5b133-1c0d-4c08-b2be-3c9b116dc326
Erste Bank und Sparkassen 3fdc41fc-3d3d-4ee3-a1fe-cd79cfd58ea3
Easybank AG eff103e6-843d-48b7-a6e6-fbd88f511b11
HYPO Tirol Bank AG 6765e225-a0dc-4481-9666-e26303d4f221
Posojilnica Bank eGen 65ef4682-4944-499f-828f-5d74ad288376
Raiffeisen Bankengruppe Österreich ee9fc487-ebe0-486c-8101-17dce5141a67
Schoellerbank AG 1190c4d1-b37a-487e-9355-e0a067f54a9f
Sparda Bank Wien 8b0bfeea-fbb0-4337-b3a1-0e25c0f060fc
Volksbanken e2e97aaa-de4c-4e18-9431-d99790773433
Volkskreditbank AG 4a0a975b-0594-4b40-9068-39f77b3a91f9

Gift cards

Type Number Security code Expiry month and year Optional
Givex gift card 6036280000000000000 ANY 12 2222
Generic gift card 6364530000000000 ANY 12 2222
SVS gift card 6006490000000000 ANY 12 2222
Fiserv (formerly ValueLink) gift card 777718270854480 ANY 12 2222

If the simulator asks for a Fiserv (formerly ValueLink) promo code, enter any value.

To test the balance check, make a test payment for an amount higher than EUR 50.

Intersolve test gift cards

Card Type Card Holder Name Card Number PIN
Gall & Gall Card 6064365010000000000 73737
Baby Gift Card 6064362200000000000 73737
Gift Card 6280501100000000000 73737
Kado Wereld 6064362510000000000 73737
Entertainment Card 6064361100000000000 73737
Plastix 4010100000000000000 73737
Webshop Giftcard 6064362070000000000 73737
Leasure Giftcard 6064362280000000000 73737
VVV Giftcard

6064364240000000000

737373
GiftForYou (Bloemen) 6064364710330000000 737373

giropay

Before making live giropay payments, use the following details to test your integration:

Bank Name BIC Customer name IBAN Account ID Bankleitzahl
Testbank Fiducia GENODETT488 Any DE36444488881234567890 1234567890 44448888

After selecting Testbank Fiducia, you are redirected to a page where you can select different statuses to simulate with. We recommend testing each giropay status code:

sc extensionSc importance
10 4000 The payment was successful.
20 2000,2100,2200,2300,2400,2500,2600,2700,3100,3900,4900 The payment was not successful.
30 4500 Status of the payment is unknown.
40 0 Bank is not unlocked for giropay.

Google Pay

To test Google Pay, log in to a Google account and create a Google Pay wallet with the details of a real card, not a test card. When you make a test payment, the card number is automatically mapped to our test card number starting with 4111, so the real card is not charged.

To test Google Pay with the 3D Secure flow, contact our Support Team.

iDEAL

Before accepting live iDEAL payments, test your integration by making payments using the following iDEAL issuers (paymentMethod.issuer). We recommend testing each iDEALPayment Result:

Payment Result iDEAL Issuer
Authorised 1121, 1151, 1152, 1153, 1154, 1155, 1156, 1157, 1158, 1159
Cancelled 1162
Pending 1161
Refused 1160

Interac

For Interac any email address can be provided, but the amount of the test transaction must be 1.00 CAD.

Klarna

Before accepting live payments, test your integration using the test environment and sample data provided by Klarna.

PayPal

For PayPal test payments use the personal account email of your PayPal sandbox account.

PaySafeCard

Card Number
0000 0000 0990 3417

SEPA Direct Debit

Account Name IBAN Country
A. Klaassen NL13TEST0123456789 NL
B. Klaassen NL36TEST0236169114 NL
C. Klaassen NL26TEST0336169116 NL
D. Klaassen NL16TEST0436169118 NL
E. Klaassen NL81TEST0536169128 NL
F. Klaassen NL27TEST0636169146 NL
G. Klaassen NL39TEST0736169237 NL
H. Klaassen NL82TEST0836169255 NL
I. Klaassen NL72TEST0936169257 NL
J. Klaassen NL46TEST0136169112 NL
K. Klaassen NL70TEST0736160337 NL
L. Klaassen NL18TEST0736162437 NL
M. Klaassen NL92TEST0736163433 NL
A. Schneider DE87123456781234567890 DE
B. Schneider DE92123456789876543210 DE
C. Schneider DE14123456780023456789 DE
D. Schneider DE36444488881234567890 DE
E. Schneider DE41444488889876543210 DE
F. Schneider DE60444488880023456789 DE
G. Schneider DE89888888881234567890 DE
H. Schneider DE94888888889876543210 DE
I. Schneider DE16888888880023456789 DE
A. Pacini IT60X0542811101000000123456 IT
A. Grand FR1420041010050500013M02606 FR
A. Martin ES9121000418450200051332 ES
W. Hurth AT151234512345678901 AT
H. Gasser CH4912345123456789012 CH
R. Paulsen DK8612341234567890 DK
B. Dalby NO6012341234561 NO
A. Bak PL20123123411234567890123456 PL
A. Andersson SE9412312345678901234561 SE

Sofort

Sofort does not have a specialized test environment. This means that you are redirected to the Sofort live environment even when making a payment from the Adyen test environment.
To test your integration, use the following details:

Bank Name Account Number Country PIN TAN
DemoBank Use any value DE Use any value Follow the instructions

Using a different account number (live data) will initiate a real payment. This payment will not be transferred to your account, and is therefore lost. It is not possible to reverse or refund this payment.

Trustly

Use the test credentials provided by Trustly. When prompted for a one-time passcode, copy the one-time passcode provided in the form.

When testing Trustly, we recommend that you specify the countryCode in your payment request. If you omit this field, the Trustly test environment will estimate your country using your IP address. If your country is not supported by Trustly, this can lead to errors with Trustly. Trustly recurring payments are currently only available in Sweden (SEK).

See also

  • Payment methods
  • Currency codes
  • Live endpoints

crusestunion.blogspot.com

Source: https://docs.adyen.com/development-resources/testing/test-card-numbers

0 Response to "How Easy to Get Approved by Adyen"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel