Skip to content

3D Secure 2 explained: how it works, who is liable for fraud, and when to use it

3D Secure authenticates the cardholder in online card payments. Learn how 3DS2 works, when fraud liability shifts to the issuer, and how to tune it.

3D Secure, written 3-D Secure in the standard and shortened to 3DS, is a protocol that authenticates the cardholder during an online card payment. When authentication succeeds, liability for fraud-related chargebacks generally shifts from the merchant to the issuer. 3D Secure 2 adds risk-based checks, so the issuer can approve low-risk payments without a challenge.

This guide explains how 3DS2 works, what the liability shift covers and where it fails, how 3DS relates to European authentication rules, and how to set it up without losing sales. It reflects EMVCo's public pages and vendor documentation as of October 2026. Each card scheme sets its own liability rules, so confirm the details with your acquirer.

Key takeaways

  • 3DS authenticates the cardholder, not the card. The issuer confirms that the person paying is the account holder.
  • 3DS2 has two paths. A frictionless flow needs no customer action. A challenge flow asks for proof.
  • Successful authentication generally shifts fraud liability to the issuer. The exact rules belong to each card scheme.
  • The shift covers fraud only. Disputes about delivery, quality, or cancellation stay with the merchant.
  • In Europe, 3DS is how card payments meet strong customer authentication under the second Payment Services Directive (PSD2).

What is 3D Secure?

3D Secure is an authentication protocol for card-not-present payments, meaning payments where the card is not physically read, such as online checkout. It adds a step before authorization in which the card issuer confirms the cardholder's identity.

The name comes from three domains. Vendor GPayments describes them as "the issuer, the acquirer, and the interoperability domain" (GPayments FAQ). The issuer is the cardholder's bank. The acquirer is the merchant's payment provider. The interoperability domain is the card scheme's infrastructure that connects the two.

EMVCo, the body that manages the EMV specifications, maintains the current version. Its site states that "EMVCo maintains the EMV 3DS Specifications and supporting approval processes" (EMVCo). The industry calls this version 3D Secure 2 or 3DS2. The first version relied on static passwords and full-page redirects. 3DS2 sends richer transaction data and supports app-based and biometric checks.

Authentication and authorization are separate steps. Authentication asks "is this the cardholder?" Authorization asks "can this card pay this amount?" A payment can pass the first and still be declined at the second. How card payments work covers authorization and what follows.

How does 3D Secure 2 work?

3DS2 runs between the checkout page and the authorization request. The customer often sees nothing.

  1. The customer submits the payment. The checkout collects the card details and data about the device and the order.
  2. The merchant's 3DS server sends an authentication request. It goes through the card scheme's directory server, which routes it to the right issuer.
  3. The issuer's access control server assesses the risk. The access control server (ACS) is the issuer's system for 3DS. It scores the request using the data it received and what the bank knows about the customer.
  4. The issuer picks a path. Low-risk payments pass in a frictionless flow. Others get a challenge.
  5. The customer completes the challenge, if there is one. Typical methods are approval in the banking app, a biometric check, or a one-time code. EMVCo lists biometrics among the supported challenge methods.
  6. The issuer returns the result. A successful result includes proof of authentication that the merchant attaches to the authorization request.
  7. The merchant sends the authorization. The issuer approves or declines the payment as usual.
Frictionless flowChallenge flow
What the customer doesNothingApproves in an app, uses a biometric, or enters a code
Who decidesThe issuer, from the data sentThe issuer, after the customer responds
Effect on checkout timeNone the customer can seeAdds a step
Main risk for the merchantNoneThe customer fails or abandons the step

The data the merchant sends matters. An issuer with complete, accurate data can approve more payments without a challenge.

What is the liability shift, and when does it fail?

The liability shift moves the cost of a fraud chargeback from the merchant to the issuer when the payment was authenticated. Global Payments describes it this way: liability shift "typically means that the responsibility for covering losses from fraudulent transactions transfers from the merchant to the issuing bank" (Global Payments developer docs).

Two limits apply. First, it covers fraud disputes only, where the cardholder says they did not make the purchase. Second, the rules are not identical everywhere. GPayments notes that "different card schemes determine their own liability shift implementation rules."

