{"section":"tutorials","requestedLocale":"en","requestedSlug":"what-is-3d-secure","locale":"en","slug":"what-is-3d-secure","path":"docs/en/tutorials/payments/foundations-and-concepts/what-is-3d-secure.md","branch":"main","content":"**3D Secure** (3DS) is a security protocol that adds a layer of protection to online credit and debit card transactions. The current generation, EMV 3-D Secure (EMV 3DS), is also known as 3DS 2.\n\nIn 3DS 2, the [issuing bank](/docs/tutorials/financial-agents-in-the-payment-flow#issuing-bank) analyzes the transaction data and decides how to authenticate the buyer:\n\n- **Frictionless authentication:** The bank considers the transaction low risk and completes authentication without requiring any action from the buyer.\n- **Challenge:** The bank asks the buyer to confirm their identity, for example, with a password, biometrics, or a code sent via SMS or email.\n\nThe protocol requires authentication but doesn't define the method: each bank uses its own verification system.\n\nChargeback is the cancellation of an online purchase made with a credit or debit card. When authentication is complete, liability for fraud-related chargebacks shifts from the merchant to the issuing bank, according to the criteria set by card networks and issuing banks. In modes that only send risk data to the issuing bank without authenticating the buyer, such as Adyen's Data Only, fraud liability may remain with the merchant. The liability shift also doesn't apply to chargebacks unrelated to fraud.\n\n## 3D Secure versions\n\n3DS 2 is maintained by [EMVCo](https://www.emvco.com/) and has more than one specification version:\n\n- **2.1.0:** Card networks stopped processing transactions authenticated with this version in September 2024.\n- **2.2.0 and 2.3.1:** Versions currently in use.\n\nThe version used in each transaction depends on the payment provider and the issuing bank.\n\nThe first generation, 3D Secure 1.0, was XML-based and redirected the buyer to the bank's environment after they entered their card details. Card networks discontinued this version as of October 2022.\n\n## 3D Secure on VTEX\n\nOn VTEX, the payment provider implements 3DS 2 via [Payment App](https://developers.vtex.com/docs/guides/payments-integration-payment-app#scenario-2-payment-app-and-3d-secure-2). This way, the buyer stays in checkout and authenticates in a modal window, without being redirected to the bank's site. To activate 3DS 2 and learn about its limitations, see [Setting up 3DS 2 authentication flow](/docs/tutorials/setting-up-3ds-2-authentication-flow).\n\n3D Secure and the [anti-fraud solution](/docs/tutorials/financial-agents-in-the-payment-flow#anti-fraud-solution) serve different purposes: 3DS confirms the buyer's identity with the issuing bank, and the anti-fraud solution evaluates the order's risk. To configure the anti-fraud solution, see [Configuring the anti-fraud](/docs/tutorials/how-to-configure-the-anti-fraud). To understand the credit card authorization flow, see [Credit Card - Basic payment flow](/docs/tutorials/credit-card-basic-payment-flow).\n\n### Related articles\n\n- [Setting up 3DS 2 authentication flow](/docs/tutorials/setting-up-3ds-2-authentication-flow)\n- [Credit Card - Basic payment flow](/docs/tutorials/credit-card-basic-payment-flow)\n- [Financial agents in the payment flow](/docs/tutorials/financial-agents-in-the-payment-flow#anti-fraud-solution)\n- [Configuring the anti-fraud](/docs/tutorials/how-to-configure-the-anti-fraud)"}