Where 3DS Latency Comes from and How to Reduce It

When a checkout feels slow, EMV 3D Secure (EMV 3DS) is often the first suspect. Sometimes that is fair, but 3DS latency is not one number. It accumulates across several steps owned by different parties: the merchant’s page, the 3DS Server, the card scheme’s Directory Server (DS), the issuer’s Access Control Server (ACS) and, in a challenge, the cardholder. Knowing which stage is slow is the only way to know who can fix it.

Where 3DS latency builds up

Stage	What happens	Who controls it	Typical causes of delay
Card range lookup	The 3DS Server checks whether the card is enrolled and which versions apply	3DS Server operator	Stale or missing card range data forcing errors or retries
3DS Method	A hidden frame lets the ACS collect browser information	Merchant page and ACS	Starting the Method late; slow ACS Method page; EMVCo caps the wait at 10 seconds
Authentication request and response	The 3DS Server sends the AReq through the DS to the ACS and receives the ARes	3DS Server, DS, ACS	Network distance; ACS risk engine time; dependencies the ACS calls
Challenge	The cardholder completes an OTP, app approval or other method	ACS and cardholder	SMS delivery; app switching; human time
Results	The ACS sends the final result to the 3DS Server	ACS and 3DS Server	Usually small; delays here affect when checkout can proceed

Frictionless authentications only pass through the first three stages. Challenged ones add the cardholder’s time, which is usually the largest single component and the one engineering can influence least directly.

Levers for merchants and PSPs

Start the 3DS Method as early as the card number is known, so it runs while the customer finishes the form rather than after they press pay.
Do not wait longer than necessary for the Method to complete. The specification limits the wait to 10 seconds; proceed when it completes or when that limit is reached.
Keep card range data fresh, so lookups succeed first time (how card range data shapes 3DS Server reliability).
Measure latency at percentiles (for example the slowest 5 per cent) and by issuer, because averages hide the issuers that cause timeouts.

Levers for issuers and ACS operators

Keep the ACS risk decision path short, and move slow enrichment calls out of the synchronous path where the decision does not need them.
Monitor the dependencies a challenge relies on, such as SMS gateways and push services, separately from the ACS itself.
Host the ACS close to the schemes’ Directory Servers it serves, or in multiple regions for international portfolios.
Track how often requests time out at the ACS, because a slow ACS can be treated like an unavailable one (what happens when an ACS is unavailable).

Testing 3DS latency before it reaches customers

Latency problems are easiest to fix before go-live. Test environments let teams simulate slow and timed-out responses and confirm that the checkout handles them as intended; the peak trading readiness article covers which fallback to apply when a stage runs slow. GPayments’ TestLabs is a 3DS testing environment for that preparation.

Frequently asked questions

How long does a 3DS authentication take?

It varies by issuer, network path and whether a challenge is needed. Frictionless authentications are usually much faster than challenged ones, where the cardholder’s own time dominates. Measure your own percentiles by issuer rather than relying on a general figure.

How long should a merchant wait for the 3DS Method?

The EMV 3DS specification limits the wait to 10 seconds. If the Method has not completed by then, the 3DS Server proceeds and indicates that it did not complete.

Does 3DS latency cause abandoned checkouts?

Long waits can contribute, particularly during challenges and on mobile. Measure abandonment by stage to see whether latency or the challenge itself is the cause.

Who is responsible for a slow ACS?

The issuer or its ACS provider. Merchants can identify slow issuers from their own data and apply their fallback policy, but cannot speed up the ACS.

Does the 3DS protocol version affect latency?

Newer versions add data and features rather than changing the basic message flow. Latency depends more on implementation, network path and issuer behaviour than on version alone.

Reducing 3DS latency in your stack

GPayments provides ActiveServer for acquirers, PSPs and merchants and ActiveAccess for issuers. To discuss where time goes in your authentication flow, contact GPayments.