Open banking · Orchestration layer
Open banking infrastructure
An open banking orchestration layer connects your business to licensed open banking providers and C2B bank accounts across Europe through one integration. Use one open banking API, one bank data model and one contract to reach every supported bank in the open banking network. This is not a bank, not a BaaS, not an open banking provider itself.
viaBanking is a software provider; regulated open banking services are delivered by licensed partner institutions.
- One integration
- Pre-integrated providers
- AIS and PIS via providers
- Sandbox and live keys
- REST + JSON
- Developer-ready
01 · Concept
What is an open banking layer?
An open banking orchestration layer is the software surface between your business and the licensed open banking providers that reach every bank. It hosts one open banking API, one bank data model and the payment consent flow that a shopper uses to authorise a bank connection. It routes each open banking API call to the appropriate open banking provider, monitors the provider's service for uptime, speed and error rates, and returns a normalised bank data payload to your business.
viaBanking is that layer, not a bank, not a BaaS platform and not an open banking provider itself. Regulated open banking actions, such as bank account access, payment initiation and strong customer authentication, are performed by the licensed provider and the shopper's own bank. viaBanking's open banking layer sits above those licensed providers so a business can use every bank in the network through one open banking API, one open banking data model and one secure integration.
- Software boundary viaBanking is the layer, not the bank
- Licensed rails AIS and PIS run through partners
- SCA on the bank Credentials never touch viaBanking
- Config, not code A new market is a switch, not a sprint
02 · Build vs buy
The build-vs-buy problem
Building your own open banking layer bank by bank is expensive. Each bank exposes a different open banking API, a different bank consent screen and a different bank data schema. Each open banking provider ships its own SDK, its own bank coverage matrix and its own error taxonomy. Every new market means another provider and another set of bank connectors for a business to maintain.
The cost is not just the first build. Bank APIs change, provider APIs change, consent windows change; and every change becomes a ticket for your business team instead of a change in the product. Payment lifecycles differ per bank, and the shopper experience differs per provider unless something normalises them. That normalisation is what an open banking layer does: it turns many bank connections into one secure open banking surface a business can use, without paying the ongoing tax of a per-bank integration.
03 · Components
What the open banking layer gives you
The layer packages the components a business needs to use open banking safely and consistently, from the shopper's payment consent through to payment settlement at the shopper's bank.
- API
One open banking API, one data model
There is one account data shape and one payment shape across every bank and every open banking provider, so a shopper flow looks the same regardless of the underlying bank. Your business writes one open banking API integration and every bank in the network reuses it.
- Routing
Routing and failover
Each open banking API call is routed to the healthiest open banking provider that reaches the target bank. If a provider degrades, the layer can fail over to a secondary provider that also reaches the same bank, so a business can keep the payment flowing without a manual switch.
- Consent
Consent and authentication
The shopper authenticates on the shopper's own bank domain using strong customer authentication. The layer coordinates the shopper's payment consent through a licensed provider; banking credentials never pass through the business or through viaBanking, so the bank login stays secure end to end.
- AIS
Fund arrival check via providers
Through a licensed AIS provider, viaBanking connects to the shopper's bank in read-only mode to confirm that the shopper's payment has actually arrived in your Collection Account. The signal lands in one open banking data model, so a business can use it for account credit verification and reconciliation without a bank-by-bank branch.
- PIS
Payment initiation via providers
Initiate account-to-account payments from the shopper's bank account through a licensed payment initiation provider. viaBanking does not settle payments and does not hold customer funds; the licensed provider and the shopper's bank move the payment on the underlying bank rails.
- Ops
Sandbox, webhooks, monitoring
A secure sandbox behaves like the live open banking API. Signed webhooks, versioned endpoints and provider-level status metadata let a business route around a degraded bank connection and stay on top of every payment lifecycle event.
We orchestrate the connection; we do not replace your provider or your bank relationships, and we do not hold customer funds. The licensed provider and the shopper's own bank remain in control of every regulated action.
04 · Reliability & coverage
Reliability and coverage
Reliability of an open banking layer is a coverage question and a routing question. Coverage is built up market by market: each supported bank is reached through one or more licensed open banking providers, and viaBanking maintains that mapping so a business does not have to. Precise coverage counts per market are shared with workspace users and kept current inside the dashboard.
Routing is where the open banking layer earns its keep. Every open banking API call is routed through the healthiest available open banking provider that reaches the target bank; every provider status change is reflected in the layer's status feed within seconds, so a business can pause a bank flow or retry through an alternative provider without a manual firefight. Expanding to a new market is a configuration change, not a new bank connector, with the same open banking API, the same bank data model and the same secure payment consent flow.
When a business goes live, use of the open banking layer scales with the business. Use one open banking API in the shopper checkout, use another route in the financial back office and use the same account contract in a mobile app; each secure use of the layer reads the same account data model, drives every financial reconciliation off the same feed and initiates every payment against every shopper's bank the same way. That consistency is what makes the financial view of a business feel like one financial system, not many bank connectors stitched together.
05 · Security & consent
Security, consent and compliance
Open banking is regulated. PSD2 in the European Union, its national transpositions and the emerging PSD3 framework set the rules around bank account access, payment initiation and strong customer authentication. viaBanking is designed to fit inside that framework: the open banking layer orchestrates licensed providers rather than replacing them, and every regulated open banking action stays with the licensed provider and the shopper's bank.
The shopper always grants consent to the licensed open banking provider that will access the bank account. Banking credentials never pass through viaBanking; strong customer authentication happens on the shopper's own bank, using the bank login and second factor the shopper already trusts. Bank data is encrypted in transit and at rest inside a secure European environment, and access to production keys is restricted per workspace. viaBanking is a software provider; regulated open banking services are delivered by licensed partner institutions.
06 · FAQ
Frequently asked questions
-
Is viaBanking a bank, a BaaS platform or an open banking provider?
No. viaBanking is an integration and orchestration layer for open banking. The regulated open banking actions, such as bank account access, payment initiation and strong customer authentication, are performed by the licensed provider and the shopper's own bank, not by viaBanking. Specific regulatory statements per market are confirmed with legal review.
-
Do you hold customer funds or move money?
No. Funds stay with the licensed provider and the shopper's bank. The open banking layer initiates and routes API calls; it does not settle payments and it does not hold or move any account balance on behalf of a business or a shopper.
-
What does the layer give me through one open banking API?
Both bank account data and payment initiation, across every pre-integrated open banking provider. One open banking API, one bank data model and one secure consent flow cover both, so your business does not integrate with each provider or each bank separately.
-
How does consent work and do you store banking credentials?
Consent is granted by the shopper to the licensed provider. Strong customer authentication happens on the shopper's own bank domain, using the bank login and second factor the shopper already uses. viaBanking never sees or stores banking credentials, only the tokens the provider returns after the shopper authorises the bank connection.
-
Do you offer a sandbox and how does go-live work?
Yes. A secure sandbox behaves like the live open banking API and is free per workspace. Going live is a key swap, not a fresh open banking integration; adding a new bank or a new provider later is a configuration change on our side, not another business integration on yours.
One layer · Many providers
One orchestration layer for open banking across Europe.
Use one open banking API to reach every supported bank, safely and consistently. Read the docs, or schedule a demo to walk your business team through a live routing example.
viaBanking is a software provider; regulated open banking services are delivered by licensed partner institutions.