How can we help you?

An Order identifies a transaction, which is the purchase of a good or a service. The order is encoded in the APIs using the orderId parameter. An Operation represents an action performed on an order, …

Yes. Merchants can make refunds and void transactions via API or in the back office.

Yes. Merchants can make preauthorization by using the parameter PREAUTH in the initialization request. Make sure that terminal supports this kind of feature.

A confirmation can be delayed for a maximum of five days.

To be accounted, a transaction must be confirmed after the authorization process.

The integration mode to be used is the one with Api Key, and not the one with Alias and MAC Key.

You can find the plugins supported and the installation instructions in the developer web portal.

URL: https://xpay.nexigroup.com/api/phoenix-0.0/psp/api/v1/orders/hpp

URL: https://xpay.nexigroup.com/api/phoenix-0.0/psp/api/v1//orders/hpp

There may be different reasons causing a notification error.

Frequent errors are:

The merchant could face a handshake error during servers’ connection, in this case can:

Although in this moment the API key doesn’t expire, for security reasons; it is better for you to change it every 90 days.

Yes. Merchants can have multiple API keys active at the same time.

To create an API key, navigate to the Settings > ApiKeys > Create section within the merchant back office.

The API key is the authentication key to connect to XPay which must be passed in the header of each API call.

Once the testing phase is complete, it is necessary to replace the ApiKey and endpoints with the production ones.

Test API keys and cards are available for use in the staging environment.

The APIs exposed by XPay support the HTTP protocol with channel encryption and utilize the JSON format for both requests and responses. We do not provide APIs in XML format.

A Software Development Kit (SDK) is a collection of tools that simplifies and streamlines the process of creating programs and applications. Nexi offers programmers and developers these tools to ease …

Hosted Payment Page

Firstly, it is necessary to determine if the E-commerce site has been developed using a CMS here as we provide plugins for these CMS platforms.

Here: https://developer.nexigroup.com/xpaygreece/en-EU/api/

Among API transactions’ data you can find a response code that identifies the reason of the denial.

You can access the merchant back office, a web portal where you can see all the transactions made by your terminal and manage them.

Yes. The merchant can perform MOTO via API or via back office (“Services” tab), according to your contract.

XPay support Visa, MasterCard, American Express and Diners schemas.

Yes. The payment page can be displayed in different languages.

Yes. You can add your logo into the checkout page (Hosted Payment Page and Pay-by-Link) by sending it to the customer support.

Yes. By using Recurring payments (MIT – Merchant Initiated Transaction) you can perform subsequent payments without the interaction with the cardholder.

Yes. By using OneClick payments (CIT – Customer Initiated Transaction) you can save cards data for frictionless payments.

No. There is the Pay-by-Link integration mode, which allows you to send payment links to customers without the need to necessarily have a website.

Yes. All transmissions of sensitive data are encrypted according to the HTTPS protocol, in line with the security standards imposed by the International Schema and the PCI-DSS standard.