Open banking API platform
One open banking API platform for every financial services team
The viaBanking open banking API platform connects financial services teams to AIS account data and PIS payment initiation from licensed providers, plus account verification, on one open contract. viaBanking is the software layer; regulated services are performed by licensed partner institutions, with the user's payment consent captured on their own bank.
- Products in the platformGrowing catalogue
- Bank access2,500+ banks
- Open banking APIsAIS · PIS
- Developer resourcesSandbox & docs
- Uptime99.99%
Definition
What is an open banking API?
In business terms, an open banking API is a regulated interface that lets financial services teams access bank data through a licensed AIS provider and route payment initiation through a licensed PIS provider, with the user's payment consent captured on their own bank. On the viaBanking platform, one open banking API contract covers connectivity to every bank, every consented account and every payment flow routed through the provider partners the platform integrates. The platform behaves like a single service: one service tier, one service contract, one bill.
Technically, the open banking API is the AIS and PIS specification wrapped in a normalising layer. The platform translates each bank's open APIs into one financial data model, so your products access one endpoint instead of twenty new bank APIs. Read the banking API primer for the connectivity service, or the solutions overview to see the service mapped to real financial services use cases.
Products & services
Products & services in the platform
Every product below runs on the same open banking API contract. The data service, the payment service and the verification service share the same auth, the same webhook set and the same financial data model. Use one service, use several services, pay only for what your financial services team ships. New products are added to the platform on the same contract, without a rewrite.
- Bank connectivity
Banking API
Bank connectivity as one open API. AIS data, PIS payments and normalised bank responses across the platform.
Open product page - Payments
Payment initiation API
The PIS layer of the open banking API. Start any bank payment through the platform, on one contract.
Open product page - Payments stack
Payment initiation services
The bundled pay-by-bank flow: routing to licensed PIS providers, status, webhooks and settlement verification on one open banking platform.
Open product page - Verification
Bank account verification API
Ownership, IBAN and name-match verification services on the open banking API platform. One API call, any bank.
Open product page
Not on the list?
Didn't find the product you need?
Our platform ships more open banking services than the four above, and their scope grows with every new bank onboarded. Tell us the financial data or payment flow your product needs and we'll shape the right open banking API integration for you.
Comparison
Direct bank APIs vs the open banking API platform
The gap between a per-bank stack and the viaBanking platform, row by row.
| Direct bank APIs | viaBanking platform | |
|---|---|---|
| Bank access | New integration per bank | One open banking API for every bank |
| Data model | Different per provider | One financial data schema in the platform |
| Products | Buy each service separately | Products bundled on the platform |
| Resources | Fragmented per bank | Central developer resources |
| Time to first call | Weeks per bank | Under a day, per platform sandbox |
| Provider compliance | Tracked per bank, per market | Provider compliance surfaced in one place |
Developer resources
Every resource in one place
The open banking API platform includes the developer resources most financial services teams reach for on day one. Sandbox access, code samples, full API reference and support resources sit on the same open developer portal, so new engineers get to a green build without a procurement email. Every resource, every service, every API is documented in one place.
Platform outcomes
What financial services teams ship on the platform
- 01
2,500+
Banks & EMIs on the platform
- 02
30+
European markets covered
- 03
99.99%
Open banking API uptime
- 04
< 1 day
From sign-up to sandbox call
- 05
seconds
Payment initiation call
FAQ
Common questions about the platform
What products does the open banking API platform include?
The platform ships four products on one open contract: the Banking API for bank connectivity, the Payment initiation API for PIS, Payment initiation services for the fuller pay-by-bank stack, and the Bank account verification API for account checks.
How does the platform compare to using bank APIs directly?
Direct bank APIs mean a new integration per bank, per market, per product. The viaBanking platform normalises data, payments and access on one open banking API, so financial services teams ship in days rather than months.
Which financial services can use the open banking API?
Any regulated financial services firm can use the platform: banks, EMIs, lenders, marketplaces, insurers and fintechs. The same open banking API serves consumer and business products across every supported market.
What developer resources are included?
Sandbox access, code samples in five languages, full API reference, changelogs, a status page and support resources. All resources are on one developer portal with no procurement gate.
Does the open banking API support user's payment consent and SCA?
Yes. Every open banking API call runs with the user's payment consent captured on their bank. SCA is handled bank-side and the platform stores the consent per financial services scope.
Ready to build
Ship on the open banking API platform
Sandbox access is free. Use the platform as one service for one product, or as a bundled service for all four products, in any European market. Your data stays scoped to their bank consent on every service call.