3D Secure is a card-payment authentication protocol that allows a card issuer to verify the cardholder during an online purchase. It adds an authentication step to the authorization process without replacing the merchant’s fraud controls.
How does 3D Secure work?
When a customer submits a card payment, transaction and device information is shared with the issuer through the 3D Secure network. The issuer may approve the authentication without customer action or request a challenge such as a one-time code or banking-app confirmation.
Frictionless flow versus challenge flow
A frictionless flow uses risk signals to authenticate the transaction in the background. A challenge flow asks the cardholder for additional proof. The issuer, not the merchant, generally determines which flow applies.
Does 3D Secure prevent chargebacks?
No. Successful authentication can shift liability for certain fraud-related chargebacks, subject to scheme rules and transaction eligibility. It does not protect against every dispute reason, such as non-delivery, duplicate billing or an incorrect amount.
What should a merchant record?
Keep the authentication result, protocol version, transaction identifier, exemption request, challenge outcome and related authorization response. These records help explain whether the payment was authenticated and how it proceeded.
Where can implementation fail?
Common problems include unsupported cards, failed challenges, timeouts, inconsistent browser data and treating authentication as proof of authorization or settlement. Test fallback behavior and monitor conversion by issuer, market and device.
Related Terms
- Card Authentication
- Payment Authorization
- Chargeback
- Card-Not-Present Transaction
- Transaction Monitoring
