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.

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.

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.

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.

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.

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.

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.