No results

Card verification

The integration of this feature allows for a card verification, without any charge, with the sole purpose of confirming the validity of the card data entered by the customer.

Below, it will be explained how to perform a card verification in the integration modes:

  • Hosted Payment Page
  • Pay-by-Link
  • XPay Build
  • Server to server

Hosted Payment Page

The payment flow remains the same as the Hosted Payment Page solution, as it is necessary to call the same API:

Valuing the "paymentSession" object with the parameter:

actionType VERIFY

The card verification involves using an amount of 0, and different amounts will not be accepted.

During the verification process, it is possible to tokenize the card data, allowing for subsequent recurring or OneClick payments. To enable this option during card verification, the submission of additional parameters is required:

Pay-by-Link

The payment flow remains the same as the Pay-by-Link, solution, as it is necessary to call the same API:

Valuing the "paymentSession" object with the parameter:

actionType VERIFY

The card verification involves using an amount of 0, and different amounts will not be accepted.

During the verification process, it is possible to tokenize the card data, allowing for subsequent recurring or OneClick payments. To enable this option during card verification, the submission of additional parameters is required:

XPay Build

The payment flow remains the same as the XPay Build, solution, as it is necessary to call the same API:

Valuing the "paymentSession" object with the parameter:

actionType VERIFY

The card verification involves using an amount of 0, and different amounts will not be accepted.

During the verification process, it is possible to tokenize the card data, allowing for subsequent recurring or OneClick payments. To enable this option during card verification, the submission of additional parameters is required:

Server to server

For those who have a Server to Server integration mode, a dedicated API is made available:

This API is not subject to 3D Secure authentication.