No results

Overview

The XML Hosted 3DSecure protocol provides for the possibility to perform safe mode payments at all steps of the transaction; In fact, the protocol allows to pay in compliance with the latest security protocols (Verified by Visa and MasterCard Identity Check) that guarantee non-repudiation of most transactions, and the standards of PCI (Payment Card Industry) DSS (Data Security Standards) Security.

The payment page is made with responsive technology to be usable via web and mobile devices.

You can customise the checkout page by inserting your shop logo (jpeg 150X40 pixels, maximum size 1 mb) by contacting customer service (commercio.elettronico@nexigroup.com).

The supported mobile operating systems are:

  • iOS for iPad and iPhone version 4 and above
  • Android version 4 and above
  • Windows Phone for versions starting from 7

The cookies generated by the payment page during navigation is technical, and used only for statistical purposes and not commercial.

Payment flow:

  1. The cardholder makes a purchase on the merchant's site; payment data is transmitted to the Merchant's server
  2. The Merchant's server initialises the payment with an HTTP Post message
  3. The Gateway validates Initialisation
  4. The Gateway returns the PaymentID, a security token and the URL of the Hosted Payment Page
  5. The Merchant's server redirects the cardholder to the HPP using the PaymentID as parameter
  6. The cardholder fills in the form with the credit card sensitive data
  7. The Gateway logs payment data
  8. The Gateway sends an authentication initialisation request to the Circuit Directory Servers
    1. Circuit Directory Servers redirect to the card issuer's authentication page
    2. The cardholder enters the authentication data requested by the card issuer (password, pin, biometric data)
    3. The Issuer replies to the Directory Servers of the Circuits with with authentication result
  9. Circuit Directory Servers respond with the outcome of the transaction
  10. The Gateway sends the payment outcome in “server to server” mode to the Merchant's ResponseURL
  11. The Gateway reads the ResultURL dynamically returned by the Merchant within the ResponseURL page
  12. The Gateway redirects the cardholder to the ResultURL