Product Updates

What is 3D Secure 2? Guide for Merchants

November 13, 2026 6 min read
3D Secure 2 (3DS2) lets the card issuer confirm who is paying online. Low-risk payments pass in the background with no extra step, riskier ones get a challenge such as a one-time passcode, and some transactions are exempt from Strong Customer Authentication (SCA).
post thumbnail

3D Secure 2 (3DS2) is the latest version of the 3-D Secure protocol, in which cardholders confirm their identity with their card issuer when they pay online.

The industry calls it EMV 3DS. Issuers and merchants use it to guard against card-not-present fraud, a risk that has grown as online, in-app and phone payments rise.

The merchant’s checkout exchanges messages with the bank that issued the card, which uses them to authenticate the shopper and approve the transaction.

Visa calls its version, Visa Secure, data-driven verification that lets merchants confirm who is paying without slowing checkout.

Key takeaways

  • 3D Secure 2 is the latest version of 3-D Secure, the protocol in which the card issuer authenticates the cardholder for an online payment.
  • Low-risk payments pass in a frictionless flow with no shopper action; others go to a challenge flow, where the shopper must respond with a PIN or one-time password.
  • The merchant starts authentication by sending the issuer transaction, payment method and device details.
  • Since 31 December 2020, EEA and UK merchants have had to migrate to EMV 3DS.

First comes the 3DS 1.0

3D Secure or 3DS stands for three-domain secure.

The protocol adds a layer of authentication by verifying the customer’s identity at online checkout. Its main purpose is to stop someone else from using a cardholder’s card for online purchases.

Visa originally developed 3D Secure to make online card payments safer and announced the worldwide rollout of the first version, 3-D Secure 1.0, in 2001. It gave online card payments a standard way to authenticate the cardholder before authorisation.

Consumers not enrolled in 3DS couldn’t buy from online retailers that used it.

The early version relied on static passwords that sometimes added friction at checkout and could lead customers to abandon the purchase.

3DS 1.0 predates the smartphone and, on a phone, sent the shopper to a browser page for authentication. 3D Secure 2 was designed after smartphones were invented.

What is 3D Secure 2 (3DS 2)? Features and benefits

In 3DS 2, the merchant and the card issuer exchange data, or messages, so the issuer can authenticate the shopper and approve the payment. Designed after smartphones spread, it lets banks confirm a shopper’s identity in a mobile banking app or an in-app flow with no browser redirect. Four features matter most for merchants:

  • Fewer interruptions at checkout. The issuer authenticates low-risk payments in the background with no extra step for the shopper; only a potentially high-risk payment triggers a challenge.
  • Richer data with every payment. When authentication starts, the merchant sends the card issuer transaction, payment method and device details, and the bank checks the shopper’s identity against them.
  • Smooth shopping on any device. With software development kits, companies can connect mobile and website, applications, or other devices like Smart TVs and wearables.
  • Several kinds of extra check. When the issuer needs extra verification, its access control server (ACS) challenges the shopper, for example with a one-time passcode or a PIN entry.

What are PSD2 and SCA?

PSD2, the second version of the European Union’s Payment Services Directive (PSD), requires Strong Customer Authentication (SCA) for payments within the European Economic Area (EEA).

SCA requirements, exemptions, issuer vetoes and different regulatory approaches per country together make the payment process more difficult.

Visa data puts card-not-present fraud rates at 7.5 times the card-present rate.

Small and medium-sized businesses are frequent targets: they handle many card-not-present payments, often without a large fraud team.

3DS 2 mobile app and website user flows

What procedure does 3D Secure follow on a website?

Sites and mobile apps can offer different paths to the same task. A customer ordering pizza or a new pair of shoes can pay in a mobile app or on a website. On a website, a 3D Secure payment runs as follows:

  • A customer chooses a product or service on a website.
  • The customer enters the payment card details, as in a regular purchase.
  • The merchant connects the customer with the bank through a redirect to a separate secure page.

At the same time, the bank sends the customer a notification with a one-time password.

  • The customer enters the password from the message on that page.
  • The system returns to the merchant’s site automatically and starts the payment.
  • Payment occurs only after successful password entry.

Steps 3 and 4 happen only in the challenge flow, explained in the next section.

How does 3DS2 authentication work in a mobile app?

In a mobile app, an SDK runs the check inside the app instead of on a browser page.

3D Secure 2 payment flow inside a mobile app

