Test Environment

Overview

During the implementation phase of the integrations, as well as in the plugin tests, a test area is made available, with the data necessary to make calls to XPay and payment cards to simulate purchases, in particular:

• Api-Key: the apikey is the key and identifying parameter of the merchant's terminal, which must be passed in the header of each API call. XPay provides a series of apikey divided by usable functionality. In production, this key can be recovered from the merchant's back office.
• Payment cards: in the test area it is possible to use specific cards to simulate positive or negative payments.

It is always recommended to run tests before going into production. Also for plugins, Nexi invites you to carry out payment tests to verify that there are no problems with the notifications sent by Nexi servers, which could be filtered by firewalls or other systems; to verify that there are no incompatibilities with third party plugins installed in the CMS.

At this stage, in case of integration difficulties or errors returned by the plugins, please refer to the support contacts at the bottom left.

X-Api-Key

Here are the api-keys that can be used to perform tests with XPay:

• Api-Key implicit accounting terminal: 5d952446-9004-4023-9eae-a527a152846b
• Api-Key terminal explicit accounting: 2d708950-50a1-434e-9a93-5d3ae2f1dd9f

It is necessary to proceed with the payments using the cards made available in the section Payment cards, and use the TEST addresses made available in each API.

Payment Cards

in the test area, it is possible to use specific cards to simulate positive or negative payments. Below are the cards that can be used to make payments in the test area.

APM

APM: data is made available to test payments with some alternative payment methods, while for others it will be necessary to register for the proprietary sandbox of the APM.