Open banking · Platform
Open Banking Platform
A single platform layer that connects your business to licensed open banking providers and C2B bank accounts across Europe through one integration. A software platform that connects you to licensed providers, not a bank or a provider itself. One open banking API, one bank data model, one set of webhook events across every supported bank.
viaBanking is a software provider; regulated open banking services are delivered by licensed partner providers.
- 1 APIAcross every supported bank
- LicensedAIS & PIS providers behind it
- A2A + CreditInitiation + credit signal
- EUEuropean bank coverage
- SandboxAvailable on request
What is an open banking platform?
An open banking platform is a software layer between your product and the licensed providers that reach every bank. It hosts one open banking API, one bank data model and the webhook events that carry each payment state back to the business. It is not a regulated operator on its own account.
viaBanking is that layer. The platform = software layer. Regulated open banking actions — payment initiation and account access — are performed by licensed AIS and PIS providers. viaBanking does not act as a bank, a card gateway or a payment processor, and does not hold or move funds.
The fragmentation the platform removes
Direct bank connectivity fragments across markets, APIs and consent screens. The platform absorbs that fragmentation into one open banking API contract.
-
One connector per bank
Each bank ships a slightly different open banking API and its own error taxonomy. Going bank by bank compounds engineering and vendor management as the business adds new markets.
-
Integration cost fragmentation
Every licensed provider has its own commercial terms. Some are volume-tiered, some are free above a turnover threshold, some are per call. The build-your-own path leaves those trade-offs on the business.
-
Payment initiated ≠ funds arrived
A raw open banking API returns "payment initiated" but not "funds credited". The blind spot is what a business really needs to close on the merchant side, and it is what the platform surfaces natively.
What the platform gives you
Six components on one open banking API contract. Regulated open banking actions are performed by licensed AIS and PIS providers; the platform orchestrates the connection.
- API
One API, one data model
One open banking API contract on top of many bank APIs. The same data model per bank means the product code paths do not fan out per provider; new banks reuse the same data schema.
- Routing
Orchestration & provider routing
Every open banking API call is routed to the appropriate licensed provider per market. If a provider degrades, the layer can fail over to a secondary partner that also reaches the same bank, so business events keep flowing.
- Consent
User's payment consent flow
The user's payment consent flow is orchestrated by the licensed PIS provider. SCA is hosted and verified by the customer's account-issuing bank. No credentials or user data touch the platform.
- A2A
Payment initiation
A2A payment initiation is performed by a licensed PIS provider on the merchant's behalf. The platform posts one open banking API call and normalises the response so the business reads one shape across every bank.
- Verify
C2B account credit verification
The platform confirms, via the account provider's API in read-only mode, that funds have actually been credited to the merchant's C2B collection account. Not a statement read; a settlement signal on the merchant side.
- Ops
Sandbox, webhooks, monitoring
A secure sandbox behaves like the live open banking API. Signed webhook events land per state change. Provider status is monitored on uptime, response time and error rates, so degradations are visible before they hit the business.
We orchestrate the connection; we do not replace your provider or your bank relationships, and we do not hold funds. Financial services teams use one API contract and reuse the same API events across every open banking service the platform ships. Each API on the platform is aligned with the underlying licensed provider APIs, so an engineering team learns one API and uses that same API across every open banking service, every A2A payment call, and every new financial services feature the team ships. Product teams use the same API surface for merchant services, treasury services and reconciliation services on one contract.
Coverage and reliability
Coverage is built up market by market. Pre-integrated licensed providers reach every supported bank across the European Union, and the platform picks the healthiest route per call. Adding a new bank or a new market is a configuration change on our side, not a fresh integration on yours.
Reliability comes from the routing layer. The platform monitors every licensed provider on uptime, response time and error rates. If a provider degrades, the platform can fail over to a secondary partner that also reaches the same bank, so business events keep flowing without a manual switch.
Confirmed credit into the C2B bank account
Every raw open banking API tells a business the payment was initiated. The platform goes one step further: it confirms, via the account provider's API in read-only mode, that funds have actually been credited to the merchant's C2B collection account, so the business only fulfils against a real settlement.
There are cases where the user can revoke payment consent before the funds leave the bank; whether this is possible depends on the bank's own processes. The platform surfaces the actual result either way. For the full walkthrough on the merchant side, see open banking solutions.
Security, consent and compliance
- Software
Software layer, not a licence
The platform is a software contract. viaBanking does not act as an AIS or PIS provider on its own account, and does not hold or move funds.
- Licensed
Regulated actions stay with partners
Payment initiation runs through a licensed PIS provider. Confirming the credit into the C2B collection account is done via the account provider's API in read-only mode. SCA is hosted and verified by the customer's account-issuing bank.
- Data
Data minimisation by design
The platform does not receive banking credentials and never handles user login screens. Personal data handling follows our Privacy Policy.
Frequently asked questions
-
Is viaBanking a bank, a gateway or a payment processor?
No. viaBanking is a software platform and orchestration layer over licensed open banking providers. The platform does not act as a bank, a card gateway or a payment processor on its own account.
-
Does viaBanking hold your own AIS or PIS licence?
No. Regulated open banking actions are performed by licensed third-party AIS and PIS provider partners. Specific regulatory statements per market are confirmed with legal review before we publish them.
-
Do you hold or move customer funds?
No. Funds stay with the licensed provider and the customer's bank. The platform confirms when funds have actually been credited to the merchant's C2B bank account, so the business sees the real settlement result.
-
How is the platform different from connecting to each bank directly?
Direct bank integrations are per bank and per licensed provider. The platform gives you one open banking API, one bank data model and one set of webhook events across every supported bank, so a new bank or a new market is a configuration change on our side.
-
Do you offer a sandbox and how does go-live work?
Yes. The sandbox is available on request and behaves like the live open banking API. Going live is a key swap; the same integration reads the same events and the same bank data model as in the sandbox.
Products and services on the open banking API platform
Financial services teams build a range of products on the viaBanking open banking API platform. Merchant checkout products, payout products, reconciliation products, and subscription products — each product is one financial services workflow that reads the same open banking APIs behind the platform. Financial teams use the same open banking APIs for A2A payment products and for credit-verification products against the C2B bank account; every new financial services product adds to the same integration.
The API is one, so engineering teams do not learn a new API per bank. Product teams use the same API events across every open banking service the platform ships. The platform ships with developer resources that help a financial services team use the open banking APIs faster: reference resources for every endpoint, ready-to-use code resources, sandbox resources, and design resources for the customer-facing surface. Each of these resources is versioned alongside the open banking APIs so the same integration reads consistent events per product release.
One platform for open banking payments across Europe
Talk to sales about a European coverage plan, or head to the developers page for the endpoint-level view. For a scenario-first read, see open banking solutions.
viaBanking is a software provider; regulated open banking services are delivered by licensed partner providers.