Payment
The first phase of the payment consists og transmitting the preliminary payment data to the Gateway, such as amount, currency, order reference and url to continue the payment.
To improve and speed up the shopping experience, the 3DSecure 2.2 protocol has been adopted. To use the service, refer to section 3D Secure 2.2.
After receiving this data, the Gateway returns an output in XML format, a unique PaymentId, a security token, and the page url to enter the credit card details.Call parameters of HTTP payment message for Payment Initialisation
NAME | DESCRIPTION | FORMAT | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Parameters of response to Payment Initialisation message
NAME | DESCRIPTION | FORMAT | |||||||||||||||||
|
Cardholder redirection to payment page
After receiving an initialisation message response, the web session of the cardholder must be redirected to the url specified in the hostedPageUrl tag to which the paymentid parameter must be appended. This url must not be set as fixed parameter for redirection but must be retrieved dynamically for every payment from the appropriate tag.
PAY ATTENTION: this url can not be inserted into an i-frame.
Once the cardholder is on the payment page, he will enter the data for his credit card and, if the card is part of the 3D Secure program, he will also be prompted to enter the relevant 3D Secure password.