Functional Certification — Bank Data Sharing 3 min read
Functional Certification proves that your Ozone Connect implementation of the Bank Data Sharing endpoints returns correct, complete data — endpoint by endpoint — and that the same data flows through the API Hub to a TPP. This page explains what the evidence is and how to produce it; the portal then builds your submission for you.
Evidence that your Ozone Connect endpoints work end to end
Functional Certification is one of the certification areas an LFI must satisfy before publishing API resources to the production Trust Framework. For Bank Data Sharing, it demonstrates — endpoint by endpoint — that your Ozone Connect endpoints behave as the standard requires, and that the same data is correctly returned to a TPP through the API Hub resource server. All evidence must come from the AlTareq Model Bank sandbox.
Gather this before you start
The portal walks you through 12 Bank Data Sharing endpoints. For every endpoint your implementation exposes, have the following ready:
- Testing Tool output — the HTML report the Testing Tool produces for your Ozone Connect endpoint (e.g.
GET /accounts/{AccountId}/balances). - Outcome & notes — whether every test passed, and where any failed or were skipped, a short explanation of why.
- Postman success screenshot — a screenshot from the Postman collection showing a successful response from the TPP-facing equivalent endpoint on the API Hub resource server (e.g.
https://rs1.LFICODE.apihub.openfinance.ae/open-finance/account-information/v2.1/accounts). - Full JSON response — the complete JSON body returned by that same TPP-facing call.
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 and every file you uploaded, organised per endpoint. 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.