Leadex Open Banking Accelerator
Open banking, ready from day one
A packaged open banking platform for banks: developer portal, Consent Management Module, open banking APIs and a sandbox, configured for your bank rather than built from scratch. Start from a working sandbox in weeks, then connect your core systems.

The challenge
Open banking promises a lot, but getting there is slow
Banks are under pressure to offer seamless, secure and innovative digital services. Open banking and open APIs make this possible, but implementing them is hard: you need a platform that simplifies integration, shortens time-to-market and stays aligned with your regulator's framework. Without the right tools, the path to open banking can be long and uncertain.
Our solution
A packaged accelerator, configured per bank
Leadex Open Banking Accelerator brings what every open banking programme needs as one packaged solution: developer portal, Consent Management Module, open banking APIs, sandbox and onboarding of third-party providers. Your bank's names, regulator, currency, payment rails, branding and consent rules are configuration, so a new bank needs no code changes.
Packaged solution
What you get
Developer portal
Built on MuleSoft Anypoint API Experience Hub.
- API catalogue with category filters, OpenAPI specs, “Try it” and documentation for every API
- Self-service onboarding for licensed providers, with bank approval and a branded welcome email
- Sandbox credentials on request, registered automatically in the bank's identity manager
Consent Management Module
A packaged Leadex module that runs alongside the bank's identity manager and follows the bank's consent rules.
- Bank-hosted consent screens in English and Arabic: sign-in, one-time password, account choice and plain-language permissions
- Full consent lifecycle (new, active, revoked, expired, consumed) with configurable expiry, for example 90 days by default
- Instant revocation: every API call checks the consent
Open banking APIs
MuleSoft APIs with a UK OBIE v3.1-style data model, localised for your market.
- Account information, live in the sandbox: accounts, balances, transactions and beneficiaries
- Payment initiation, confirmation of funds and reference data, with specs and sandbox mocks
- Gateway policies for token validation and rate limiting, with consent enforced on every request
The journey
How it works
The customer journey end to end, shown with our demo fintech app and Demo Bank.
Step 1
Connect
A customer opens a fintech app and chooses to connect their bank account.

Demo fintech app: connect a bank account Step 2
Sign in at the bank
The app sends them to the bank's own sign-in page, and a one-time password confirms it's them.

Customers sign in on the bank's own page Step 3
Consent
The customer picks the accounts, sees in plain language what will be shared and for how long, and approves.

The customer decides what to share, and for how long Step 4
Data
The app receives balances and transactions through APIs that check the consent on every call.

Data flows through consent-checked APIs Step 5
Revoke
When the customer withdraws consent, the bank refuses the app's next API call.

Revocation takes effect on the very next call
Configuration, not code
Built for your market
What changes from bank to bank is configuration, not code: one configuration file per bank.
Regulator alignment
Aligned with your regulator's framework, for example the CBK draft Open Banking Framework (Kuwait), the CBJ Open Finance Instructions (Jordan) or UK OBIE-style data models.
Local currency and IBAN
Currency precision, for example KWD with 3 decimals, and your country's IBAN format.
Payment rails
Domestic instant payment rails such as WAMD or CliQ.
Multilanguage support
Every customer- and developer-facing screen is translatable, including right-to-left languages such as Arabic.
Data residency
Runs in the cloud or on-premises and in-region, to meet data-residency rules.

Product tour
Inside the portal




Technology
Built on MuleSoft
The accelerator runs on MuleSoft Anypoint Platform, so your team operates and extends it with tools it already knows.
| Component | Role |
|---|---|
| Anypoint Platform (Design Center, Exchange, API Manager) | Design, publish and govern the APIs |
| Mule runtime: CloudHub 2.0 or Runtime Fabric | Runs the APIs; in-region or on-premises if required |
| Anypoint Flex Gateway | mTLS, token validation and rate limiting at the edge |
| Anypoint API Experience Hub | Developer portal on Salesforce Experience Cloud |
| Anypoint Monitoring | API analytics, logs and alerts |
Delivery
From sandbox to production
An indicative plan from kickoff to production. The actual timeline depends on your core systems and your regulator.
01
Discovery
Confirm scope, the regulator's requirements and your bank's configuration.
02
Sandbox go-live
Developer portal and account information APIs live in the sandbox for providers to test.
03
Payments
Payment initiation and confirmation of funds added to the sandbox.
04
Production hardening
Core banking integration, FAPI and mTLS security, and in-region hosting.
References
Proven in production at banks in the region
A leading bank in Jordan: open banking
- Developer portal, consent management and open banking APIs (account information, payment initiation, confirmation of funds) under the central bank's open finance instructions
- Web and mobile consent, sandbox, English and Arabic
- The first bank in its market to launch open banking, and the first Anypoint API Experience Hub launch in the Middle East
A regional bank: banking-as-a-service platform
- Developer portal with 20+ API products: identity, KYC, accounts, cards, transfers, instant payments, loans, virtual IBAN and more
- Simulated sandbox bank, SDKs, Postman collection, webhooks and documented go-live steps
References available on request.
Next step
Request a guided demo
We walk you through the accelerator on a call and map it to your open-banking roadmap.
- A live walkthrough of the developer portal, consent journey and APIs
- How the accelerator fits your regulator's framework and core systems
- An indicative plan from sandbox to production