Sequences
Four flows: enrolment (once per connector), a mandate (once per audience, checked against the agent's mission), a call to a partner, and revocation. The person appears only in the first two.
Enrolment
The customer's passkey sign-in and the device evidence both commit to the keys being enrolled; the bank then makes the agent a federation entity whose Entity Configuration the agent signs itself.
A mandate, for one audience
FAPI 2.0-shaped: PAR, PKCE, DPoP, iss in the response. The attestation authenticates the client at PAR and at the token endpoint; PingFederate never sees the attestation itself, only a private_key_jwt the filter mints after verifying it. Each authorization_details entry names what, where and why, and PingFederate's RAR processor asks the PDP about every entry before the customer sees a consent page.
Each audience - the bank's API, the partner - is its own mandate: PingFederate ties a grant to one token manager, and each manager stamps one aud.
A call to a partner
The partner has never met the connector. Its enforcement point is configured by the federation, and every decision comes from PDPs that resolve their own inputs from the anchor's pinned keys.
Revocation
