Functional Certification — Insurance Data Sharing 3 min read
Functional Certification proves that your proposition consumes Insurance Data Sharing correctly: you request only the permissions your endpoints need, across the insurance sectors you support, and you can retrieve that policy data from the AlTareq Model Bank. This page explains what evidence to gather; the portal then builds your submission for you.
Evidence that your proposition consumes the data correctly
Functional Certification is one of the mandatory certification areas a TPP must satisfy before production access. For Insurance Data Sharing, it demonstrates that your consent requests only the permissions your proposition uses, that those permissions align to the endpoints you consume, and that you can retrieve the policy data from the AlTareq Model Bank sandbox.
This area certifies policy retrieval (ReadInsurancePolicies). Consuming the encrypted Premium field — a JWE gated by ReadInsurancePremium — has its own certification and is out of scope here.
Gather this before you start
The portal covers the 14 Insurance Data Sharing endpoints available to TPPs — a policy-collection and a policy-by-id endpoint per sector. Have the following ready:
- Use case — a sentence or two on why you consume this data (for example, aggregating a customer’s motor and health policies to power a coverage-comparison product).
- Your consent (RAR object) — the
authorization_detailsobject you send at/par, and confirmation that its per-sector permissions align to the endpoints you consume. - Postman evidence — for each endpoint you consume, a screenshot showing you retrieved that policy data from the sandbox Model Bank.
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 correctly.
One ZIP to attach to your ticket
When you have filled in the form and attached your screenshots, the portal generates a single ZIP containing a summary document and every screenshot, organised per endpoint. Attach that ZIP to a Service Desk ticket with the Certification Type “TPP Functional Certification Evidence”. Nothing is sent anywhere until you attach it — the submission is built entirely in your browser.