3-D Secure
How Vayapay authenticates card payments with 3-D Secure 2
3-D Secure lets the card issuer authenticate the cardholder during an online card payment. When authentication succeeds, the liability for fraud-related chargebacks usually shifts from you to the card issuer.
Vayapay supports 3-D Secure 2 and handles it for you: the data exchange with the card schemes, the redirects and the result. You don't need a separate 3-D Secure integration.
Frictionless and challenge flow
The card issuer decides, based on the transaction data, which of two flows applies:
| Flow | What your customer sees |
|---|---|
| Frictionless | Nothing. The issuer authenticates the payment in the background. |
| Challenge | The issuer's authentication page, for example to approve the payment in a banking app or enter a one-time code. |
You don't choose the flow. The more complete the customer data in your order, such as name, email address, billing address and IP address, the more likely the issuer applies the frictionless flow.
- With the hosted payment page, authentication is part of the payment page.
- With card payments in your own checkout, the authenticate request returns a
redirect_url. Redirect your customer to it. If a challenge is needed, it's shown there.
While your customer is authenticating, the transaction has the status pending. Afterwards your customer returns to your return_url. Always confirm the payment from your server.
To test both flows, see Test data.
Send complete customer details
The issuer bases its choice of flow on the data it receives. Send your customer's name, email address, billing address, phone number and IP address in the customer object of the order, so more payments go through the frictionless flow. See Create an order in the API reference for the fields.
Use your own 3-D Secure provider
Already authenticating cardholders with your own 3-D Secure provider? In your own checkout, you can send its results to Vayapay and skip authentication by Vayapay. See External 3-D Secure.