Bank API
The viaBanking bank API is the connectivity catalogue for financial services teams that need one integration to open banking. Account information via AIS, payment initiation via PIS, and account verification, routed through licensed provider partners on one open contract.
The full picture
You already know what a bank API is. Below is what actually matters when picking one: the audience it's built for, the differentiators that make viaBanking the shortest path, and the map of everything included in the catalogue.
Regulated financial services businesses: banks, EMIs, licensed lenders, marketplaces, insurers and payment providers that want one software layer to reach open banking, on one contract, without a per-bank integration.
The typical bank API provider sells one service and stops. viaBanking ships the full catalogue on one contract, with first-class customer support and a growing service surface as new bank rails come online.
The full catalogue sits just below this section. Each service links to a product page for the deep detail; the sibling Banking API, Open banking API and Payment initiation services pages set the wider context.
Service catalogue
Every service below is a bank API endpoint. Financial services teams pick the services they need, pay per service and scale the customer support service without a rewrite. The catalogue grows as new bank rails come online, on the same open contract.
Access consented account data via licensed AIS providers, orchestrated on one contract. Financial services teams read balances and metadata through one normalised data model; the AIS call itself is performed by the licensed provider.
Open product pageRoute payment initiation to a licensed PIS provider. viaBanking handles the API and provider routing; the payment initiation itself is performed by the licensed PIS partner, not by viaBanking.
Open product pageBank account ownership, IBAN and name-match verification exposed as a first-class API service for C2B checks.
Open product pageBank-to-bank transfer initiation routed to a licensed PIS provider that executes the transfer. viaBanking does not move funds; the licensed partner does. Normalised status surfaces back through one API.
Balance reads via licensed AIS providers, on the same connectivity contract. Quota-controlled per service tier.
Statement data retrieval via licensed AIS providers, within bank-permitted windows. One financial data model across the connectivity catalogue.
Signed webhook events as a service. Every state change surfaces on the webhook service, regardless of which licensed provider handled the call.
A free sandbox service that simulates provider responses for every route, out of the box.
A customer support service for financial services teams building on the connectivity layer. Included on every service tier, out of the box.
Adding regularly
The catalogue grows every quarter. If the banking service your product depends on isn't listed yet, tell us what you need and we'll scope it into the roadmap or spin it up on the same open contract.
Who uses it
Regulated banks, EMIs, lenders and marketplaces run their banking services on the bank API. One contract, one service tier, one customer support desk. Not a system integrator project, not a provider stack per market.
The business gets one financial API and one system to build on; every product is a service call.
The customer journey stays familiar: pick a bank, approve the payment on their own bank, and the money moves out of their account through the transfer service. No customer credentials leave the bank, not one.
Every customer touchpoint is a service: consent, payment and receipt.
Rollout
Pick from the catalogue, test in sandbox, go live. The same three steps whether you ship one service or the whole stack, per market and per bank.
Pick the services your product actually needs from the catalogue above. Start with one; add other products as the roadmap opens. No procurement email per service.
Free sandbox, code samples, the API reference and a customer support service on the same day. Wire user's payment consent, SCA and webhooks against real bank fixtures.
Promote your code, route to live banks, monitor from one dashboard. Add a new market by switching more banks on, not by rebuilding. See what production looks like in the developer docs.
Team & careers
Careers at viaBanking centre on shipping banking services, not slides. Open careers span integration engineering, payments, developer experience and customer support. Every career gets you close to real banking rails, real payment flows and real financial data, out in production.
We refresh open careers as new roles open. If a banking-services career is what you're looking for, browse the careers page or read the about page.
FAQ
The bank API is a connectivity catalogue: account information via licensed AIS providers, payment initiation via licensed PIS providers, account verification, transfer initiation routed to licensed partners, webhooks, sandbox and customer support. viaBanking is the software layer; the regulated banking and payment services are performed by the licensed partner institutions.
The bank API is the connectivity catalogue: every open banking integration as an API. The Banking API is the connectivity primer. The Open banking API is the platform overview across products. All three sit on the same viaBanking software contract, with regulated services performed by licensed provider partners.
Any regulated financial services business: banks, EMIs, lenders, marketplaces, insurers and payment providers. The bank API service serves both consumer and business products across the supported markets.
Yes. Customer support is a first-class bank API service, not a paid add-on. Every service tier includes a customer support channel, sandbox support and integration support out of the box.
Open careers are posted on the careers page and refreshed as new roles open. Careers at viaBanking span integration engineering, payments infrastructure, customer support and developer experience.
Purpose-built landings
The bank API catalogue above is the full picture. Two sibling pages pick out a shorter path for the two audiences that ask first: a fintech team scoping a workflow, and a developer wiring the first call.
A company information service for any fintech workflow into Italy: real company info, real detail and real data on one API contract, on top of licensed providers.
Open the fintech page For developersOne bank API a developer can use to hit many licensed open banking APIs behind one contract: sandbox, reference and a quickstart path from key to first live call.
Open the developer pageReady to build
Sandbox is free. Use one banking service or the full catalogue. See what pricing looks like on the pricing page.
