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.S5: App: 3DS Server verifies the SDK, routes and sends the AReq (Step 5)

What does 3.1.S5 require?

The 3DS Server verifies the authenticity of the 3DS SDK and ends processing if it cannot; generates the 3DS Server Transaction ID; obtains the 3DS Requestor ID, the acquirer BIN where required, and its reference number; ensures the AReq information of Table B.1 is available, ending processing otherwise; determines the DS from the BIN under ISO 7812 and optionally other account data; establishes the mutually authenticated link with the DS; formats the AReq; and sends it, ending processing on failure or timeout.

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.