Loading...
FinchTrade

Definition

3D Secure

Learn how 3DS checks work at online checkout, why challenges appear, and what authentication means for payment approval and fraud liability.

3D Secure (3DS) is a protocol for authenticating cardholders in card-not-present credit and debit card payments, especially online checkout. It adds an authentication layer to help the card issuer assess whether the person using the card is its legitimate holder, reducing the risk of unauthorized use.

The Three Domains

The name 3D Secure refers to three domains involved in authentication, not three authentication factors. The issuer domain covers the card issuer and the systems it uses to authenticate the customer. The merchant/acquirer domain covers the merchant and the acquiring side that requests authentication, typically through a payment provider. The interoperability domain supplies the infrastructure and protocols that connect these participating systems and carry authentication messages between them.

How the Authentication Check Works

At checkout, transaction and device information is sent through the authentication infrastructure to the issuer. The issuer evaluates that information to assess the payment's risk and determine the authentication response. In 3DS2, a frictionless flow can authenticate the cardholder in the background without asking them to take an extra step.

A challenge flow instead asks the customer to complete an issuer-selected check, such as entering a one-time code or confirming the purchase in a banking app. Challenges can reflect risk or other applicable requirements; they are not limited to transactions classified as high risk. A separate website redirect is not always needed, because the experience may be presented within a browser or app.

The second generation of 3D Secure, commonly called 3DS2, supports richer risk information and browser and mobile-app experiences. Compared with older redirect-heavy flows, this can reduce unnecessary checkout interruptions, but it does not eliminate challenges.

Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?

Payment Outcomes

Authentication checks the cardholder's identity; payment authorization determines whether the issuer approves the payment. Passing a 3D Secure check does not guarantee authorization, because the issuer still evaluates factors such as available funds or credit and account status. A payment can therefore pass authentication and still be declined. Nor does a successful check establish that a purchase has completed or that funds have settled. Merchants need to distinguish the authentication result from the later payment status rather than treating them as the same outcome.

Benefits and Practical Limits

3D Secure helps reduce unauthorized card use, but it cannot prove identity beyond doubt or prevent every fraudulent payment. Eligible transactions may shift liability for certain unauthorized-payment chargebacks from the merchant to the issuer, subject to card-scheme rules and exceptions. Successful authentication alone is not a blanket guarantee of liability protection, and that protection does not cover every kind of customer dispute.

3DS can support strong customer authentication where applicable. Whether a payment meets the relevant requirements depends on its scope, the authentication performed and any applicable exemptions; using the protocol alone does not establish regulatory or data-protection compliance.

Challenges can add friction, confuse customers or cause checkout abandonment. Technical integration failures can also interrupt the process even when the customer is legitimate. A merchant's payment-provider integration and clear instructions about the requested check matter: customers need to understand what to do and how to return to checkout after an app-based confirmation.

Power your growth with seamless crypto liquidity

A single gateway to liquidity with competitive prices, fast settlements, and lightning-fast issue resolution

Get started