On this page
ACS (Access Control Server)
ACS (Access Control Server)
The ACS (Access Control Server) is the issuer-side software component in the 3D Secure 2 (3DS2) (EMV 3DS) protocol that makes the final authentication decision for card-not-present (CNP) transactions. Hosted by the card-issuing bank (or an outsourced ACS vendor), it receives authentication requests generated by the merchant's 3DS Server, evaluates them using a risk engine, and returns a decision: frictionless approval, consumer challenge, or rejection. The ACS is the component responsible for the friction-vs-conversion trade-off that defines the shopper experience in SCA-regulated markets.
The three-domain model
EMV 3DS operates across three domains, as described by M2P Fintech and Corbado (2026):
| Domain | Key component | Operated by |
|---|---|---|
| Acquirer / Merchant | 3DS Server | Merchant or their gateway |
| Interoperability | Directory Server | Card networks (Visa, Mastercard, Amex, etc.) |
| Issuer | ACS | Issuing bank or their ACS vendor |
Three transaction IDs link every message in a single 3DS transaction: threeDSServerTransID (generated by the 3DS Server), dsTransID (generated by the Directory Server), and acsTransID (generated by the ACS).
ACS internal components
According to a practitioner engineering guide (Medium/@Hammad_Hassan61):
- TLS/mTLS termination — accepts inbound authentication requests
- Message parser and validator — validates AReq message format against EMVCo spec
- Card range and enrolment database — PAN lookup to confirm the card is enrolled in 3DS
- Risk-based authentication (RBA) engine — scores the transaction using 150+ data elements
- Frictionless flow engine — generates CAVV and returns ARes with status Y when risk is low
- Challenge flow engine — serves the challenge UI (OTP, biometric, SPC) when risk score exceeds threshold
- HSM-backed CAVV generator — produces the Cardholder Authentication Verification Value; requires FIPS 140-2 Level 3+ hardware
- ARes/RRes builder and signer — constructs and signs authentication response messages (JWS with RS256 or ES256)
- 3DS Method URL handler — receives browser fingerprint data before the AReq to enrich the risk score
Security requirements include TLS 1.2 minimum (1.3 recommended), mTLS between DS and ACS, and PCI-DSS Level 1 compliance. The ACS must return an ARes within 10 seconds; failure causes the Directory Server to send an error (ErReq code 306).
Authentication decision flow
The ACS processes each authentication request through a structured sequence, as described by the Medium engineering guide:
Pre-RBA checks (in order):
- If the card is not enrolled → return
U(unable to authenticate) - If mandatory challenge policy applies → return
Cdirectly (skip RBA) - If the cardholder has whitelisted the merchant → return
Y(skip RBA) - Otherwise → run the RBA engine
RBA engine output:
- Score ≤ low threshold →
Y(frictionless) with CAVV and Electronic Commerce Indicator (ECI) 05 (authenticated) - Score between thresholds →
C(challenge required) - Score above high threshold →
N(authentication failed) orR(issuer rejected as suspected fraud; unlikeN,Rcannot proceed)
Adyen's documentation (2026) describes four distinct 3DS transaction flows available to merchants:
| Flow | Description |
|---|---|
| Frictionless | Passive authentication via device fingerprint; no shopper interaction |
| Challenge | Shopper performs additional verification (biometrics or 2FA) per SCA requirements |
| Data-only | Sends a 3DS2 request without requesting authentication; Visa and Mastercard only |
| Standalone authentication | Authenticates and returns data to authorise with Adyen or a third party later |
Stripe's September 2026 changelog added explicit support for a Data Share Only result mode (three_d_secure.result = "data_share_only"), which indicates the issuer performed 3DS in a mode that shares cardholder data to improve authorisation decisions without a full authentication. Prior to this change, Data Share Only transactions were indistinguishable from no-3DS charges (as-of 2026-09-30).
Data elements and merchant impact on frictionless rate
EMV 3DS sends 150+ data elements to the ACS — approximately 10× the data capacity of 3DS 1.0 (M2P Fintech). The richness of this payload directly affects the ACS's ability to authenticate frictionlessly.
ACI Worldwide's documentation states that providing fewer data elements reduces issuer confidence and increases the likelihood of the ACS triggering a challenge. Recommended fields beyond mandatory ones include billing/shipping addresses, cardholder contact information, and prior account history.
Key data elements the ACS risk engine weighs (Medium engineering guide):
threeDSCompInd— whether the browser ran the 3DS Method URL (acts as a score multiplier)- Account history:
chAccAgeInd,nbPurchasesInLast6Months,txnActivityDay/Year - Merchant risk:
shipIndicator,deliveryTimeframe, gift card count and amount addrMatch— whether billing and shipping addresses match
Challenge methods
Under EMV 3DS, the ACS can present multiple challenge types. Corbado (updated 2026-08-28) lists:
- SMS/email OTP — one-time passcode delivered out of band
- Push OTP via mobile banking app — out-of-band push notification; dominant in the UK
- In-app biometrics — fingerprint or face recognition within the bank's app
- Secure Payment Confirmation (SPC) — Secure Payment Confirmation (SPC), a FIDO-based browser challenge method; supported starting in EMV 3DS v2.3 (confirmed on Netcetera and Worldline ACS products as of 2026)
- Knowledge-based authentication (KBA) — static secret questions; fallback only
Corbado reports that in the UK, over 75% of 3DS challenges are completed through a bank app, mostly with biometrics (citing Stripe H1 2024 data — as-of H1 2024, potentially superseded).
The Stripe H1 2024 data on UK challenge completion methods and the Stripe France frictionless trend data both predate the most recent ACS updates; more recent figures may differ.
EMVCo protocol versions
EMVCo is the standards body that publishes the EMV 3DS spec. Current version status (as-of 2026-10-23):
| Version | Status | Notes |
|---|---|---|
| 2.1 | Deployed | Supports PSD2 SCA but EMVCo recommends 2.2+ for full functionality |
| 2.2 | Current minimum (EMVCo recommended) | Added FIDO data in 3DS messages |
| 2.3 | Current deployments | Added decoupled authentication; Secure Payment Confirmation (SPC) officially supported |
| 2.3.1.1 | Latest stable (Spec Bulletin SB n° 279, 2025-08-11) | — |
| 2.4.0.0 | Draft (as-of 2026-06-03) | DSB n° 330 public comment closed 2026-07-01; subscriber-only access |
Stripe added support for 3DS protocol versions 2.3.0 and 2.3.1 in Payment Records in its 2026-09-30 changelog.
EMVCo collaborates with the PCI Security Standards Council on security evaluation of EMV 3DS solutions. Letters of Approval (LOA) are issued per ACS vendor per spec version; multiple ACS vendors held v2.3.1 certifications as of late 2025.
ACS vendor landscape
The market for ACS software is dominated by a small number of certified vendors, as summarised by Corbado (2026-08-28). Most issuing banks do not build an in-house ACS.
| Vendor | Notes (all vendor-reported, flag for bias) |
|---|---|
| Entersekt | Acquired Modirum in December 2023; claims 2.5bn+ transactions/year (FY2024) |
| Broadcom (Arcot/CA Technologies) | Claims coverage of 5,000+ financial institutions across 229 countries |
| Netcetera | Claims first ACS vendor certified to EMV 3DS 2.3.1; covers 1,000+ issuers and 230M cards |
| Worldline | Claims 2.4bn+ 3DS transactions/year for 100+ issuers |
| GPayments (ActiveAccess) | — |
| ACI Worldwide | — |
| RSA | — |
| 2C2P | — |
| 3dsecure.io | — |
| Adyen | — |
| Computop | — |
Netcetera's own blog states "230 million cards" and "1,000+ issuers," while the Corbado 2026 review (citing vendor materials) reports "800+ banks/issuers" and "50M+ cards protected." These figures likely reflect different time periods or different product lines and cannot be reconciled from available sources. — netcetera.com vs corbado.com
M2P Fintech states that building an in-house ACS requires a multi-million-dollar investment, 1.5–3 years to market, and full responsibility for EMVCo and network certification; buying from a vendor provides pre-certification, usage-based pricing, and ~5× faster deployment.
Benchmarks and conversion impact
Note: All figures below are vendor-reported or from vendor research (Forter, Stripe). No independent third-party benchmark covering all European markets was identified.
The Forter EMEA Research Report 2026 (based on ~723,000 approved, challenged transactions in June 2026) is the most comprehensive 2026 dataset found (as-of 2026):
- Approximately 1 in 6 trusted (pre-approved) customers fail or abandon the 3DS challenge across Europe.
- Per-country challenge abandonment rates for trusted customers: Austria 25.5%, Germany 24.5%, Italy 21.8%, Spain 20.0%, France 16.2%, UK 6.9%.
- Mobile challenge abandonment is 7–12 percentage points higher than web across major issuers (e.g., Crédit Agricole: 29% mobile vs. 17% web; Bank of Scotland: 24% mobile vs. 14% web).
- Abandonment on transactions above €100 is 8–15 percentage points higher than on low-value transactions.
- Authentication failure breakdown across the Forter network: exemption rejection 27.8%, issuer rejection 15.6%, user abandonment 12.6%, technical failure 11.5%.
- Forter states that poorly implemented 3DS is associated with a typical European conversion decline of 2–3.5%.
- VortexIQ/Cybersource platform documentation sets a severity alert for 3DS challenge abandon rate at 15–25%, with an audit check firing above 30% (medium severity) (as-of unknown date).
Stripe data from regulated markets (stale-risk — H1 2024 data; flagged as potentially superseded):
- French frictionless authentication flows rose 40% in H1 2024, attributed to French issuers approving more SCA exemption requests when transactions carried richer data over 3DS rails.
- UK issuers accept SCA exemption requests at rates 10 percentage points higher than EEA issuers, and UK authentication success rates are 5–10% higher than comparable SCA markets (H1 2024).
Stripe's regulated-markets data above references H1 2024. The Corbado and Forter sources (both from 2026) supersede it for directional benchmarks.
Japan post-mandate (as-of April–mid-2025, Stripe data — stale-risk flag): After Japan's April 2025 3DS mandate, approximately 60% of transactions took the frictionless path, merchants averaged a 93% conversion rate, and dispute rates were more than 30% lower than the same period the prior year.
Stripe reports that in unregulated US markets, issuers often declined transactions that requested 3DS, treating the 3DS request itself as a fraud signal — reducing approval rates when 3DS is used voluntarily. This conflicts with general vendor messaging (e.g., M2P Fintech) that 3DS reduces declines. The likely explanation: ACS configurations and issuer readiness differ substantially between mandate-driven markets and unregulated markets. — stripe.com vs m2pfintech.com
Regulatory context (PSD2/SCA, PSD3/PSR)
Current regime — PSD2/SCA (active):
Adyen and Forter note that for EEA transactions above EUR 30 without a valid SCA Exemptions|exemption, the ACS must trigger a challenge rather than return frictionless Y. Transaction Risk Analysis (TRA) exemption thresholds under Delegated Regulation (EU) 2018/389 (as-of 2026):
| Transaction value | Maximum issuer fraud rate to qualify |
|---|---|
| Up to €100 | ≤ 0.13% |
| Up to €250 | ≤ 0.06% |
| Up to €500 | ≤ 0.01% |
Forter (2026) reports that since May 2025, the Banque de France has required exemptions on French-issued cards to go through 3DS rails; direct-to-authorisation (DTA) requests on French-issued cards are soft-declined by the ACS.
Future regime — PSD3 / Payment Services Regulation (PSR):
PCI Proxy and Checkout.com report that PSD3 and PSR reached provisional political agreement in November 2025. Key ACS-relevant changes proposed (as-of November 2025 provisional agreement — not final law):
PSD3/PSR provisions summarised here reflect the November 2025 provisional agreement. Final adopted text and implementation dates may differ.
- 3DS 2 remains the primary SCA mechanism; no new protocol is mandated.
- The four SCA exemption categories (low-value, TRA, trusted beneficiary, secure corporate payment) remain substantially unchanged.
- Liability Shift (Payments) (authenticated 3DS moves fraud chargeback liability to the issuer) remains unchanged.
- PSPs must offer at least one SCA method accessible to customers without smartphones, disabilities, or limited digital literacy — requiring ACS routing to alternative challenge methods (hardware tokens, telephone OTP).
- Delegating SCA functions to a third party (3DS Server provider, wallet, gateway) would be classified as outsourcing under EBA guidelines subject to DORA; the PSP remains liable if a delegated party applies SCA incorrectly.
- Formal adoption expected 2027; application likely after ~21-month transition (~2027–2028).
Key terms
| Term | Meaning |
|---|---|
| AReq / ARes | Authentication Request / Authentication Response — the core 3DS messages exchanged between 3DS Server and ACS |
| CReq / CRes | Challenge Request / Challenge Response — messages exchanged during the challenge window |
| RReq / RRes | Results Request / Results Response — sent after challenge completion to notify the 3DS Server |
| CAVV | Cardholder Authentication Verification Value — cryptographic proof of authentication generated by the ACS; validated at authorisation |
| ECI | Electronic Commerce Indicator — code returned by ACS indicating authentication result (05 = fully authenticated; 06 = attempted; 07 = no authentication) |
| RBA | Risk-Based Authentication — the ACS's scoring engine that decides frictionless vs challenge |
| TRA | Transaction Risk Analysis — SCA exemption category; issuer applies it when transaction value and fraud rate are below PSD2 thresholds |
| DS | Directory Server — the card-network component that routes AReq to the correct ACS and manages card ranges |
| HSM | Hardware Security Module — tamper-resistant hardware required for CAVV generation (FIPS 140-2 Level 3+) |
| SPC | Secure Payment Confirmation — FIDO2-based browser challenge method supported in EMV 3DS 2.3+ |
| DTA | Direct-to-Authorisation — sending an authorisation request without a prior 3DS authentication; blocked for French-issued cards since May 2025 |
| Frictionless | ACS decision that authenticates passively (no consumer interaction); returns Y with CAVV |
| Challenge | ACS decision requiring the consumer to actively verify identity (OTP, biometric, SPC) |
| Data-only 3DS | 3DS2 flow that shares risk data without triggering authentication; Visa and Mastercard only |
| LOA | Letter of Approval — EMVCo certification document issued per vendor per spec version |