Skip to content

    Test environment

    Learn how to test your integration in the Netaxept test environment.

    Introduction

    The test environment is built for functional testing only and not for stress or load testing purposes. It is not allowed to run more than one transaction per second in the test environment.

    Overview

    Testing ensures that your API implementation towards Netaxept works as intended. You can test OK responses as well as transactions with errors.

    You must use the test environment url for testing your RESTful API integration:

    https://test.epayment.nets.eu/netaxept/

    Please also make sure, to use your Test Credentials: Netaxept Test API token, and Netaxept Test Admin Portal password.

    You can access the Netaxept Test Admin Portal here.

    Please note: The MerchantId for testing might differ from your MerchantId for production.

    Test amount and response codes

    In the Test environment, you may use any amount for testing purposes.

    However, if you test card payments with amounts ranging from 0.01–0.99 or 1.01–1.99, the transactions will not go through and you will receive an error message after sending the transaction for authorization.

    The response code is generated according to the decimals of the input amount. For example, the amount of 1.00 will return a response code of "00", while an amount of 1.52 will return "52".

    Occasionally, during testing in the Test environment, you may encounter an error message such as “Refused by issuer $TSTE” when using amounts less than 500 (e.g. 5 EUR) with decimals. In such cases, we recommend using amounts greater than 500 to ensure seamless testing.

    If you wish to test how your integration handles excessive authorization reattempt responses, such as "PB Transaction permanently blocked" please note that we have dedicated cards for this purpose. These cards trigger automatic blocks set by Netaxept based on the response codes. You can find these card numbers in the "Test cards" section.

    For additional information on managing authorization reattempts, please refer to the information available here.

    General information about response codes is available here.

    Additional payment methods

    While most of the card payments do not require any additional activation, other payment methods must be activated by adding the corresponding credentials into the test environment's Netaxept Admin.

    Test Cards

    Below you can find test cards that you can use when testing card payments via Netaxept in the test environment. Use the different cards to validate your solution's error handling during the different Netaxept operations.

    The first card table contains normal test cards which don’t support 3D Secure authentication and therefore transactions with these cards are processed as unauthenticated. If you want to test your integration with 3D Secure authentication flow, please refer to second card table below.

    Card payments made in the test environment won't be transferred or settled to your company's bank account.

    The expiry date for testing cards can be any date later than today. The Verification code can be any 3 digits.

    CardCard numberType of transactionError or other notesResponse
    Visa (Debit)4925000000000004AllNoneOK
    Visa (Debit)4925000000000087Register, Process(AUTH), Process(SALE)Register will work, Process(AUTH) and Process(SALE) will fail.OK/99
    Visa (Debit)4925000000000061Register, Process(AUTH), Process(CAPTURE)Register, Process(AUTH), Process(CAPTURE) will work.OK/OK/OK
    Visa (Debit)4925000000000061Register, Process(SALE)Register will work, but Process(SALE) will fail. Use this card to verify error handling of cards that have previously been stored successfully for Easy / Recurring payments, but now fails. Although Process(SALE) is a combination of of Process(AUTH) and Process(CAPTURE), the former will fail, while the two latter, and other Process operations will succeed.OK/99
    Visa (Debit)4925000000000079Register, Process(AUTH), Process(CAPTURE)Register and Process(AUTH) will work, but Process(CAPTURE) will fail.OK/OK/99
    Visa (Debit)4925000000000079Register, Process(SALE)Register and Process(SALE) will work.OK/99
    Mastercard (Debit)5413000000000000AllNoneOK
    Maestro (Debit)6761638084569584AllNoneOK
    Diners Club36000000000222AllNoneOK
    American Express375700000000002AllNoneOK
    Bring5566530000000001AllNoneOK
    Dankort5019994001300153AllNoneOK

    To test different authentication (EMV 3DS / 3DS2) scenarios for your integration, use the test cards below.

    These cards support two primary authentication flows that EMV 3DS support:

    • Frictionless flow occurs when the issuer authenticates the cardholder without cardholder involvement by evaluating the transaction’s risk level using risk based authentication.
    • Challenge flow occurs when the issuer assesses the risk of the transaction during the frictionless flow and determines that the transaction requires additional cardholder authentication through application of an SCA challenge.
    CardCard numberFlowAuthenticationType of transactionError or other notesResponse
    Visa, Password: Secret33!4012000000012003001ChallengeYRegister+Auth or SaleNoneOK
    Visa4016360000000093ChallengeY, N, A, URegister+Auth or SaleNoneOK
    Mastercard5188340000000060ChallengeY, N, A, URegister+Auth or SaleNoneOK
    Visa4012000000012011004FrictionlessYRegister+Auth or SaleNoneOK
    Visa4012000000012011012FrictionlessNRegister+Auth or SaleRegister ok, Terminal will fail.Terminal Fail
    Visa4012000000012011053FrictionlessARegister+Auth or SaleRegister ok, Terminal will fail.Terminal Fail
    Visa4012000000012011020FrictionlessURegister+Auth or SaleRegister ok, Terminal will fail.Terminal Fail
    Visa4012000000012011038FrictionlessRRegister+TerminalRegister ok, Terminal will fail.Terminal Fail
    Mastercard, Use for SDK test5544330000000010FrictionlessYRegister+Auth or SaleNoneOK

    Test cards for testing excessive authorization responses

    Netaxept offers a mechanism for blocking transactions based on specific response codes and the number of reattempts. To test different authorization reattempt scenarios and fine-tune your retry logic, you can use the following test cards in your test transactions. When you make a transaction with these cards, you'll receive the following response codes after excessive reattempts, depending on the amount used:

    • PB (Permanent block): Do not try again.
    • TB (Temporary block): Try again later.

    Any transaction-related card block applied during testing is automatically removed after two days. That way, it is ensured that the card number in question becomes available again for further testing.

    CardCard numberType of transactionResponse
    Visa4761342534612467AllPB/TB
    Visa4761342534612475AllPB/TB
    Visa4761342534612483AllPB/TB
    Visa4761342534612491AllPB/TB
    Visa4761342534612509AllPB/TB
    Visa4761342534612517AllPB/TB
    Visa4761342534612525AllPB/TB
    Visa4761342534612533AllPB/TB
    Visa4761342534612541AllPB/TB

    Reattempts for both Process(AUTH) and Process(SALE) with error codes in the same category will result in either a PB (permanent block) or TB (temporary block) response. The specific outcome depends on the error code category and the number of reattempts.

    Test Direct banks

    Below you can find both merchant and end-user credentials that you can use when testing direct bank payments via Netaxept in test environment. Please note that these are general credentials provided by each bank and are subject to change over time. Also, functionalities available for testing can vary per bank.

    Add the merchant credentials in the test environment’s Netaxept Admin on the "Options" => "Agreements" page. End-user credentials should be used on the web bank site.

    Bank nameMerchant credentialsEnd-user credentials
    Finnish direct banks via PaytrailCurrency: EUR, Merchant ID: 375917, Authentication hash: SAIPPUAKAUPPIASUse the same credentials as mentioned below for each Finnish bank.
    AktiaCurrency: EUR, Seller Id: 1111111111111, MAC Key: 1234567890123456789012345678901234567890123456789012345678901234, Key Version: 0001Username: 12345678, Password 1: 123456, Password 2: 1234, Password 3: 1234
    Danske Bank FICurrency: EUR, Service Provider Id: 000000000000, MAC Key: jumCLB4T2ceZWGJ9ztjuhn5FaeZnTm5HpfDXWU2APRqfDcsrBs8mqkFARzm7uXKd, Business Online Agreement number: 788817User needs to use their own Danske Bank credentials. Amounts are not captured from the user's account.
    Handelsbanken FICurrency: EUR, Seller Id: 0000000000, Seller Account: 448710-126, MAC Key: 11111111111111111111Select “Avaintunnuskortilla”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456
    Nordea FICurrency: EUR, Merchant ID: 12345678, MAC Key: LEHTI, Key version: 0001Follow the instructions in demo bank.
    Oma SäästöpankkiCurrency: EUR, Seller Id: 0000000000, MAC Key: 11111111111111111111Select “Käytä verkkopankkitunnuksia”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456
    POP PankkiCurrency: EUR, Seller Id: 0000000000, MAC Key: 11111111111111111111Select “Avaintunnuskortilla”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456
    S-PankkiCurrency: EUR, Service Provider Id: SPANKKIESHOPID, Account No.: FI4139390001002369, MAC Key: SPANKKI, Algorithm version (01,03): 03Select “Tunnuslukutaulukolla”, Username: 12345678, Password: 123456, Password 2: 1234, Password 3: 1234
    SäästöpankkiCurrency: EUR, Seller Id: 0000000000, MAC Key: 11111111111111111111Select “Avaintunnuskortilla”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456
    ÅlandsbankenCurrency: EUR, Receiver id: AABESHOPID, Account No: FI7766010001130855, MAC: PAPEGOJA, Algorithm version (01,03): 03Go to Kirjaudu taulukolla section, Username: 12345678, Password 1: 123456, Password 2: 1234, Change the account, Password 3: 1234

    Test Invoices and Instalments

    Below you can find end-user credentials that you can use when testing invoice and instalment payments via Netaxept in test environment. Please note that these are general credentials provided by each invoice/instalment service provider and are subject to change over time.

    Most of the invoice/instalment service providers provide only merchant-specific credentials instead of generic test credentials for all merchants. Due to this, to be able to test invoice and instalment payments in test environment, please apply for merchant credentials from your chosen invoice/instalment service provider. After that add the merchant credentials in the test environment's Netaxept Admin on the "Options" => "Agreements" page.

    NameEnd-user credentials
    RivertyNo generic credentials available
    Walleyhttps://dev.walleypay.com/docs/checkout/test-data/

    Test Gift cards

    Below you can find test gift cards that you can use when testing gift card payments via Netaxept in the test environment.

    Please note that you may need to have separate merchant setup in your test merchant account to be able to run gift card payments.

    NameCard numberVerification codeType of transactionError or other notesResponse
    PBS gift card 6075725999906991923 726AllThis card has a balance of 1,00 in a given currency, e.g. 1 DKK. If the transaction amount is bigger than this, the payment window will request the amount is split, and the rest of the amount is paid with another payment method. To test without split payment, adjust the test amount to 1 (e.g. 1 DKK) or less.OK
    Nets gift card / Gavekort 9578351001074700000803SALE onlyUse this to test NOK transactions.OK
    Nets gift card / Gavekort 9578351001074700000745SALE onlyUse this to test NOK transactions.OK
    Nets gift card6366773500000000000142SALE onlyUse this to test EUR transactions.OK

    Was this helpful?

    What was your feeling about it?