Draft

This is v2.2-draft — a working draft of the v2.2 standards, published for review and not yet ratified. It MUST NOT be used as the basis for a production implementation. For the current standards, switch to v2.1 using the version selector. See the v2.1 → v2.2-draft changelog for every change in this version.

Validate · Enforce · Trust

ATMs — Requirements v2.2-draft2 min read

The tables below list the validation rules that apply to the ATM API. The Validated by column indicates where each rule is enforced.

All requests require an active Trust Framework application with the BDSP role, a valid transport certificate presented on every request via mTLS, and an active signing key for JWT signing.

01 Endpoint

List Atms

GET/atms

Field

Rule

Validated by

Authorization

Must contain a valid Bearer access token obtained via a client_credentials grant with the atm scope.

API Hub

x-fapi-interaction-id

Should be included. Should be a valid UUID (RFC 4122). An invalid value will not cause a failure but tracing will not be possible.

N/A