Learn how to test your integration in the Netaxept test environment.
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.
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:
Please also make sure, to use your Test Credentials: Netaxept Test API token, and Netaxept Test Admin Portal password.
Please note: The
MerchantId for testing might differ from your
MerchantId for production.
Test amount and response codes
In the test environment you can test with any sums you like.
However, if you test card payments with sums of 0.01–0.99 or 1.01–1.99, the transaction will not go through and you will receive an error after sending the transaction to authorization.
The response code is generated according to the decimals of the input sum. For example, the sum of 1.00 will return a response code of "00" and 1.52 will return "52".
You may occasionally receive an error “Refused by issuer $TSTE” when testing in test environment with amounts less than 500 (for example 5 euros) with decimals. In this case, we recommend you to use amounts more than 500 to continue the regular testing.
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.
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.
|Card||Card number||Type of transaction||Error or other notes||Response|
|Visa (Debit)||4925000000000087||Register, Process(AUTH), Process(SALE)||Register will work, Process(AUTH) and Process(SALE) will fail.||OK/99|
|Visa (Debit)||4925000000000061||Register, Process(AUTH), Process(CAPTURE)||Register, Process(AUTH), Process(CAPTURE) will work.||OK/OK/OK|
|Visa (Debit)||4925000000000061||Register, 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)||4925000000000079||Register, Process(AUTH), Process(CAPTURE)||Register and Process(AUTH) will work, but Process(CAPTURE) will fail.||OK/OK/99|
|Visa (Debit)||4925000000000079||Register, Process(SALE)||Register and Process(SALE) will work.||OK/99|
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.
|Card||Card number||Flow||Authentication||Type of transaction||Error or other notes||Response|
|Visa, Password: Secret33!||4012000000012003001||Challenge||Y||Register+Auth or Sale||None||OK|
|Visa||4016360000000093||Challenge||Y, N, A, U||Register+Auth or Sale||None||OK|
|Mastercard||5188340000000060||Challenge||Y, N, A, U||Register+Auth or Sale||None||OK|
|Visa||4012000000012011004||Frictionless||Y||Register+Auth or Sale||None||OK|
|Visa||4012000000012011012||Frictionless||N||Register+Auth or Sale||Register ok, Terminal will fail.||Terminal Fail|
|Visa||4012000000012011053||Frictionless||A||Register+Auth or Sale||Register ok, Terminal will fail.||Terminal Fail|
|Visa||4012000000012011020||Frictionless||U||Register+Auth or Sale||Register ok, Terminal will fail.||Terminal Fail|
|Visa||4012000000012011038||Frictionless||R||Register+Terminal||Register ok, Terminal will fail.||Terminal Fail|
|Mastercard, Use for SDK test||5544330000000010||Frictionless||Y||Register+Auth or Sale||None||OK|
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 name||Merchant credentials||End-user credentials|
|Finnish direct banks via Paytrail||Currency: EUR, Merchant ID: 375917, Authentication hash: SAIPPUAKAUPPIAS||Use the same credentials as mentioned below for each Finnish bank.|
|Aktia||Currency: EUR, Seller Id: 1111111111111, MAC Key: 1234567890123456789012345678901234567890123456789012345678901234, Key Version: 0001||Username: 12345678, Password 1: 123456, Password 2: 1234, Password 3: 1234|
|Danske Bank FI||Currency: EUR, Service Provider Id: 000000000000, MAC Key: jumCLB4T2ceZWGJ9ztjuhn5FaeZnTm5HpfDXWU2APRqfDcsrBs8mqkFARzm7uXKd, Business Online Agreement number: 788817||User needs to use their own Danske Bank credentials. Amounts are not captured from the user's account.|
|Handelsbanken FI||Currency: EUR, Seller Id: 0000000000, Seller Account: 448710-126, MAC Key: 11111111111111111111||Select “Avaintunnuskortilla”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456|
|Nordea FI||Currency: EUR, Merchant ID: 12345678, MAC Key: LEHTI, Key version: 0001||Follow the instructions in demo bank.|
|Oma Säästöpankki||Currency: EUR, Seller Id: 0000000000, MAC Key: 11111111111111111111||Select “Käytä verkkopankkitunnuksia”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456|
|OP||Currency: EUR, Invoicer Id: Esittelymyyja, MAC Key: Esittelykauppiaansalainentunnus, MAC Key: Esittelykauppiaansalainentunnus||Username: 123456, Password: 7890, Password 2: 1234|
|POP Pankki||Currency: EUR, Seller Id: 0000000000, MAC Key: 11111111111111111111||Select “Avaintunnuskortilla”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456|
|S-Pankki||Currency: EUR, Service Provider Id: SPANKKIESHOPID, Account No.: FI4139390001002369, MAC Key: SPANKKI, Algorithm version (01,03): 03||Select “Tunnuslukutaulukolla”, Username: 12345678, Password: 123456, Password 2: 1234, Password 3: 1234|
|Säästöpankki||Currency: EUR, Seller Id: 0000000000, MAC Key: 11111111111111111111||Select “Avaintunnuskortilla”, Username: 11111111 / 22222222, Password 1: 123456, Password 2: 123456, Password 3: 123456|
|Ålandsbanken||Currency: EUR, Receiver id: AABESHOPID, Account No: FI7766010001130855, MAC: PAPEGOJA, Algorithm version (01,03): 03||Go to "Kirjaudu taulukolla" section, Username: 12345678, Password 1: 123456, Password 2: 1234, Change the account, Password 3: 1234|
|Name||Social security number||Security code||Password||Response|
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.
|AfterPay||No generic credentials available|
|Klarna||https://developers.klarna.com/en/se/kpm/test-credentials (Switch country on top right corner)|
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.
|Name||Card number||Verification code||Type of transaction||Error or other notes||Response|
|PBS gift card||6075725999906991923||726||All||This 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||9578351001074700000||803||SALE only||Use this to test NOK transactions.||OK|
|Nets gift card / Gavekort||9578351001074700000||745||SALE only||Use this to test NOK transactions.||OK|
|Nets gift card||6366773500000000000||142||SALE only||Use this to test EUR transactions.||OK|