--- title: "Alternative payment methods test credentials" description: "Test your integration with test credentials for other payment methods." url: "https://docs.adyen.com/development-resources/test-cards-and-credentials/alternative-payment-method-credentials" source_url: "https://docs.adyen.com/development-resources/test-cards-and-credentials/alternative-payment-method-credentials.md" canonical: "https://docs.adyen.com/development-resources/test-cards-and-credentials/alternative-payment-method-credentials" last_modified: "2026-05-23T12:56:20+02:00" language: "en" --- # Alternative payment methods test credentials Test your integration with test credentials for other payment methods. [View source](/development-resources/test-cards-and-credentials/alternative-payment-method-credentials.md) Test alternative payment methods with the test credentials provided on this page. ## Requirements | Requirement | Description | | -------------------- | ------------------------------------------------------------------------------------------- | | **Integration type** | Use test credentials to test your existing [online payments](/online-payments) integration. | ## 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 | Payment PIN | | --------------------------------- | ------ | ----------- | | | 111111 | 111111 | ### Alipay Hong Kong | Username | PIN | Payment PIN | | -------------------------- | ------- | ----------- | | | a111111 | b111111 | ## Apple Pay For a full list of test cards and instructions how to add these to your test device, see [Sandbox testing](https://developer.apple.com/apple-pay/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/region | 3DS enrolled | Allows create mandate | Allows create network token | | ---------------- | ---------- | ------- | ---- | --------------------------- | ------------------- | -------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | 4622943127237569 | 123456 | 12/2024 | 744 | Success | Visa | IN | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | | 4000000000000002 | 123456 | 12/2029 | 123 | Success | Visa | IN | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | | 5400000000000005 | 123456 | 12/2029 | 123 | Success | Mastercard | IN | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | | 370000000000002 | 123456 | 12/2029 | 1234 | Success | American Express | IN | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | | 6522000000000006 | 123456 | 12/2029 | 123 | Success | Rupay | IN | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | | 5252520200034065 | 112223 | 12/2029 | 123 | PBE10002 Insufficient funds | Mastercard - Credit | IN | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-x-](/user/data/smileys/emoji/x.png "-x-") | ![-x-](/user/data/smileys/emoji/x.png "-x-") | ## BLIK To test BLIK in the TEST environment, use the following 6-digit BLIK codes to simulate different scenarios: | BLIK Code | Error code | Error description | | --------- | ----------------------- | --------------------------------------------------- | | 999 000 | **AUTHORIZED** | Regular authorisation. | | 912 111 | **ALIAS\_DECLINED** | Issuer declined due to security. | | 927 111 | **TAS\_DECLINED** | The transaction has been declined. | | 934 111 | **USER\_DECLINED** | Shopper declined the transaction in the Issuer app. | | 969 111 | **SEC\_DECLINED** | Declined due to security. | | 956 111 | **SYSTEM\_ERROR** | System error. | | 961 111 | **GENERAL\_ERROR** | General error. | | 960 111 | **INSUFFICIENT\_FUNDS** | Insufficient funds. | | 989 111 | **TIMEOUT** | Timeout on the Issuer end. | | 990 111 | **LIMIT\_EXCEEDED** | BLIK transaction limit exceeded. | | 949 111 | **USER\_TIMEOUT** | Shopper did not approve the transaction in time. | | 902 111 | **ISSUER\_DECLINED** | Issuer declined. | ### Testing One-Click payments For specific One-Click scenarios, use the following amounts: * x.02 PLN (for example 10.02 PLN): regular transaction, shopper is not tokenized. * x.12 PLN: shopper is tokenized, can be used for One-Click (for example transactions without a BlikCode). * x.42 PLN: use for One-Click transactions, payment is authorized, but shopper is de-tokenized, so cannot be used again for One-Click. ### Testing refusal reasons The following amounts can be used for specific refusal reasons: | Amount | Error code | Error description | | ------ | ----------------------- | --------------------------------------------------------------------------------------------------------------------------- | | 288.00 | **ALIAS\_DECLINED** | The Issuer declines to process the Transaction with the Alias for security reasons. | | 192.00 | **TAS\_DECLINED** | Ticket Authorisation System declined. | | 144.00 | **USER\_DECLINED** | Declined by the user in Mobile Application. | | 216.00 | **SEC\_DECLINED** | Declined for security reasons. | | 264.00 | **SYSTEM\_ERROR** | The system error. | | 360.00 | **GENERAL\_ERROR** | The general error, must be applied in the case of unspecified error in the remaining items on this list. | | 120.00 | **INSUFFICIENT\_FUNDS** | Insufficient funds. | | 312.00 | **TIMEOUT** | It is returned in the case of the timeout in the Issuer’s systems except for the communication with the Mobile Application. | | 96.00 | **LIMIT\_EXCEEDED** | The limit exceeded. | | 336.00 | **USER\_TIMEOUT** | It is returned in the case of the timeout in the Mobile Application of the Issuer. | ## 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](https://en.wikipedia.org/wiki/Cadastro_de_Pessoas_Físicas) or [CNPJ](https://en.wikipedia.org/wiki/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](/payment-methods/boleto-bancario/api-only). | ## Brazil vouchers | Card type | Card number | Expiry date | CVC | | ------------------------------ | ------------------- | ----------- | --- | | Ticket (Edenred - Alimentação) | 6033 4225 5384 5003 | Any | 418 | | Ticket (Edenred - Refeição) | 6026 5145 1530 4787 | Any | 265 | | Pluxee (Alimentação) | 6033 8902 5703 4050 | 11/2034 | 164 | | Pluxee (Refeição) | 6060 7101 0440 1649 | 11/2032 | 507 | | Vale Refeição | 6370 3671 0000 0993 | 01/2032 | 520 | | Elo voucher | 5067 2300 0000 0002 | 03/2030 | 737 | | Visa voucher | 4058 8600 0000 0000 | 03/2030 | 737 | | Mastercard voucher | 2340 6300 0000 0009 | 03/2030 | 737 | ## Cash Ticket | Card Number | | ------------------- | | 0000 0000 0990 3188 | ## Doku Use the following simulators to test payment completion via Indonesian bank transfers and convenience stores. * [Alfamart](#alfamart) * [BCA](#bca) * [BNI](#bni) * [BRI](#bri) * [CIMB Bank Transfer](#cimb-bank-transfer) * [Danamon Bank Transfer](#danamon-bank-transfer) * [Indomaret](#indomaret) * [Mandiri Bank Transfer](#mandiri-bank-transfer) * [Permata 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](https://staging.doku.com/VASimulator/AlfaAction_show.doku). 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](https://staging.doku.com/VASimulator/AlfaAction_show.doku). 2. Select the **Payment** tab and enter: * **Customer** — the **vaNumber**. * **Amount** — the value of the payment in [minor units](/development-resources/currency-codes). * **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 webhook event from us for when the shopper completed the payment. #### Get a webhook event for the completed payment This step simulates the webhook event for when the shopper completed the payment. 1. Go to the [Alfa Simulator](https://staging.doku.com/VASimulator/AlfaAction_show.doku). 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 event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://staging.doku.com/VASimulator/BCAAction_show.doku). 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](https://staging.doku.com/VASimulator/BCAAction_show.doku). 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](/development-resources/currency-codes). 3. Select **Submit**. A **Payment Success** response confirms you successfully simulated the shopper completing a payment. You can expect a [webhook event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://portalbeta.bni-ecollection.com/partner/simulator/payment-simulator/index). 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](/development-resources/currency-codes). 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 event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://staging.doku.com/VASimulator/BriAction_show.doku). 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](https://staging.doku.com/VASimulator/BriAction_show.doku). 2. Select the **Payment** tab and enter: * **Customer** — the 16-digit `action.reference` value. * **Amount** — the value of the payment in [minor units](/development-resources/currency-codes). * **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 event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://staging.doku.com/VASimulator/CimbAction_show.doku). 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](https://staging.doku.com/VASimulator/CimbAction_show.doku). 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](/development-resources/currency-codes). 3. Select **Submit**. A **Payment Success** response confirms you successfully simulated the shopper completing a payment. You can expect a [webhook event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://staging.doku.com/VASimulator/DanamonAction_show.doku). 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](https://staging.doku.com/VASimulator/DanamonAction_show.doku). 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](/development-resources/currency-codes). * **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 event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://staging.doku.com/VASimulator/IndomartAction_show.doku). 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](https://staging.doku.com/VASimulator/IndomartAction_show.doku). 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 event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://staging.doku.com/VASimulator/MandiriAction_show.doku). 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](https://staging.doku.com/VASimulator/MandiriAction_show.doku). 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](/development-resources/currency-codes). * **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 event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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](https://staging.doku.com/VASimulator/PermataAction_show.doku) 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](https://staging.doku.com/VASimulator/PermataAction_show.doku) 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](/development-resources/currency-codes). * **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 event](/development-resources/webhooks/webhook-types#event-codes) with `eventCode` set to **AUTHORISATION** and `success` set to **true**. ### 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 issuer (**paymentMethod.issuer**). | Bank name | Issuer ID | | -------------- | ------------------------------------ | | PSA Bank Group | b631e29a-097e-4400-be52-762b6d772b38 | ## Gift cards | Type | Number | Security code | Expiry month and yearOptional | | ------------------------------------- | ------------------- | ------------- | ----------------------------- | | 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 | 7777182708544835 | 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 | Any | 6064365010000000000 | 73737 | | Baby Gift Card | Any | 6064362200000000000 | 73737 | | Gift Card | Any | 6280501100000000000 | 73737 | | Kado Wereld | Any | 6064362510000000000 | 73737 | | Entertainment Card | Any | 6064361100000000000 | 73737 | | Plastix | Any | 4010100000000000000 | 73737 | | Webshop Giftcard | Any | 6064362070000000000 | 73737 | | Leasure Giftcard | Any | 6064362280000000000 | 73737 | | VVV Giftcard | Any | 6064364295385017427 | 737373 | | GiftForYou (Bloemen) | Any | 6064364710330000000 | 737373 | ## Google Pay To start testing Google Pay, log in to a Google account and create a Google Pay wallet. There are two approaches to using this wallet for testing: * **Enroll in test card suite** Enroll your wallet in Google's [test card suite](https://developers.google.com/pay/api/android/guides/resources/test-card-suite). Test card suite pre-populates your wallet with a group of cards to use in the TEST environment. These are related to Adyen's collection of test cards, and cover scenarios including: * Cards stored as FPAN * Cards stored as DPAN (only when testing through native Android and Chrome on Android) * Cards enabled for 3DS2 When you start the payment flow and open the list of test cards, each card is marked with the applicable scenario. * **Without test card suite** You upload real credit cards to your wallet, which are mapped to one of Adyen's [test cards](/development-resources/test-cards-and-credentials/test-card-numbers) of the same brand. Your card is not charged. To test 3D Secure 2, you must use American Express or Discover cards, which trigger 3D Secure 2 challenge flows in the test environment. You cannot use any other card brands. You can check the status of a Google Pay test payment in your [Customer Area](https://ca-test.adyen.com/) > **Transactions** > **Payments**, whether you used a card from the test card suite or or not. Remember that cards outside the test card suite are mapped to an Adyen test card of the same brand. ## iDEAL The iDEAL test environment is unreliable and may not always work to test your changes. We recommend doing live penny tests to verify your integration. ### Request iDEAL for the live environment Before you can accept live payments, you need to [add iDEAL](/payment-methods/add-payment-methods) in your [live Customer Area](https://ca-live.adyen.com/). ### Live Penny Testing 1. Get a live bank account from one of the iDEAL issuers. 2. Create an iDEAL payment on live and redirect to the iDEAL Payment Page. 3. Scan the QR code on the iDEAL Payment Page or Click **Select your bank** to navigate to a list of issuers. 4. Authorise the payment. 5. Check the status of test payments in your [live Customer Area](https://ca-live.adyen.com/) > **Transactions** > **Payments**. ### Testing on the Test environment In case the iDEAL test environment is up and running, it may be possible to test using your test account. You are always redirected to a test payment page where you can simulate different iDEAL result codes. On the payment page: 1. Click **Select your bank** to navigate to a list of issuers. 2. Select the **TESTNL2A** issuer. 3. Select the test simulation you want to run according to the following table: | Test simulation | `resultCode` produced | | ------------------------- | --------------------- | | Success | Authorised | | Cancellation | Canceled | | Cancellation before login | Canceled | | Expiration | Pending or Received | | Failure | Refused | When possible, we recommend that you test each scenario before you go live, otherwise you should perform a **Live Penny Test** to verify your integration. Check the status of test payments in your [Customer Area](https://ca-test.adyen.com/) > **Transactions** > **Payments**. ## Interac For Interac any email address can be provided, but the amount of the test transaction must be 1.00 CAD. ## Klarna Use the [test environment and sample data provided by Klarna](https://docs.klarna.com/resources/test-environment/). ## MobilePay MobilePay cannot be tested in the test environment. You must make penny test (low-amount) payments in the live environment. 1. Submit a request for MobilePay in your [live Customer Area](https://ca-live.adyen.com/). 2. After MobilePay is added to your live Customer Area, do the following for each test payment: 1. Make a MobilePay payment for a low amount. 2. Get the [**AUTHORISATION** webhook](/development-resources/webhooks/webhook-types/#default-event-codes) on your server. It includes the status of the payment. 3. In your live Customer Area, go to **Transactions** > **Payments** to see the status of the payment. ### Test payouts to MobilePay wallets The MobilePay payout feature is experimental, and supported only with the `/payments` endpoint. Do the following to test MobilePay payouts: 1. Get a test app following the instructions in the [VippsMobilePay documentation](https://developer.vippsmobilepay.com/docs/knowledge-base/test-environment/#app-installation). When prompted for a phone number and NIN (national identity number), use one of the following sets: * NIN 0407640091\ Phone +45 22105837 * NIN 0702860109\ Phone +45 34817154 * NIN 0111500196\ Phone +45 73920021 2. Test your integration end-to-end: * Make a test payment that generates a payout token, using the Vipps MobilePay test app to simulate the customer side. * Check that you receive and process the recurring lifecycle webhook. * Make a [Transfers API](https://docs.adyen.com/api-explorer/transfers/latest/overview) request using the token that you receive in the webhook. ## Oney 3x 4x You must use different test credentials for France and Spain. ### 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 ## Pay by Bank (Europe) You can test payments in the following supported regions: Use the relevant test credentials and test issuer IDs, where available. #### UK For the UK, where you can show the issuer list in the payment form, use the following test issuer IDs: | Bank name | Issuer ID | | -------------- | -------------------------------------------- | | Tink Demo Bank | **uk-demobank-open-banking-handoff** | | Tink Demo Bank | **uk-demobank-open-banking-redirect** | | Tink Demo Bank | **uk-demobank-open-banking-redirect-aispis** | When you send a test payment and are redirected to our open banking partner Tink, log in with the following test credentials for the UK: | Scenario | Username | Password | | -------------------- | --------- | -------- | | Approved | u83646180 | rlf446 | | Authentication error | u92721594 | nbs589 | | Temporary error | u91902655 | jtx720 | For an Approved test scenario, you will see two checking accounts. Select the first checking account (ending in 285) for payment amounts greater than GBP 150, or the second checking account (ending in 327) for amounts less than GBP 150. #### Germany When you send a test payment and are redirected to our open banking partner Tink, log in with the following test credentials for Germany: | Scenario | Username | Password | | -------------------- | --------- | -------- | | Approved | u83188312 | zhx571 | | Authentication error | u92721594 | nbs589 | | Temporary error | u91902655 | jtx720 | #### France When you send a test payment and are redirected to our open banking partner Tink, log in with the following test credentials for France: | Scenario | Username | Password | | -------------------- | --------- | -------- | | Approved | u77894411 | mzw990 | | Authentication error | u92721594 | nbs589 | | Temporary error | u91902655 | jtx720 | #### Finland When you send a test payment and are redirected to our open banking partner Tink, log in with the following test credentials for Finland: | Scenario | Username | Password | | -------------------- | --------- | -------- | | Approved | u06516046 | kam413 | | Authentication error | u92721594 | nbs589 | | Temporary error | u91902655 | jtx720 | ## 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/region | | ------------ | ---------------------------- | -------------- | | 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 | ## Trustly Use the [test credentials provided by Trustly](https://test.trustly.com/testing/). 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](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments#request-countryCode) in your payment request. If you omit this field, the Trustly test environment will estimate your country/region using your IP address. If your country/region is not [supported by Trustly](/payment-methods/trustly), this can lead to errors. ## Vipps Vipps cannot be tested in the test environment. You must make penny test (low-amount) payments in the live environment. ### Request for Vipps in the live environment Before you can accept live Vipps payments, you need to submit a request for Vipps in your [live Customer Area](https://ca-live.adyen.com/). After Vipps is added to your live Customer Area, do the following for each test payment: 1. Make a Vipps payment for a low amount. 2. Get the [**AUTHORISATION** webhook](/development-resources/webhooks/webhook-types/#default-event-codes) on your server. It includes the status of the payment. 3. In your live Customer Area, go to **Transactions** > **Payments** to see the status of the payment. ## See also * [Payment methods](/payment-methods) * [Currency codes](/development-resources/currency-codes) * [Live endpoints](/development-resources/live-endpoints)