Getting started

This page shows how to get started and what agreements and credentials you might need before integrating XPay payment solutions.

Prerequisites

What you need before you start:

Perform integration with XPAY in accordance with this manual (in case you require Server to Server integration, please make sure that you meet all the PCI DSS requirements as you will be asked for relevant documents).
Obtain the XPay Test Credentials to test your integration and perform basic tests. For more information, please see the Test area section.
Confirm to your Nexi partner or your Acquirer that you are ready for live production.
Obtain the XPay Credentials to go live.
Obtain the XPay Admin Account for the Merchant portal (if applicable).
Start the production operation.

In case of any questions, please contact our technical support.

Introduction

The latest generation virtual POS of Nexi is designed for those who, through a website, want to sell goods or services by managing online payments.

This payment gateway has the following benefits:

Easy integration
Flexibility: management of online payments through the main international circuits.
Security: thanks to compliance with the security standards defined by international circuits with Visa Secure and Mastercard Identity Check.
Transparency: because traditional paper reporting is accompanied by online reporting through the website.

The electronic payment platform provides customers with a series of payment methods and tools to manage transactions, depending on their specific needs.

All transmissions of sensitive data involving the operator, Nexi's systems and the end customer are encrypted according to the HTTPS protocol, in line with the security standards imposed by the International Circuits and the PCI-DSS standard.

Nexi systems are also subjected to periodic and constantly updated security checks to ensure protection against any vulnerabilities detected under standard protocols.

This site is intended as a guide for developers, not neglecting the functional aspect.

Integration

The first step is to identify which type of integration you want to implement in your ecommerce or in your management system:

Hosted Payment Page: with this method, the customer at the time of payment is redirected to a Nexi cash desk, where he enters the card data and performs the authentication procedures necessary for payment. Once the transaction is concluded, it returns to the merchant's ecommerce.

Pay-By-Link: designed for merchants who do not necessarily have an ecommerce site, but need a way to receive payments. This solution allows you to create payment links, which can be sent via email, SMS or through the most famous messaging systems to your customers.

Server to Server: payment solutions that do not include external cash desks, card data are entered directly into the ecommerce site, through API calls the merchant server sends sensitive data to the gateway to make the payment. PCI DSS certification required (SAQ D questionnaire).

In-App SDK: The sections dedicated to the SDKs are divided by programming language, and contain information relating to the installation of these tools and their use. The SDKs can be modified according to the needs of the developers.

Process Payments

Once you have chosen the type of payment that best suits your business, you must check the additional services made available by Nexi, in order to identify any features to be implemented:

OneClick payments: This feature allows you to tokenize the customer's card data in order to allow faster subsequent payments.
Recurring payments: This feature allows you to tokenize the customer's card information, so you can make recurrences for services such as subscriptions.
Currency conversion: By default the payment with the gateway is made with Euro currency, but services are made available to allow the customers to proceed with the payment in the reference currency.
Omnichannel: This feature allows to enrich the user experience of collection services by offering customers the omnichannel framework, ensuring the ability to manage shopping experiences and multi-channel use cases that allow you to initiate an online payment (in store) and finish it in store (online):
- Click and Collect: This feature allows a shopping experience that allows the customer to initiate a purchase on an online channel and to finish it at a physical store of the merchant.
- POS Tokenization: This feature allows the customer to register their card data via tokenization directly on the physical POS and allowing the merchant to subsequently charge amounts without requiring a card or other data from the customer (recurring payments and OneClick).
Multi-currency payments: XPay allows you to operate in 30 countries and settle payments in 12 currencies:
- Multi Currency: with the Multi Currency service it is possible to manage the currency with which to display prices and accept payments.
- DCC: allows customers of international Visa and Mastercard credit cards to make purchases in their own currency, with a guaranteed exchange rate at the time of payment.

Not all of the features listed are available for integration modes.

SDK

A Software Development Kit is a suite of tools that can be used to create, in a simpler and more immediate way, programs and applications. Nexi provides these tools to help programmers in developing solutions, starting from a ready-made base. Check the available programming languages in the dedicated section.

Test Area

During the implementation of integrations, as well as in plugin testing, a test environment is made available, with the data needed to make calls to the gateway and payment cards to simulate purchases.

It is always recommended to perform tests before the transition to production. Also for plugins, Nexi invites you to carry out payment tests to verify that there are no problems with 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 difficulties in integration or errors returned by plugins, refer to the support section.