The 3DS 2 mobile app payment looks like this:

  • A customer sends the card information to the payment gateway.
  • The gateway passes the transaction, payment method and device details to the card issuer.
  • The issuer’s access control server assesses the payment’s risk from this data and the shopper’s history.
  • Depending on that risk, the frictionless or the challenge flow follows.
  • The issuer then checks funds and account status and approves or declines the payment in real time.

Frictionless and challenge flows: how 3DS2 authentication works

Frictionless flow

When a payment looks low risk, verification happens behind the scenes: the access control server (ACS) evaluates the client’s device data and purchased items and authenticates them without involving the customer.

Issuers run this risk check on every payment in real time. Low-risk payments pass without friction, and higher-risk ones move to the challenge flow.

Challenge flow

3D Secure 2 challenge flow

A challenge starts when the ACS lacks the information to treat the payment as low risk. Where strong customer authentication applies, the shopper uses at least two of these three elements:

  • Something they know: a PIN or a password.
  • Something they have: a phone that receives a one-time password, a card reader or a key generation device.
  • Something they are, also called biometric authentication: fingerprint image, facial recognition, voice patterns, etc.

Can frictionless security tools in banking apps replace 3D Secure?

Device-based tools such as FIDO authentication can work inside 3D Secure 2. An EMVCo whitepaper written with the FIDO Alliance explains how EMV 3DS messages can carry FIDO authentication data.

What is Dynamic 3D Secure?

How Dynamic 3D Secure decides the flow: with 3DS 2.0 enabled, the payment goes frictionless when possible and to a challenge otherwise; without it, 3DS 1.0 runs the traditional authentication flow.
How Dynamic 3D Secure decides the flow: with 3DS 2.0 enabled, the payment goes frictionless when possible and to a challenge otherwise; without it, 3DS 1.0 runs the traditional authentication flow.

3DS is a safety measure designed to decrease chargebacks, but it can lower the transaction success rate and result in a bad payment experience.

Dynamic 3DS lets a merchant define transaction criteria and set rules for the 3D Secure flow. It collects and sends the needed security information to the issuer and processes all low-risk payments without additional authentication. Verification applies automatically only to risky payments.

How Unlimit supports 3DS 2 and keeps payments safe

Unlimit’s payment processing page presents its platform as fully compliant with PSD2, SCA and 3D Secure 2.0.

Unlimit also states that it is a PCI DSS Level 1 Certified Service Provider.

The provider says it relies on local licences to accept payments without intermediaries and to settle funds directly into businesses’ wallets or accounts.

Unlimit UK Ltd publishes its General Terms and Conditions for eMoney Accounts, its Card Services Terms and Conditions and a complaints handling policy on the Unlimit UK legal documents page.

Start accepting payments in the US and globally with one integration

3DS v2 deadline: when did 3D Secure 2 become mandatory?

Since 31 December 2020, merchants across the EEA, part of non-EEA countries and the UK have had to adjust their authentication capabilities and migrate to EMV 3DS to meet the PSD2 SCA requirements.

Two-factor authentication (2FA) became mandatory for every customer-initiated transaction within Europe, unless the transaction falls under an exemption.

What are the exemptions?

Skipping authentication can significantly improve the payment process, so it pays to use the exemptions wherever a transaction qualifies.

The SCA exemptions are:

  • Low-value transactions (all payments equal to or under EUR 30).
  • Low-risk transactions, as assessed by the payment provider through transaction risk analysis. The exemption depends on reference fraud rates and an exemption threshold value set in Chapter III of the SCA regulatory technical standards.
  • Recurring payments for the same amount, where the exemption covers each payment after the first one in the series.
  • Secure Corporate payments (can be applied by issuers only).
  • Payments to trusted beneficiaries, the payees on the payer’s own list (can be applied by issuers only).

Changelog

  • December 2020, first publication: 3D Secure 2 for merchants in seven sections, with four benefits, two authentication flows and five SCA exemptions.
  • November 2026, full update: definitions, authentication flows and SCA rules checked against EMVCo, Visa, Mastercard, the European Commission, the European Banking Authority and the UK FCA; deadlines rewritten in the past tense; three unconfirmed figures removed.
  • November 2026, new section: Key takeaways.
Join Unlimit newsletter and get the highlights of upcoming events, fresh articles & special offers
You can unsubscribe in any time.
Read our Privacy Notice.