Functional Certification — Confirmation of Payee 3 min read
Functional Certification proves that your Ozone Connect Confirmation of Payee implementation returns the correct account-holder name, and that the API Hub then produces the right name-match verdict — Yes, Partial, No, and account-not-found — for the payee names a TPP submits. This page explains what the evidence is and how to produce it; the portal then builds your submission for you.
Evidence that your cop-query drives the right verdict
Confirmation of Payee has a single Ozone Connect endpoint, POST /customers/action/cop-query. Unlike Bank Data Sharing, the LFI does not decide the match — your endpoint returns the account-holder name and the API Hub applies the name-matching rules to produce the verdict. Functional Certification therefore proves each match outcome, per segment: that the name you return, matched against the name a TPP submits, yields the correct NameMatchIndicator. All evidence must come from the AlTareq Model Bank sandbox.
Gather this before you start
You choose the version and segments (Retail is evidenced with a personal name; SME and Corporate with a business name), then evidence each of the 4 outcomes per segment. Have the following ready:
- Testing Tool output — one HTML report the Testing Tool produces for your Ozone Connect
cop-queryendpoint. - Requested name & IBAN — for each outcome, the name and IBAN you sent in the confirmation request. Craft the name to force the outcome: exact for Yes, close for Partial, different for No, and an unrecognised IBAN for account-not-found.
- Name you returned — the full name (and, if collected, first and last name) or business name your
cop-queryreturned as the LFI. Account-not-found returns an emptydataobject instead. - Postman verdict screenshot — a screenshot from the Postman collection showing the TPP-facing
POST https://rs1.LFICODE.apihub.openfinance.ae/open-finance/confirmation-of-payee/v2.1/confirmationresponse with the expectedNameMatchIndicator(or HTTP 204 for account-not-found).
Your organisation and name are taken from your Sandbox Trust Framework sign-in — you do not type them in. Sign in when the portal prompts you so your submission is attributed to your LFI.
One ZIP to attach to your ticket
When you have filled in the form and attached your evidence, the portal generates a single ZIP containing a summary document, your Testing Tool report, and every screenshot, organised per scenario. Attach that ZIP to a Service Desk certification-evidence ticket. Nothing is sent anywhere until you attach it — the submission is built entirely in your browser.