Open Banking (UAE)
In the UAE, Open Finance is centralized: every bank and every TPP connects through Nebras, the regulator's API hub. There's no TPP fan-out at the bank's door — so the question isn't "how many connections," it's "how does the bank stay connected to Nebras as it evolves."
The model — one flow, hub at the center
The bank exposes its APIs once to Audax. Audax runs the certified Nebras connector. Nebras fans out to every licensed TPP in the UAE market.
Audax's transformation engine maps the bank's core APIs to the Nebras specification through configuration, not custom code. The same adapter pattern that's live in production for SNAP is applied to Nebras as part of UAE onboarding.
Nebras certification happens per market and per deployment. Audax's adapter is built to the Nebras spec, so this is a focused validation exercise rather than a rebuild — and ongoing re-certification as the spec evolves is absorbed by Audax, not the bank's team.
AlTareq-compliant consent and authorization flows — redirects, scope selection, approval confirmation — delivered by Audax as branded, ready-to-use screens that meet UAE Open Finance UX requirements.
Nebras spec updates (for example v1.2 → v2.1) are absorbed by Audax. The bank doesn't re-map its core APIs or re-test against a new schema each time the regulator publishes a revision.
Audax owns the running connection to Nebras — monitoring, schema drift, transport changes, security updates. The bank keeps its single connection to Audax stable.
If the bank also wants to consume data from other UAE institutions via Nebras (account aggregation, multi-bank dashboards), Audax provides a unified experience — no separate build.