Tag Archive for: 3d secure

The decisions EMV 3DS deliberately leaves out of scope

A standard is usually read as an answer sheet. If two products both implement it, the reasoning goes, they behave the same way, and the remaining differences are commercial. EMV 3DS does not work like that, and the places where it does not…

EMV 3DS Version Management: From Protocol Versions to Device Information

Teams new to EMV 3DS usually assume there is a specification, that it has a version number, and that being on that version means being current. All three assumptions are wrong in ways that cause real planning failures. There is a family of…

The field-level rules behind 3DS requestor data quality

Issuers can only assess the risk data they actually receive. That sentence is uncontroversial and almost never acted on, because the data quality problem in 3DS is not a strategic one. It is a hundred small encoding and population decisions…

What a soft decline is and how to respond to one with 3DS

A merchant sends a card transaction straight to authorisation without authenticating first. The issuer declines it, but not because anything is wrong with the card. The decline means something closer to: authenticate the cardholder and come…

How EMV 3DS can carry age and identity verification

Age verification in 3DS is possible, and almost nobody uses it. If you sell alcohol, run a gambling platform, or operate anything a regulator expects you to keep minors out of, you already have an age verification problem and an expensive answer…

How the SDK and ACS interact during an app-based 3DS challenge

An app-based 3DS challenge looks simple from the outside. The cardholder taps, a screen appears, they enter a code, the payment completes. Underneath, the screen they see is the product of a negotiation that runs across four separate messages,…

Why Skipping the 3DS Method URL Raises Your Challenge Rate

If your frictionless rate is lower than your peers and your data quality looks fine, there is a good chance the problem sits earlier in the checkout than you have been looking. Before an authentication request is ever sent, the browser flow…

Choosing a 3DS Server: An Evaluation Guide for Acquirers and PSPs

The 3DS Server sits on the acquirer side of the 3D Secure protocol: it builds and validates authentication requests, routes them to the correct issuer via the Directory Server, and interprets the result. For acquirers, PSPs, and payment gateways,…
EMV 3D SEcire 2 Guide 2026

What Is 3D Secure? A Complete 2026 Guide for Enterprise Payment Teams

3D Secure (3DS) is a payment authentication protocol that protects card-not-present transactions by adding a real-time identity verification step between the cardholder, their issuing bank, and the merchant. 

3D Secure Liability Shift in the United States: What’s Covered and What Isn’t

3D Secure (3DS) can move fraud liability off the merchant and onto the issuer, but only in specific cases. This article explains when liability shift applies in the US, when it does not, and what evidence your team should include when a dispute…