Bank connectivity
Bank connectivity for open banking
Open banking payments start with a connection to a bank. Building that per bank, then keeping it alive as each one changes, is the work teams underestimate. viaBanking is the bank connectivity layer: one platform, one contract, and access to every supported bank through a single open banking API.
viaBanking provides connectivity, not banking. Open banking services are conducted by licensed providers, the banks move the money, and the platform routes and confirms.
Definition
What bank connectivity means
A plain definition, because the term gets used loosely. The wider model is set out on the open banking aggregator page.
- Layer
One layer of access to banks
The layer that gives a platform access to banks under one contract for every payment, instead of a separate integration for each bank you use.
- Boundary
Connectivity, not banking
The layer carries payment requests and returns payment status data. Banking stays with the banks, and open banking services run on a licensed provider's authorisation.
- Upkeep
Maintained, not just built
Banks change endpoints and field names on their own schedule. Connectivity is the ongoing work of absorbing that, which is why teams buy it rather than build it.
The case
One connection instead of many
The commercial case, in the order a buyer meets it. The endpoint view sits on open banking for banks.
- Build
One integration to set up
Set up one open banking API and one data model. No per-bank branch, no second set of credentials, no mapping file per bank.
- Operate
One platform to run
One place to watch open banking payments, read payment status data and raise an issue. Support does not scale with the number of banks you use.
- Contract
One agreement to sign
Coverage arrives through the banking platform you already use, not a stack of agreements you negotiate and renew separately.
In the flow
Connectivity in the payment flow
Where the layer sits when a customer actually pays. What the initiating licence covers is on the PIS provider page.
- 01
The customer picks a bank
At checkout the customer chooses to pay from their own bank. Connectivity supplies the bank list your market supports, so the customer only sees payment options they can use today.
- 02
A licensed provider initiates
Payment initiation for those payments is conducted by a licensed PIS provider reaching that bank. The customer authenticates in their own banking app and the bank moves the payment.
- 03
The credit is confirmed
The platform then confirms, read-only, that the payment landed on your C2B account. Your services use that payment signal to release an order, not the initiation callback.
Coverage
Coverage kept live
Coverage is a service, not a list published once. Open banking payments only work where the bank list is current.
- 2,500+Banks and EMIs reachable
- 31EU markets covered
- 1Contract, whatever the bank list does
-
A new bank is our work
When a licensed provider adds a bank, it appears on the open banking integration your platform already uses. No release on your side, and no new data mapping.
-
Changes are absorbed here
When a bank moves an endpoint or renames a field, the connectivity layer takes the change, and the one API your customer-facing services use stays still.
FAQ
Three answers before the call
-
Does viaBanking hold a licence or move funds?
No. viaBanking is a software platform and holds no AIS or PIS licence. Open banking services are conducted by licensed providers, the banks move the money, and the C2B account belongs to the issuer you use.
-
What does the connectivity actually access?
Access to banks through licensed providers for payment initiation, plus read-only confirmation that payments reached the C2B account you use. It is not access to a customer's bank statement, balance or account data.
-
Do we still need our own agreements?
Yes. The C2B account is opened by your business with a licensed EMI or bank, and payment initiation uses a provider's authorisation, contracted directly or through the network you connect to.
One connectivity layer, every supported bank
Tell us which markets and banks matter first and we map them against the open banking payments coverage you would use. Larger rollouts start on open banking for enterprise.
viaBanking is a software and technology provider. Regulated payment initiation and account information services are delivered by licensed partner institutions. viaBanking does not hold an AIS or PIS licence, does not provide banking services, does not execute bank payments and does not hold or move funds.