EMV 3-D Secure (3DS) - Payment Authentication Protocol
Authentication flow requirements (chapter 3: app-based, out-of-band, browser-based) – EMV 3-D Secure (3DS) - Payment Authentication Protocol

EMV 3-D Secure (3DS) - Payment Authentication Protocol 3.1.S12-14: 3.1.S12-14 App: ACS builds the challenge and the SDK renders it (Steps 12 to 14)

The ACS validates the CReq, sets the interaction counter to zero and the challenge completion indicator to N, obtains what the chosen challenge method and the ACS UI type need for display, formats the CRes per Table B.4, protects it and sends it over the established link; the SDK validates the CRes and displays the user interface for the ACS UI type and populated elements.

Maintained by Gerard BlokdykControl text last updated

Other controls in Authentication flow requirements (chapter 3: app-based, out-of-band, browser-based) – EMV 3-D Secure (3DS) - Payment Authentication Protocol

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll EMV 3-D Secure (3DS) - Payment Authentication Protocol controls