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 TPPs to hold the BSIP role. The API Hub validates the role on every request before proxying it to the LFI.
Who's using Confirmation of Payee
TPPs currently calling the Confirmation of Payee API 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 your Ozone Connect CoP endpoint must follow.
Confirmation of Payee — API Guide
Implementation notes, payload structure, and worked examples.
Confirmation of Payee — User Journeys
The end-to-end flows your customer experiences when CoP runs against your account data.
Confirm the IBAN matches the Name on the Account
OpenAPI reference for the POST /customers/action/cop-query endpoint.