Tag Archive for: ACS

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,…

How Bridging Message Extensions Support New Features in Older 3DS Products

No payments estate upgrades in a single step. Some components move to a new protocol version quickly, others are constrained by vendor release cycles, scheme certification windows or simply by the fact that they work and nobody wants to touch…

How the ACS Information Indicator Tells the Acquiring Side What an Issuer Supports

Most acquiring-side 3DS implementations send the same shaped authentication request to every issuer and find out what happened afterwards. That works, in the sense that transactions authenticate. It also means a good deal of information the…

How the 3DS SDK Gathers, Encrypts, and Transmits Device Data to the ACS

App-based 3D Secure has a reputation for producing better frictionless rates than browser flows, and the reason is usually given as richer device data. That is true, but it is an incomplete answer. The more interesting part is how the data…

When an Issuer Lets the Merchant Authenticate the Cardholder

A cardholder unlocks a retailer's app with their face, browses, and checks out. They are then asked to authenticate again, this time by their bank, using a code sent by text message. The second authentication is weaker than the first and considerably…

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…

What Should Issuers Measure Across 3D Secure Authentication?

Issuers should monitor more than transaction volume. A useful 3D Secure view includes authentication success, frictionless and challenge ratios, decoupled activity, decline reasons, errors, device channels, issuer and scheme views, and trends…

Giving Issuers Greater Control Over the 3D Secure Authentication Experience

Issuer control over the 3D Secure authentication experience includes more than branding. Modern ACS platforms can support configurable content, challenge templates, responsive previews and page flows scoped by issuer, card scheme, authentication…

From Support Tickets to Self-Service in Modern ACS Operations

Modern ACS operations should move appropriate routine configuration closer to the teams responsible for authentication. Structured administration, previews, configurable flows and clearer reporting can reduce operational friction without removing…

Preparing Your ACS Environment for EMV 3DS 2.3.x

Preparing for EMV 3DS 2.3.x requires more than enabling a new message version. Issuers should assess ACS protocol support, authentication capabilities, integrations, infrastructure, operational controls, testing and rollout governance as…