EMV 3-D Secure (3DS) - Payment Authentication Protocol
Message handling requirements (chapter 5) – EMV 3-D Secure (3DS) - Payment Authentication Protocol

EMV 3-D Secure (3DS) - Payment Authentication Protocol 5.2-4: 5.2-4 Outages, availability and error codes

A component that detects a system failure stops accepting requests until corrected and answers outstanding requests with an Error message carrying code 98 or 99; components are recommended to be architected for high availability without relying on another component for routing or load balancing or on stored alternative URLs alone; every component accepts any value in the Error Code and IReq Code fields and uses the closest listed code where no exact match exists.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • P2-3.5.1 P2-3.5.1 Availability mechanisms against loss of 3DS processing

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Message handling requirements (chapter 5) – EMV 3-D Secure (3DS) - Payment Authentication Protocol

Query this from an agent

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