EMV 3-D Secure (3DS) - Payment Authentication Protocol 3.1.S5: 3.1.S5 App: 3DS Server verifies the SDK, routes and sends the AReq (Step 5)

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.