Build your submission

Your details

Your organisation and name are taken from your Sandbox Trust Framework session — the same sign-in used across the portal. Sign in so your submission is attributed to your organisation.

Proposition & consent

Tell us briefly why you consume Bank Data Sharing, pick the version and endpoints you consume, and provide the consent you request.

A sentence or two on what you use this data for — for example, powering a retail personal finance management (PFM) product with the customer’s balances and transactions.

Edit the authorization_details entry below to match your consent request. This is the Rich Authorization Requests (RAR) object defined by RFC 9396: the entry you send at /par that declares the permissions and scope of the consent. It is validated against the OpenAPI schema — edits commit on blur, and anything that does not match the schema reverts.

Evidence

For each endpoint, attach a Postman screenshot showing you successfully retrieved the data from the sandbox AlTareq Model Bank. Start from the Model Bank’s discovery endpoint:

Model Bank .well-knownhttps://auth1.altareq1.sandbox.apihub.openfinance.ae/.well-known/openid-configuration

Consent management

These consent-lifecycle operations are certified for every TPP, whichever endpoints you consume. Retrieve and revoke a consent you staged against the sandbox Model Bank, and attach a Postman screenshot of a successful call for each.

Endpoint evidence

Review & generate

Review the summary below, add any comments, then download your submission. The ZIP contains a summary.html plus every screenshot — attach it to your TPP Functional Certification Evidence Service Desk ticket.

Organisation

—

Submitted by

—

Version

V2.1

Segment

—

Endpoints consumed

0

Consent operations

2

Permissions aligned

Not confirmed