Open Banking
DigiFI
Consent-based Open Banking APIs for teams building financial products
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.
- 10 API domains
- 50+ endpoints
- Consent-scoped access
- Free to start
The Problem
Banking rails take quarters, not sprints
Shipping a product that touches money means bank connections, payment rails, KYC, card issuing, and the compliance work under all of it. Most teams spend their first two quarters building none of the thing they set out to build.
Before
A separate integration per bank, per rail, per vendor — each with its own auth, formats, and failure modes.
After
One RESTful suite across ten domains, one token, one set of response formats, and test customers of your own to prove it against first.
API Suite
Ten domains, one integration
Fifty-plus documented endpoints covering accounts, payments, consent, cards and identity — the same endpoints in the sandbox as in production.
Account Information
Balances, transaction history, account details with filtering and pagination.
Payment Initiation
Single, bulk, and scheduled payments, domestic and cross-border, with real-time status tracking.
Fund Confirmation
Real-time fund availability checks before initiating a payment, to cut failed transactions.
Identity Verification
KYC-compliant identity verification 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, controls, limits, and notifications.
Notifications
Multi-channel delivery (email, SMS, push) for transaction events.
Authentication & Authorization
Token-based auth, client credentials, session management, per-app access.
Open Data
Public banking data: branch locations, ATM networks, product catalogs, and exchange rates.
Customer Support
Programmatic ticketing, FAQ search, and customer communication APIs.
Developer Experience
Read the response, not the manual
Clean, predictable endpoints with consistent response formats. Full OpenAPI 3.0 documentation with an interactive sandbox for testing, and the same endpoints in the sandbox as in production.
Initiate a payment
POST /api/v1/payments/single
{
"fromAccount": "1234567890",
"toAccount": "0987654321",
"amount": "2500.00",
"currency": "USD"
}
// 200 OK
{
"transactionId": "txn_8f3a...",
"paymentStatus": "COMPLETED"
}A sample of the surface
- GET
/api/v1/accounts/Retrieve all accounts - POST
/api/v1/payments/singleInitiate single payment - POST
/api/v1/payments/bulkInitiate bulk payment - POST
/api/v1/fund-confirmation/Check fund availability - GET
/api/v1/identity/verifyVerify user identity - POST
/api/v1/consents/Ask a customer for account access - POST
/api/v1/auth/loginAuthenticate and get a token
Getting Started
Four steps to your first call
No contract to start, and the only step you wait on is the review of your app — not of your test data.
Register as a partner
Create a developer account and company profile in under two minutes.
Register your app
Describe the application and its use cases. Its test customers and accounts are provisioned as you submit it.
Collect 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.
Developer Sandbox
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.
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 Organization
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.
Consent
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.
Banks & Electronic Money Institutions
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.
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.
Enrolled institutions are issued a directory ID and published in the provider directory, and run on service provider plans of their own. Talk to us about enrolling.
Use Cases
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 into checkout and seller flows.
Personal Finance Tools
Build budgeting and planning products on real-time account data and transaction categorization.
Lending & Credit Platforms
Assess borrower eligibility through identity verification and account data aggregation.
Payroll & Disbursements
Automate salary runs and bulk disbursements at any scale, with per-payment status tracking.
Banking-as-a-Service
Embed banking capabilities into any platform under your own white-label brand.
Security & Compliance
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 traffic encrypted over HTTPS, with optional two-way TLS for partners that require it.
Token Auth
Token-based authentication with configurable expiry, scoped per application.
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, with audit trails on every call and on every consent.
Built With
The stack under the API
The platform choices under the API, stated rather than implied.
Pricing
Start free. Scale when you’re ready.
No upfront costs and no hidden fees. Every app you register is provisioned with its own test customers and accounts the moment you create it — nothing to request, nothing to wait for. The two lower tiers are sandbox environments; production access begins at Enterprise.
These are the plans for partner developers. Banks and electronic money institutions have their own tiers on service provider plans.
Sandbox
$0
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 Plus
$79/mo
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
Enterprise
$299/mo
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. Custom Enterprise plans are also available: dedicated support, custom integrations, flexible billing, and an on-premise option. Talk to sales.
Also From Pocket Pass Digital
Three more tools built the same way
Two ways in. Pick yours.
Sign up as a partner developer to build on the APIs — your app’s test customers and accounts are waiting for you the moment you register it. Or enrol as a service provider if you hold your customers’ accounts.