PAYING.CO GUIDES
3D Secure, explained.
What 3DS is, who takes part in a 3DS2 payment, how it differs from 3DS 1.0 and the PARes message, and what to decide before you integrate it.
5 min read · By Kevin Medina · Updated November 19, 2026
The short version
3D Secure (3DS) lets the card issuer verify the cardholder during an online or in-app payment, before authorization. EMV 3DS (3DS2) approves most low-risk payments silently and challenges only when needed. It supports PSD2 strong customer authentication and can shift fraud liability to the issuer.
What 3D Secure is
3D Secure (3DS) is an authentication protocol for card-not-present payments. Before the payment is authorized, the issuer gets a chance to confirm that the person paying is the real cardholder. The current version is EMV 3-D Secure, often called 3DS 2 or 3DS2, and the specification is maintained by EMVCo.
The original 3DS 1.0 sent the shopper to a separate page to enter a static password. EMV 3DS replaced it with a data-driven flow that works in browsers and in mobile apps, and that can approve most low-risk payments without asking the shopper to do anything.
Who is involved
| Component | Side | Role |
| 3DS Requestor | Merchant or platform | The merchant environment that starts the authentication request. |
| 3DS Server | Merchant or PSP | Builds and sends the authentication request, and receives the result. |
| 3DS SDK | Mobile app | Collects device data and shows the challenge screen inside an app. |
| Directory Server (DS) | Card brand | Routes requests between the 3DS Server and the right issuer. |
| Access Control Server (ACS) | Issuer | Assesses risk and decides whether to approve silently or issue a challenge. |
How a 3DS2 payment flows
- The merchant collects device and transaction data and sends an authentication request through the 3DS Server.
- The Directory Server routes the request to the issuer's ACS.
- The ACS assesses risk. If the payment looks safe it returns a frictionless approval.
- If the ACS wants more proof, it starts a challenge, such as a one-time code or a confirmation in the bank app.
- The result and the authentication data go back to the merchant, who includes them in the authorization request.
3DS 1.0 versus 3DS2
| Question | 3DS 1.0 | 3DS2 (EMV 3DS) |
| Experience | Redirect to an issuer page for every check | Frictionless for most low-risk payments, challenge only when needed |
| Mobile apps | Poor fit | Built for apps through the 3DS SDK |
| Data shared with the issuer | Very little | Rich device and transaction data |
| Result message | The PARes (Payer Authentication Response) | The ARes, plus an RReq after a challenge |
| Status | Retired by the card brands | The current standard |
Why it matters
- Liability shift: when a payment is authenticated, liability for certain fraud chargebacks generally moves to the issuer. The exact rules depend on the card brand and the region.
- Regulation: in Europe, PSD2 strong customer authentication requires extra verification on many online payments, and 3DS2 is the usual way to meet it. Exemptions such as low-value payments and recurring payments reduce how often a challenge is needed.
- Approval rates: richer data lets issuers approve more genuine payments without friction.
What to decide before you integrate
- Use your gateway's 3DS, or run your own 3DS Server? Most teams use the gateway.
- Which channels need it: web checkout, mobile app, or both? Apps need a 3DS SDK.
- Which regions are in scope, and which SCA exemptions will you request?
- How will authentication data flow into the authorization message, and who owns the decline and retry handling?
- Which components need approval? EMVCo publishes the specification and runs testing and approval for 3DS components.
3DS covers online and in-app payments. In-person chip and contactless payments follow EMV rules instead. See our EMV Level 3 certification work for that side, or payment integration for gateway and acquirer connections.
For a deeper read, see our blog post on 3D Secure as a foundational layer of modern payment security.
Frequently asked questions
What is 3DS?
3DS, or 3D Secure, is a protocol that lets the card issuer verify the cardholder during an online or in-app card payment, before the payment is authorized. The current version is EMV 3-D Secure, also called 3DS2.
What does 3DS stand for?
3DS stands for 3-Domain Secure. The three domains are the issuer domain, the acquirer or merchant domain, and the interoperability domain run by the card brands. It is usually written 3D Secure.
What is a PARes in 3DS?
PARes stands for Payer Authentication Response. It was the message the issuer's server returned to the merchant in 3DS 1.0. In 3DS2 the equivalent is the Authentication Response (ARes), followed by a Results Request (RReq) when a challenge took place.
What is the difference between 3DS and 3DS2?
3DS 1.0 redirected every shopper to an issuer page for a static password. 3DS2 shares rich data with the issuer, approves most low-risk payments silently, and supports mobile apps. The card brands have retired 3DS 1.0.
What is an EMV 3DS access control server?
The Access Control Server (ACS) is the issuer-side component. It receives the authentication request, assesses risk, and either approves the payment without friction or starts a challenge.
Do I need a 3DS payment gateway?
If you take card-not-present payments in a market that needs strong customer authentication, or you want the liability shift, you need 3DS. Most merchants get it through a gateway that runs the 3DS Server and handles the routing.
Does Paying.co help with 3DS?
Paying.co is a payment engineering firm. We build payment applications and gateway and acquirer integrations, and we can help you scope where 3DS fits in a card-acceptance project.
Scoping card acceptance with 3DS in the mix?
Paying.co is a payment engineering firm specializing in EMV Level 3 certification, payment applications and acquirer integration. Tell us the channels, regions and gateway, and we will help you scope where 3DS fits.
Talk to us Book a meeting with a founder