Confirmation of Payee 2 min read
Confirmation of Payee (CoP) lets a TPP verify that an IBAN belongs to the named account holder before a payment is initiated. The check happens outside the consent and authorisation flow — it requires no user interaction, runs against the LFI that holds the destination account, and returns a name-match result in real time.
Bank Service Initiation Provider
Access to the Confirmation of Payee API requires the BSIP role. This role must be assigned to your application in the Trust Framework before calling either endpoint. See Roles for the full list of scopes and grant types this role permits.
CoP is a two-call flow: discovery, then confirmation.
Discovery is called against the API Hub. The TPP submits the destination IBAN; the Hub resolves which LFI holds the account and returns that LFI's discovery endpoint URL and resource server URL.
Confirmation is called directly against the resolved LFI. The TPP authenticates using a client credentials grant (no user redirect), sends a signed request containing the IBAN and account holder name, and receives a signed response with the match result.
/open-finance/confirmation-of-payee/v2.1/discovery/open-finance/confirmation-of-payee/v1.2/confirmationBoth request and response bodies are compact JWS strings (Content-Type: application/jwt). The Hub discovery response carries DiscoveryEndpointUrl and ResourceServerUrl. The LFI confirmation response carries NameMatchIndicator and, on non-Yes results, a MaskedName.
Match results
A Partial or No result must be disclosed to the user — see User Journeys for the required consent and authorisation page behaviour.
ConfirmationOfPayee.YesConfirmationOfPayee.PartialMaskedName to the payer before proceedingConfirmationOfPayee.NoMaskedName to the payer before proceedingWhich LFIs are live for Confirmation of Payee
LFIs currently serving Confirmation of Payee requests across UAE Open Finance.
Browse this section
The full set of pages for the Confirmation of Payee API.
Confirmation of Payee — Requirements
Validation rules and behaviour every CoP request must follow.
Confirmation of Payee — API Guide
Implementation notes for discovery, signed payloads, and confirmation responses.
Confirmation of Payee — User Journeys
How match results must be surfaced to the payer across all scenarios.
Discover the LFI that will confirm the payee
OpenAPI reference for the POST /discovery endpoint.
Confirm the IBAN matches the Name on the Account
OpenAPI reference for the POST /confirmation endpoint.