Italy · Regional page
Open banking Italy: one API for Italian banks and payments
Italy has more banking institutions than almost any comparable European market, and each of them operates its own access interface. That single fact decides how a payment route here has to be built. viaBanking puts one integration in front of the whole list, licensed providers start each payment on the payer's consent, and we confirm in read-only mode that the amount reached the C2B account your business holds.
- OneIntegration in front of the whole Italian bank list
- Read-onlyConfirmation of the credit on your own C2B account
- LicensedPartner providers perform the payment initiation
- Nothing heldviaBanking never holds or moves your funds
The problem
Why the bank count changes the architecture
- 01
The number of institutions is the whole problem
Italy has an unusually long list of banking institutions for the size of its economy: large national groups, regional banks, cooperative banks and mutual banks, each operating its own open access interface. A company trying to reach its customers bank by bank in Italy is not planning a project, it is committing to a programme with no end date.
- 02
Interface maturity is spread across a wide range
Some banks in Italy run open banking interfaces that behave predictably under load. Others answer slowly, version their API endpoints on their own calendar or describe the same payment outcome in language nobody else uses. The spread is wider here than in markets with fewer institutions, and open banking payments feel the difference.
- 03
Customers are not concentrated where you expect
Coverage of the largest groups sounds like most of the market, and for many Italian businesses it is not. Regional and cooperative banks hold long standing relationships with exactly the customers a B2B seller cares about, and those relationships do not move.
- 04
Direct integration cost grows with the bank list
Every bank added means another mapping to write, another support path to document and another endpoint change to absorb later. In a market with this many institutions, that cost does not level off. It compounds.
The platform
One contract in front of a long list
One integration in front of the list
Your systems call a single open banking API endpoint. viaBanking works out which licensed provider reaches the payer's bank in Italy, translates the request and maps the answer into one payment model. The size of the bank list stops being your company's problem.
Coverage grows without your releases
When a licensed provider adds an Italian institution, it appears in the bank selection your customers see. Nothing ships on your side, no new mapping enters your codebase and the open banking API surface does not move.
Uneven interfaces absorbed here
Slow answers, renamed fields and API endpoint changes are handled inside the connectivity layer. Your code sees the same normalised status whichever institution answered and however it phrased the outcome.
The credit confirmed on your account
A licensed AIS partner reads your own C2B account in read-only mode and raises one event per payment when the expected amount is credited. That event is what your order logic should depend on.
The connectivity layer that carries this is described on the bank connectivity page.
Use cases
Where Italian businesses put this to work
B2B invoicing and wholesale
Companies in Italy settle a great deal by transfer already. Open banking payments carry the invoice reference through to the credit event, so accounts receivable matches it without a person opening a banking screen.
Ecommerce with larger baskets
Furniture, appliances, machinery parts and travel, where the amount sits above what a customer is comfortable committing to a card in a single transaction. Open banking payments remove that ceiling from the conversation.
Marketplaces and platforms
Buyers arrive from many different Italian banks and every incoming payment lands in the same model with its reference intact, which keeps the platform ledger from growing a per bank exception list. Cross border marketplaces get the same behaviour in Italy as in every other market on the API.
Account funding for financial products
Trading, savings and insurance platforms use open banking payments to fund customer balances, and the balance appears only once the money is genuinely on the company account.
Professional services and deposits
Deposits on work with a long delivery cycle, where the business wants the funds confirmed before the schedule is committed and the client wants to pay from their usual bank. Open banking payments make that deposit traceable to an invoice.
Subscription and membership renewals
Annual renewals and upgrades handled as open banking payments while cards keep carrying the smaller recurring charges, with both sets of payments reporting into one payment model.
Market structure
The shape of the Italian banking landscape
Three tiers of institution, each operating its own interface and each maintaining it on its own terms. The grouping below describes the structure of the market and is not a coverage claim about any specific Italian bank.
- National groups
A handful of institutions, most of the volume
The large Italian banking groups operate interfaces that behave predictably and are versioned with reasonable notice. A company reaching only these covers a lot of consumer volume and misses a great deal of business volume.
- Regional banks
Dozens of institutions, uneven interfaces
Regional banks vary widely in how their access interface performs under load and in how they name a payment outcome. This tier is where a routing layer earns its cost, because each of these connections would otherwise be a separate piece of maintenance.
- Cooperative and mutual banks
The long tail, and the loyal customers
Cooperative and mutual institutions hold long standing relationships with exactly the small businesses a B2B seller invoices. Coverage here differs most between licensed providers, which is why we check a real customer list rather than quote a market figure.
- 1Integration your engineers build, whatever the bank count
- 1Payment model, however many institutions answer
- 0Per bank mappings living in your codebase
Definition
What holds the Italian arrangement together
The framework is described in full on the PSD2 open banking page.
Banks operate the access interface
European rules require banks in Italy to run a dedicated open interface that a licensed institution may use on a customer's instruction. That obligation applies to the large national groups and to the smallest cooperative bank alike, which is why open banking payments in Italy are possible at all despite the number of institutions. Without that rule, open banking here would be a set of private deals rather than a market.
The payer authorises inside their bank
An Italian payer selects their bank, authenticates there and approves the amount and the beneficiary. That approval is the user's payment consent. No banking credential passes through the merchant or through viaBanking at any point.
The licensed provider performs the initiation
Payment initiation is a regulated activity carried out by a licensed PIS provider, and the funds move on bank rails. viaBanking supplies the API, the routing and the payment data model, and performs no regulated activity of its own.
Local vocabulary you will meet
Italian teams search and write about this category in their own language, and the terms below come up in every project conversation. They are listed for orientation, not as product names.
| In Italian | What it refers to here |
|---|---|
| Open banking Italia | The term Italian teams use when searching for this category in their own language |
| Banca | Bank. The institution holding the payer's account and performing the authentication |
| Pagamento | Payment. The instruction the licensed provider starts on the payer's consent |
| Bonifico | Bank transfer. The mechanism the funds travel on once the payment is authorised |
| Conto | Account. On this route the relevant account is your own C2B account |
| Banca d'Italia | The national central bank, named here only as market context and not as a partner |
Integration
Create, select, approve, normalise, confirm
- 1
Create
One call carrying an amount, a currency, a reference and the destination C2B account.
- 2
Select
The payer picks their Italian bank from the institutions the routed provider reaches.
- 3
Approve
Consent and authentication happen inside that bank, on its own screens.
- 4
Normalise
Whatever the bank called the outcome, your systems receive one status vocabulary.
- 5
Confirm
A read-only check raises the credit event when the expected amount reaches your account.
Capabilities
Seven rows, including what is out of scope
| Capability | What it covers | Performed by |
|---|---|---|
| Bank reach | Italian institutions reachable through the routed licensed providers | Maintained by viaBanking |
| Payment initiation | Started on the user's payment consent | Licensed PIS provider |
| Authentication | Strong customer authentication at the payer's bank | The payer's bank |
| Funds movement | On European bank rails, into your C2B account | Banks and EMIs |
| Status normalisation | One vocabulary across every Italian route | viaBanking |
| Account credit confirmation | Read-only check on your own account | Licensed AIS provider, surfaced by viaBanking |
| Payer account data | Balances, statements and history are not part of this product | Not offered |
Security and consent
The permission this route runs on
The bank keeps what matters
Authentication happens inside the Italian bank the payer selected. No password, code or device confirmation reaches viaBanking, and none is stored by the merchant either.
One consent per payment
It names an amount, a beneficiary account and a reference, and it ends when that payment resolves. It gives nobody a continuing right to look at the payer's account.
Read-only, on your own account
The account checked is the C2B account your business holds with a bank or EMI. The check recognises an expected account credit. It cannot manage the account and cannot send money out of it.
FAQ
Six questions about the Italian market
-
How does open banking work in Italy?
Your system creates one payment, the payer selects their Italian bank and approves inside it, a licensed provider performs the initiation, and viaBanking confirms in read-only mode that the amount reached your own C2B account. The number of banks in the market is handled by the routing layer rather than by your integration.
-
How many Italian banks can a customer pay from?
Reach comes from the licensed providers behind the route. The large national groups are broadly covered and the regional, cooperative and mutual institutions vary considerably by provider. We map your customers' actual banks against live coverage before you build, and we do not publish an Italian coverage figure the product has not confirmed.
-
Why not integrate with Italian banks directly?
Because of the count. Reaching one bank is a project, and in a market with this many institutions the work never finishes. A routed open banking API puts one contract and one payment model in front of the whole list, and the regulated steps are identical either way: a licensed provider initiates and the bank moves the funds. Companies that have tried the direct route in Italy usually come to us after the third or fourth integration.
-
Who performs the regulated part of the flow?
Licensed institutions. A PIS provider performs the payment initiation, an AIS provider performs the read-only check on your own account, and the money moves between banks and EMIs. viaBanking is a software company, holds no licence, executes no payments and moves no funds.
-
How is the payment confirmed as received?
Through a read-only check on your own C2B account that raises one event when the expected amount is credited. It is a fact about your business account. It is not a look at the payer's account, their balances or their transaction history, and no account ownership check is performed.
-
How long does an Italian rollout take?
Sandbox on the first day and typically one to three weeks of engineering, most of it spent on payment statuses. Opening the C2B account with the receiving bank or EMI is arranged directly between your company and that institution, and it usually sets the date. Neighbouring markets are covered on the France page, and the regional overview on the Europe page.
Send us the Italian banks your customers actually use
Regional and cooperative institutions are where coverage questions get interesting, so the useful conversation starts with your own list. We come back with what the licensed providers behind our routes reach today and with what the C2B account arrangement would be for your company. If open banking payments are a poor fit for what you sell in Italy, we will say so rather than sell you an integration that competes with something already working.
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 execute bank payments and does not move funds.