The ACS may give the cardholder a message in a frictionless or decoupled response through Cardholder Information Text: text of 1 to 128 characters, optionally with issuer and payment system image URLs, required in the ARes when the ACS confirms decoupled authentication and optional in the RReq. The 3DS Server passes it to the requestor, which shows it to the cardholder as section A.20 illustrates. In the RRes the 3DS Server reports the Results Message Status: 01 RReq received for further processing, 02 CReq not sent because the requestor chose not to challenge, 03 ARes with status C or D not delivered to the requestor for a technical reason, 04 the 3DS Server will run decoupled authentication in a later authentication. The final CRes may carry only status Y, N or D, and statuses C and S are not allowed in the 3RI channel.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.