Release candidate

v2.2-rc2 is not ratified and MUST NOT be used for production. Current: v2.1. Changelog

This is v2.2-rc2 — a release candidate for 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-rc2 changelog for every change in this version.

Validate · Enforce · Trust

Confirmation of Payee — Requirements v2.2-rc22 min read

The User Journeys for this service also apply and must be adhered to.

The tables below list the validation rules that apply to Confirmation of Payee. The Validated by column indicates where each rule is enforced. All requests require an active Trust Framework application with the BSIP role, a valid transport certificate presented on every request via mTLS, and an active signing key for JWT signing.

01 Section

Mandatory CoP Requirement

For all Open Finance account-to-account transfers where the creditor is unknown to the TPP — for example, entered by the customer at the time of payment — a Confirmation of Payee request must be made prior to consent creation, provided the receiving bank supports the CoP service. A creditor is considered unknown when the TPP does not already hold a verified record of the payee (for example, a pre-enrolled beneficiary confirmed by a prior successful CoP check). Where CoP has been performed, the full raw JWS response from the /confirmation endpoint must be included in the ConfirmationOfPayeeResponse field of the creditor entry in the payment consent PII.

02 Endpoint

Payee Discovery

POST/discovery
#
Field
Rule
Validated by
1
Authorization
Must contain a valid Bearer access token obtained via a client_credentials grant with the confirmation-of-payee scope.
API Hub
2
Request body
Must be a compact signed JWT (Content-Type: application/jwt).
API Hub
3
message.Data.Identification
Required. Must be a valid UAE IBAN.
API Hub
4
OpenAPI schema
The request must conform exactly to the POST /discovery OpenAPI schema. No additional or undocumented parameters are permitted.
API Hub
5
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
03 Endpoint

Name Match

POST/confirmation
#
Field
Rule
Validated by
1
Authorization
Must contain a valid Bearer access token obtained via a client_credentials grant with the confirmation-of-payee scope.
API Hub
2
Request body
Must be a compact signed JWT (Content-Type: application/jwt).
API Hub
3
message.Data.Identification
Required. Must be a valid UAE IBAN.
API Hub
4
ConfirmationOfPayeeResponse in PII
Where CoP has been performed, the full raw JWS response string from /confirmation must be included in the ConfirmationOfPayeeResponse field of the creditor entry in the payment consent PII.
TPP
5
OpenAPI schema
The request must conform exactly to the POST /confirmation OpenAPI schema. No additional or undocumented parameters are permitted.
API Hub
6
IBAN not recognised
If the IBAN is not recognised, the response will be 204 with no body.
LFI
7
Account state
An account that is not Active is not reported as an error. The confirmation response is returned whatever the account's status, and Data.AccountStatus carries that status — as Status does on GET /accounts. A 403 is no longer returned because the account is blocked from receiving payments; the account's state is conveyed by Data.AccountStatus instead.
LFI
8
Data.AccountStatus in response
Always present on a confirmation response, alongside NameMatchIndicator. Carries the status of the account at the LFI, using the statuses that apply to current and savings accounts: Active, Inactive, Dormant, Unclaimed, Deceased, Suspended or Closed, with the same meanings as Status on the account resource. The value is supplied by the LFI; a joint account carries a single value.
API Hub
9
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