Card verification service

Presentation

The PCI/Charge/VerifyPaymentMethod Web Service is used to verify the validity of a payment card. Once the verification is complete, the card can be used by the Merchant for payments that they can handle on their side.

Si nécessaire, le service authentifie le porteur de carte et renvoie les informations d'authentification à la fin du processus.

As a reminder, within the DSP2 framework, it is mandatory to authenticate the cardholder via the 3D Secure protocol.

Supported protocols

Other authentication protocols may be added to this list.

General principle

The service PCI/Charge/VerifyPaymentMethod allows to verify card validity.

To do this, the call to the PCI/Charge/VerifyPaymentMethod web service triggers a verification transaction.

The process is as follows:

• an initial call to the servicePCI/Charge/VerifyPaymentMethodwith a responsePaymentorAuthenticationInstruction.
• If the return belongs to theAuthenticationInstructiontype, the operation must be performed on the merchant side:
  • Creation of a visible or invisible iFrame.
  • In the iFrame, browser redirection to a target page after submitting a form that respects the definition specified in the instruction.
  • Potential interaction with the cardholder or the browser.
  • Return page of the remote server that will emit a JavaScript event containing the result of the instruction.
  • Interception of the instruction result in the form of a JavaScript event in the parent window.
  • New call to the PCI/Charge/VerifyPaymentMethod service with the signed result of the instruction obtained via the browser.
  • The PCI/Charge/VerifyPaymentMethod service then returns either an instruction or a result.
• si le retour est de type Payment, alors celui-ci contiendra le résultat final de la vérification et le processus est terminé.

Authentication is an important part of this web service, see how it works below.

Detailed flowchart

The following flowchart presents a generic payment scenario with authentication: the initial call to the service, an instruction, an interaction, the final authentication result and the end of payment.

See the implementation guide