ScenarioAuthentication resultWho generally bears fraud liability
Customer passes a frictionless flowAuthenticatedIssuer
Customer completes a challengeAuthenticatedIssuer
Customer fails or abandons the challengeNot authenticatedNo shift. The payment should not proceed
Issuer's system does not respond and the merchant proceeds anywayNot completedMerchant, in general. Check your acquirer's rules
Merchant does not request 3DSNoneMerchant
Non-fraud dispute, such as item not receivedAnyMerchant. 3DS does not apply

The fourth row catches merchants out. If authentication cannot be completed and you send the authorization anyway, you generally keep the fraud liability. Decide in advance whether your gateway should allow or block those payments, and confirm the rule with your acquirer.

Card-present payments have a separate rule. Since October 1, 2015 in the US, in-store counterfeit fraud liability sits with the party that has not adopted chip technology, per Visa's EMV liability shift notice. Card-present vs card-not-present payments compares the two channels.

A successful authentication does not make a payment dispute-proof. Chargebacks explained covers the disputes that 3DS does not touch.

How does 3DS relate to Strong Customer Authentication under PSD2?

Strong Customer Authentication (SCA) is a requirement of PSD2, the European Union's second Payment Services Directive. It calls for two-factor authentication on many electronic payments in the European Economic Area. 3DS is the protocol card payments use to meet it.

EMVCo says that "EMV 3DS supports SCA by enabling the use of two-factor authentication," and notes that the European Banking Authority has recognized such protocols. Global Payments' documentation says merchants use 3DS "to comply with European strong customer authentication (SCA) regulations set in PSD2."

In practice, an issuer in the European Economic Area can decline a card payment that needed authentication and arrived without it. The rules include exemptions and out-of-scope cases, and applying them is a decision for your acquirer and the issuer. Ask your acquirer which ones it supports, and treat this as a compliance question for a specialist.

Outside Europe, 3DS is usually optional. Merchants use it selectively, on high-risk orders or where an issuer asks for it.

Does 3DS lower conversion, and how do you tune it?

A challenge adds a step, and every extra step loses some customers. The frictionless flow exists to limit that cost. How much 3DS affects your conversion depends on how often your payments are challenged and how many customers complete the challenge.

Four practices help.

  • Send complete data. Device, billing, shipping, and account history fields help the issuer approve without a challenge.
  • Apply 3DS by risk where the rules allow. Outside markets that require authentication, run it on orders your fraud tools score as risky.
  • Measure by issuer. Track challenge rate, challenge completion rate, and authorization rate after authentication for each issuing bank.
  • Handle failures cleanly. After a failed challenge, offer one more attempt and a second payment method. Do not send the authorization anyway.

A failed authentication is one cause of declined payments. Why card payments get declined covers the others.

How do you implement 3DS?

Most merchants get 3DS through their gateway or payment service provider and do not build the protocol themselves.

  1. Check what your provider supports. Confirm EMV 3DS version support, in-app flows, and which card schemes are covered.
  2. Choose the integration. A hosted payment page or hosted fields run 3DS for you. A direct API integration gives more control and more work.
  3. Collect the data fields. Pass the device and order data your provider asks for, with the customer's consent where required.
  4. Set your rules. Decide when to request 3DS and what to do when authentication is unavailable.
  5. Store the result. Keep the authentication outcome with the order. It is your evidence if a fraud dispute arrives.
  6. Test each path. Use your provider's test cards for frictionless, challenge, failed, and unavailable results.
  7. Monitor after launch. Watch challenge rate, completion rate, and fraud chargebacks by issuer and country.

Stored cards add a wrinkle. The first payment, with the customer present, can be authenticated. Later merchant-initiated charges cannot, because the customer is not there. Card tokenization explained covers how stored credentials stay valid.

Sources

What to do next

Ask your acquirer for its liability rules by card scheme, then test the frictionless, challenge, and failure paths before launch. For the disputes that 3DS does not cover, read chargebacks explained. BlindPay does not issue cards. It accepts card payments as one payin method, and every production charge requires an authenticated 3-D Secure result, per the card payins docs.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.