Reach your customers’ banks, with their say-so
Standard Open Banking APIs for accounts, payments and consent, against the institutions your customers already bank with. Register an app and its test customers and accounts are waiting for you — no ticket, no queue.
A bank or an electronic money institution? Enrol as a service provider — self-service, reviewed by our team, on plans of your own.
Everything you need to build
financial applications
10 APIs covering accounts, payments, consent, cards and identity — the same endpoints in the sandbox as in production.
Account Information
Retrieve account balances, transaction history, and account details with comprehensive filtering and pagination.
Payment Initiation
Single, bulk, and scheduled payments with real-time status tracking. Support for domestic and cross-border transfers.
Fund Confirmation
Real-time fund availability checks before initiating payments to reduce failures and improve user experience.
Identity Verification
KYC-compliant identity verification and validation services integrated with banking systems.
Account Access Consent
Ask a customer for access to their accounts at their own institution, and read only what they authorised, for as long as they allow it.
Card Issuance & Management
Virtual and physical card provisioning, card controls, limits management, and real-time card notifications.
Notifications
Multi-channel notification delivery including email, SMS, and push notifications for transaction events.
Authentication & Authorization
Token-based authentication with client credential support, session management, and per-app access controls.
Open Data
Public banking data including branch locations, ATM networks, product catalogs, and exchange rates.
Customer Support
Programmatic support ticket management, FAQ search, and customer communication APIs.
RESTful APIs built for speed and simplicity
Clean, predictable endpoints with consistent response formats. Full OpenAPI 3.0 documentation with an interactive sandbox for testing.
Go from sign-up to live in minutes
Four steps, and the only one you wait on is the review of your app — not of your test data.
Register as Partner
Create your developer account and company profile in under 2 minutes.
Register Your App
Describe your application and use cases. Its test customers and accounts are provisioned as you submit it.
Get Credentials
Your Client ID is issued on approval. Your test data is already there.
Start Building
Call the APIs against your own test customers, and reshape their data whenever you need to.
Test data that arrives with your app
Register an application and it is provisioned with its own bank customers — each one holding real, callable accounts. Nothing to request, nobody to wait for, and no shared fixtures to trip over.
It is yours to run: rename a customer, change a balance, open another account, mark someone inactive to exercise a rejection, or reset the whole set back to a known-good starting point after a messy afternoon.
Provisioned instantly
Created with the registration itself, not after a review. Your first API call does not have to wait for approval.
Yours to edit
Customers, accounts, balances and statuses are all editable from the portal by your owners and administrators.
Reset on demand
One click puts the customers, the accounts and their transaction history back to the defaults for your plan.
Scoped to your team
Every application gets its own set, and the whole organization can see them. No other organization can.
Your team, your plan, your invoices
Everything an organization needs to manage itself, without opening a support ticket.
One shared workspace
Applications, accounts, sandbox data and tickets belong to the organization, so your colleagues see the work you started.
Owners and administrators
Plan changes, billing details and shared test data are limited to the people you trust with them. Everyone else can still read.
Billing you can see
Your billing details, the PayPal account paying, and every payment, refund and plan change — on one page, in the portal.
Reach your customers' banks — because they said so
Your sandbox is yours. Somebody else's accounts are theirs, and the only way across that line is the account holder's consent: granted by them, at their institution, over the accounts they choose.
Get registered first
Ask the institution to register your application, saying what you intend to request and what you do with it. It decides before any of its customers is approached.
The customer decides
You send them a link. They sign in at their institution, see who is asking and for what, tick the accounts they mean to share, and authorise or refuse.
Only what they shared
Quote the consent and the accounts they chose appear alongside your own. Not their other accounts, not another customer's, and never a write.
Payments, one at a time
A payment is its own consent: the amount and the payee fixed before they see it, authorised once, used once. Send anything different and it is refused.
- They can take it back. The customer withdraws access from their own page, and so can the institution. It stops on the next call.
- It runs out. Ninety days at most, then they are asked again — access nobody remembers granting is access nobody granted.
- Every step is kept. Who asked, who authorised, over which accounts, and who ended it — the two questions a dispute always comes down to.
Join as a service provider, on your own terms
Institutions enrol themselves — no email thread, no queue behind somebody's inbox. What we review is the enrolment; what you decide is everything after it.
Enrol yourself
Your legal entity, your regulatory authorisation, your contacts, your evidence, and a declaration signed by an authorised representative. Save it in stages; submit when it is complete.
Your customers
Open customers with sign-ins of their own and accounts held at you. When a third party asks, the account holder answers — not your staff on their behalf. They get a portal of their own to answer from.
Who may ask
Applications request registration with you before they can approach anyone. Approve, refuse with a reason, or suspend — and the consents your customers already gave stay theirs.
Every consent, in one place
Which applications are reading which customers' accounts, since when, and until when. Answerable to your customer, because you can actually answer.
When they leave
A customer can ask to be closed down. Their third-party access ends the moment they ask — that part is theirs. Closing the accounts is yours, so the request comes to you to complete or refuse with a reason.
Details that stay current
Customers change their own email address, confirming the new one before it takes effect. You are told when it happens and keep a record of what it was, because it is where you reach them.
Bank-grade security at every layer
What protects an account here is the same thing that protects it at the bank: nobody reaches it without the holder saying so.
TLS Encryption
All communications encrypted over HTTPS with optional two-way TLS.
Token Auth
Secure token-based authentication with configurable expiry per app.
Tenant Isolation
Every account, app and ticket belongs to your organization. Colleagues share it; nobody outside can reach it, except through a consent its owner granted.
Compliance Ready
Built for Open Banking regulatory compliance and audit trails.
Power any financial application
Six things teams have built on endpoints like these.
Neobanks & Digital Wallets
Account management, payments and card controls behind your own front end.
E-Commerce & Marketplaces
Embed payments, fund verification, and instant payouts directly into your checkout and seller disbursement flows.
Personal Finance Management
Build budgeting, expense tracking, and financial planning tools with real-time account data and transaction categorization.
Lending & Credit Platforms
Assess borrower eligibility with identity verification, fund confirmation, and account data aggregation APIs.
Payroll & Disbursements
Automate salary payments and bulk disbursements with scheduled and bulk payment APIs for any scale.
Banking-as-a-Service
Embed banking capabilities into any platform. Our white-label APIs let you offer financial services under your own brand.
Built with best-in-class technology
Start free. Scale when you're ready.
No upfront costs. No hidden fees. Every application you register is provisioned with its own test customers and accounts the moment you create it — nothing to request, nothing to wait for.
These are the plans for partner developers. Banks and electronic money institutions have their own tiers — see service provider plans.
Sandbox environment for development and testing
- Full API access
- 1,000 API calls / month
- 2 test customers per app, provisioned instantly
- 25 accounts, 2 apps
- Interactive sandbox
- Community support
Sandbox environment for full-scale integration work
- 50,000 API calls / month
- 250 accounts, 10 apps
- 8 test customers per app, cards included
- Edit and reset your test data on demand
- Scheduled & bulk payments
- Card management
- Priority support
- Your own test backend, quoted separately
Production environment for banks and large institutions
- Production environment access
- Unlimited API calls
- Unlimited accounts & apps
- Full test-customer roster per app
- All features included
- 24/7 dedicated support
- Custom SLA
Already subscribed? You keep the price you signed up at — these prices apply to new subscriptions.
Need a Custom Solution?
For large organizations with specific requirements, we offer custom enterprise plans with dedicated support, custom integrations, and flexible billing.
Two ways in. Pick yours.
Two ways in: sign up as a partner developer to build on the APIs, or enrol as a service provider if you hold your customers' accounts.
Institutions join the scheme through service provider enrolment, and are published in the provider directory.