3D Secure

---
tags: [3dsecure]
---

<img src="https://files.readme.io/0e2e49b-3dsecure_icon.png" alt="3D Secure" align="left"> Effortlessly comply with Strong Customer Authentication (SCA) mandates for online selling. Nexio enables online sellers to enable or disable **3D Secure** requirements when necessary. Enhance your fraud strategy and minimize vulnerabilities by adding an additional layer of protection.

{/* 3D (three-domain) Secure, also known as 3DS, is a security layer for checkout. It helps prevent fraud by requiring cardholders to authenticate with their issuing bank when making online purchases.To comply with the PSD2’s Strong Customer Authentication (SCA) requirements, especially in regions where mandated, merchants should ensure transactions are properly authenticated with 3DS prior to being processed.Nexio uses 3DS 2.x protocol whenever possible, with 3DS 1.x fallback enabled for cases where issuers do not yet support 2.x.When a transaction is attempted, card issuers use the transactional data provided to determine whether a challenge is required. If a challenge is issued, additional information from the cardholder will be needed, such as a password or one-time code sent to the cardholder by their issuing bank.# 3D Secure through NexioThrough Nexio, the 3DS authentication workflow happens through a redirect provided by the cardholder’s issuing bank.With 3DS 2.x, shoppers experience a frictionless flow during which they are redirected from Nexio's secure ecommerce iframe to their bank page and then immediately redirected back to the shopping page.With 3DS 1.x, shoppers experience a challenge flow during which Nexio’s iframe prompts them to confirm they are being redirected to their bank's page for authentication. After confirmation, the iframe opens a new tab for completing the authentication. After a shopper completes authentication, the transaction is processed.Merchants using only the Nexio API to process transactions will need to handle the redirect separately. */}

# Learn more

For additional information, see the following pages:

* [3D Secure overview](doc:3d-secure-1)
* [3DS requirements](doc:3ds-requirements)
* [Using 3DS to run transactions](doc:using-3ds-to-run-transactions)
* [Using a third-party 3DS provider to run transactions](doc:using-a-third-party-3ds-provider-to-run-transactions)