The new site can be found at https://developers.nets.eu/netaxept/en-EU/docs/
This site will no longer be maintained, but will stay live for a while for forwarding purposes.
Testing
Testing ensures that your API implementation towards Netaxept works as intended and can handle properly both OK responses and transactions with errors. You can use Netaxept’s test environment for the testing purposes. It is available 24/7 with the exception of service interruptions that are not communicated in advance.
- In the test environment, API calls via REST interface need to be sent to an address starting with https://test.epayment.nets.eu
- Login page for Netaxept Admin in the test environment is https://test.epayment.nets.eu/admin
- Go to Netaxept Admin User Guide >
Test amounts and response codes
In the test environment, you can test using any sums you like. However, please note that 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 transaction to authorization. The response code is generated in accordance with the decimals in the input sum. For example, the sum of 1.00 will return a response code of "00" and 1.52 will return "52". Addition to this, you may occasionally receive an error “Refused by issuer $TSTE” when testing in test environment and using 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. Read more about response codes
Credentials
In the test environment, you need to use test merchant credentials received from Nets and the payment method details available below or received directly from your chosen payment service provider.
Most of the card payments don’t require any additional activation. If you wish to test other payment methods, please activate these by adding the corresponding credentials in the test environment's Netaxept Admin on the "Options" => "Agreements" page.
Payment 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.
Please note that card payments made in the test environment won't be transferred or settled to your company's bank account.
| Card number | Expiry date | Verification code | Type of transaction | Error or other notes | Response |
| | > today | Any 3 digits | All | None | OK |
| | > today | Any 3 digits | Register + Auth or Sale | REGISTER will go ok, but PROCESS (Auth) or PROCESS (Sale) will fail. | OK/99 |
| | > today | Any 3 digits | Register + Auth + Capture | REGISTER + PROCESS (Auth) + PROCESS (Capture) will go OK. | OK/OK/OK |
| | > today | Any 3 digits | Register + Sale | REGISTER will go ok, 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. Note that although PROCESS (Sale) is a combination of of AUTH and CAPTURE, the former will fail, while the two latter, and the other Process operations will succeed. | OK/99 |
| | > today | Any 3 digits | Register + Auth + Capture | REGISTER and PROCESS (Auth) will go ok, but the PROCESS (Capture) will fail. | OK/OK/99 |
| Visa (Debit) 4925000000000079 | > today | Any 3 digits | Register + Sale | REGISTER and PROCESS (Sale) will go OK. | OK/99 |
| Mastercard (Debit) | > today | Any 3 digits | All | None | OK |
| Maestro (Debit) | > today | Any 3 digits | All | None | OK |
| Diners Club | > today | Any 3 digits | All | None | OK |
| American Express | > today | Any 3 digits | All | None | OK |
| Bring | > today | Any 3 digits | All | None | OK |
| Dankort 5019994001300153 | > today | Any 3 digits | All | None | OK |
To test different authentication (EMV 3DS / 3DS2) scenarios for your integration, use the following test cards below.
When testing with these cards, it is good to note that they 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 number | Flow | Authentication | Expiry date | Verification code | Type of transaction | Error or other notes | Response |
| Visa 4012000000012003001 Password: Secret33! | Challenge | Y | > Today | Any 3 digits | Register+Auth or Sale | None | OK |
| Visa 4016360000000093 | Challenge | Y, N, A, U | > Today | Any 3 digits | Register+Auth or Sale | None | OK |
| Mastercard 5188340000000060 | Challenge | Y, N, A, U | > Today | Any 3 digits | Register+Auth or Sale | None | OK |
| Visa 4012000000012011004 | Frictionless | Y | > Today | Any 3 digits | Register+Auth or Sale | None | OK |
| Visa 4012000000012011012 | Frictionless | N | > Today | Any 3 digits | Register+Auth or Sale | Register will go ok, | Terminal Fail |
| Visa 4012000000012011053 | Frictionless | A | > Today | Any 3 digits | Register+Auth or Sale | Register will go ok, However Terminal will fail | Terminal Fail |
| Visa 4012000000012011020 | Frictionless | U | > Today | Any 3 digits | Register+Auth or Sale | Register will go ok, However Terminal will fail | Terminal Fail |
| Visa 4012000000012011038 | Frictionless | R | > Today | Any 3 digits | Register+Terminal | Register will go ok, | Terminal Fail |
| Mastercard 5544330000000011 Use for SDK test | Frictionless | Y | > Today | Any 3 digits | Register+Auth or Sale | None | OK |
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.
| Card number | Expiry date | Verification code | Type of transaction | Error or other notes | Response |
| PBS gift card 6075725999906991923 | N/A | 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 9578351001074700013 | N/A | 803 | SALE only | Use this to test NOK transactions. | OK |
| Nets gift card / Gavekort 9578351001074700021 | N/A | 745 | SALE only | Use this to test NOK transactions. | OK |
| Nets gift card 6366773500000000136 | N/A | 142 | SALE only | Use this to test EUR transactions. | OK |
BankAxess
| Name | Social security number | Security code | Password | Response |
| | 22128011111 | otp | qwer1234 | OK |
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 in the web bank site.
| Bank name | Merchant credentials | End-user credentials |
| Finnish direct banks via Paytrail | Currency: EUR | Use the same credentials as mentioned below for each Finnish bank. |
| Aktia | Currency: EUR | Username: 12345678 |
| Danske Bank FI | Currency: EUR | User needs to use their own Danske Bank credentials. Amounts are not captured from the user's account. |
| Handelsbanken FI | Currency: EUR | Username: 11111111 / 22222222 |
| Nordea FI | Currency: EUR | Credentials are prefilled in "Code card" section. Password 2: 1234 |
| Oma Säästöpankki | Currency: EUR | Username: 11111111 / 22222222 |
| OP | Currency: EUR | Username: 123456 |
| POP Pankki | Currency: EUR | Username: 11111111 / 22222222 |
| S-Pankki | Currency: EUR | Username: 12345678 |
| Säästöpankki | Currency: EUR | Username: 11111111 / 22222222 |
| Ålandsbanken | Currency: EUR | Go to "Kirjaudu taulukolla" section. |
Invoice 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.
| Name | End-user credentials |
| AfterPay | No generic credentials available |
| Collector | https://merchant.collectorbank.se/integration/b2c/general-information/test-persons/ |
| Klarna | https://developers.klarna.com/en/se/kpm/test-credentials (Switch country on top right corner) |