The Bridging Message Extension lets 2.2 components use 2.3.1.1 features through four data sets: Recurring Data, Challenge Data (automatic switching to the OOB app and entry masking, CReq/CRes in the app flow with message version 2.2.0 only), File URL Data (the 3DS Server downloads the full card range data from a DS file, ignoring card range data in the PRes, when both support it, per section 5.6 of 2.3.1.1) and Additional Data (acquirer country code, authentication method, card security code and its status, device information version recognised, transaction challenge exemption, 3RI and authentication indicators, challenge error reporting and cancellation). The extension version number must be the same across a message pair: a recipient answers with the version it received or leaves the extension out. The Letters of Approval held show Directory Servers tested with EMVCo's suite for version 2.0 of the Bridging extension on 2.2.0 (suite release 2.0.1.5) as well as the 2.3.1 and 2.2.0 suites.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.