Direct to each bank
- 6Connections your engineers build and own permanently
- 6Payment data mappings living in your codebase
- 6Bank release calendars your team has to track
- 0Confirmed account credit signals, unless you build one yourself
Spain · Regional page
Open banking Spain: one connection to Spanish banks
The interesting question in Spain is not whether open banking payments work. It is how many connections your engineering team wants to own for the rest of the product's life. One connection to viaBanking reaches the Spanish banks through licensed providers, who initiate each payment on the customer's approval, and we confirm in read-only mode that the funds were credited to your own C2B account.
The cost of going direct
What a per bank integration really bills you
The build estimate is the small number. The permanent number is what it costs to keep every one of those connections alive while the banks on the other end keep changing.
- 01
A direct connection is a permanent commitment
Wiring your product into one Spanish bank is a few weeks of work and then a liability that never closes. Somebody on your team owns that connection for as long as it exists, and that ownership does not appear anywhere in the original estimate.
- 02
Every bank models the same payment differently
Two Spanish banks will accept the same transfer and describe it in incompatible language: different consent objects, different reference limits, different names for the moment a payment becomes final. Code written against the first bank teaches your team very little about the second.
- 03
Failures land on you at the worst hour
When a direct connection breaks, the alert reaches your engineers and the customer reaches your support queue. Neither of them can do much except wait, because the fix lives inside somebody else's release cycle.
- 04
The bank list is never finished
Spain has a long tail of banks and credit cooperatives beyond the large groups. Direct work covers the first few and then stalls, and the customers on the uncovered banks quietly go back to paying another way.
The platform
Move the maintenance, keep the reach
One connection, many banks
Your product holds a single open banking connection to viaBanking. Behind it, licensed providers reach the Spanish banks, and we decide which route carries a given payment. Adding new banks does not add new connections on your side.
The mapping work moves off your team
Consent objects, reference formats and status names are translated inside our layer. Your engineers see one payment model and never write a Spanish bank specific branch, whatever new work the banks publish.
Route selection happens without a release
If a route degrades, we reroute the open banking traffic to another supported provider. Nothing ships on your side and your payment logic is unchanged, because the change is on the connection we own rather than the one you built.
Confirmation, not assumption
A licensed AIS partner reads your own C2B account in read-only mode and we raise one event when the expected amount is credited. That is the fact your systems should act on.
Before and after
The same reach, counted two ways
Open banking reach can be built two ways, and the difference is entirely on your side of the boundary. The banks and the licensed providers are identical in both columns. What changes is how much of the arrangement your own team has to own for the life of the product, counted here for a company reaching six Spanish banks.
Through one connection
- 1Connection your engineers build and own
- 1Normalised payment model, whatever the bank count
- 0Bank release calendars reaching your side of the boundary
- 1Confirmed credit event per payment, on your own account
Definition
Who does what when a Spanish customer pays
The underlying rules are set out on the PSD2 open banking page.
The bank runs the interface
Spanish banks operate a regulated open access interface that a licensed institution may call on a customer's instruction. It is separate from the online banking screens the customer uses, and it exists because European regulation obliges the bank to provide it. Open banking payments in Spain all travel through that channel.
The customer approves in their bank
A payer in Spain selects their bank, is taken into that bank's own environment and approves the amount and the beneficiary. Authentication happens there, and the user's payment consent is given to the bank rather than to your website. New payers need no account with anyone except their existing bank.
The licence sits with the provider
Payment initiation is performed by a licensed PIS provider. The bank moves the funds. viaBanking supplies the open banking connection, the routing and the payment data model, and performs no regulated payment activity at any point.
- OneConnection your engineers build and maintain in Spain
- ManySpanish banks reachable behind it through licensed providers
- Read-onlyConfirmation of the credit on your own C2B account
- NoneBanking credentials handled by viaBanking at any stage
Use cases
Six Spanish situations, with the detail that matters
Ecommerce with large baskets
A Spanish retailer selling appliances at four figure prices watches card declines cluster at the top of the basket range. A bank payment route removes the issuer limit from the conversation, and the confirmed account credit tells the warehouse when to release the order.
B2B collections
Invoices in Spain are frequently settled by transfer typed by hand. Sending a payment link instead means the beneficiary account, the amount and the reference arrive intact, and the accounts receivable ledger matches them without anybody reading a statement.
Trading and account funding
A brokerage funding customer accounts in Spain needs the money to be real before the balance appears. Waiting for the account credit confirmation rather than for the provider acknowledgement is the difference between a controlled process and a risk carried on the firm's own book.
Marketplaces and platforms
Buyers in Spain pay through one route regardless of which bank they use, so the platform's ledger receives one payment shape and one reference structure for every incoming transfer.
Utilities, insurance and instalments
Large periodic amounts where a card is a poor fit and a manual transfer is a reconciliation problem. The payment link carries the policy or contract reference through to the credit event.
Companies already running several markets
Spain becomes one more configuration on a connection that already carries other countries, with no new integration and no new payment model to learn.
Capabilities
Direct connections against one routed connection
| Dimension | Direct to each bank | Through one connection |
|---|---|---|
| Connections your team maintains | One per Spanish bank | One, to viaBanking |
| Payment model in your code | One per bank, mapped by hand | One normalised model |
| Adding a Spanish bank | A new project and a new release | A configuration change on our side |
| Bank endpoint changes | Your engineers, on the bank's calendar | Absorbed in the connectivity layer |
| Failure triage | Per bank, by your team | Per route, surfaced by the platform |
| Who initiates the payment | A licensed provider | A licensed provider |
| Who confirms the account credit | Usually nobody, so finance checks by hand | Read-only check on your C2B account |
The comparison covers engineering only. Choosing a routed connection does not change who is licensed for what: a licensed provider initiates on both paths, and the bank authenticates and moves the money on both paths. Open banking payments in Spain are regulated the same way whichever of these two shapes your architecture takes, so this is an engineering decision rather than a regulatory one.
Integration
Five stages, and the edge case in each one
The happy path takes an afternoon. What follows is the part that decides whether open banking payments behave well in production, and it is where most Spanish rollouts spend their engineering time.
- 1
Create the payment
One call carrying an amount, a currency, a reference and your C2B account.
Edge case. If the reference exceeds what a bank accepts, the layer normalises it before the request leaves.
- 2
The payer picks a bank
Spanish institutions reachable on the routed provider are presented for selection.
Edge case. A bank that is temporarily degraded is marked rather than silently failing mid flow.
- 3
Consent and authentication
The payer approves inside their own bank and authenticates there.
Edge case. An abandoned approval returns a defined status rather than an open ended pending state.
- 4
Provider status
The licensed provider reports what the bank returned, normalised into one vocabulary.
Edge case. Ambiguous bank answers are surfaced as ambiguous, never upgraded into success.
- 5
Account credit confirmation
The read-only check raises an event when the expected amount reaches your account.
Edge case. A payment that arrives after the session closed still produces the same event.
Payload detail sits on the open banking for developers page.
Security and consent
The narrow permission this route runs on
Credentials never leave the bank
Your customer authenticates on their Spanish bank's own pages. Nothing they enter passes through viaBanking, and your systems never hold a banking credential.
The consent is narrow by design
It names one amount, one beneficiary account and one reference, and it ends when that payment resolves. It grants no continuing access to the payer's account.
Read-only means read-only
The account we observe through a licensed partner is the C2B account your company holds. We can recognise an expected account credit on it. We cannot manage it, cannot send money from it and hold no funds at any point.
FAQ
Six questions before a Spanish build
-
What does open banking change for a Spanish business?
It gives you a payment route where the customer approves a transfer inside their own bank and your system receives a confirmed credit on your own account. In engineering terms it replaces a set of direct bank relationships with one connection, and in finance terms it replaces manual matching with a payment reference that survives the journey.
-
How is this different from integrating with a bank directly?
A direct integration reaches one bank and makes your team responsible for it permanently. This is one connection in front of many Spanish banks, with the mapping, the routing and the failure handling maintained on our side. The regulated step is identical on both paths: a licensed provider initiates and the bank moves the funds.
-
Which Spanish banks can customers pay from?
The major banking groups are broadly reachable through the licensed providers behind the route, and coverage of smaller banks and cooperatives varies. We check your customers' actual institutions against live coverage before you build rather than quoting a national figure.
-
Who is responsible for the regulated part?
The licensed PIS provider performing the initiation, and the bank or EMI holding the accounts. viaBanking is a software company. We hold no AIS or PIS licence, we do not execute payments and we do not hold funds at any stage of the flow.
-
What does going live actually involve?
Sandbox keys on day one, then the engineering work of handling five payment statuses and one credit event. Most teams need one to two weeks. In parallel your company opens the C2B account with a licensed bank or EMI, directly with that institution, and that onboarding usually sets the date.
-
Which businesses should not bother with this?
Companies whose Spanish payments are small, frequent and already working well on cards. Open banking payments earn their integration when amounts are large, when references matter, or when the business is already paying for several direct connections in Spain. Neighbouring markets are covered on the Portugal page and the wider view on the Europe page.
Count the connections you would rather not own
Tell us which Spanish banks matter and what you have already built. We come back with live coverage from the licensed providers behind the route, and with an honest view of whether one connection is worth the migration in your case. Companies running open banking payments in other markets usually find that Spain needs configuration rather than new work.
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.