Native templates (one-time passcode for payment and non-payment authentication, single-select, multi-select and out-of-band instructions) integrate into the 3DS Requestor App's look with issuer content from the CRes, the ACS populating the ACS UI Type and continuing the challenge until it sets the Challenge Completion Indicator to Y. After sending a CReq the SDK keeps the processing screen up until the CRes arrives or the CReq/CRes timeout of 5.5.2.2 expires (Req 4.13); the SDK controls the label of the action that exits to the app (Req 4.14); the 3DS Requestor controls UI interaction such as Cancel, may show a screen title, returns control to its app when Cancel in its header is selected, and has the CReq built in response to the cardholder's interaction (Req 4.15 to 4.18).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.