Portugal · Regional page
Open banking Portugal: one API for Portuguese banks and payments
Portugal is a market most payment roadmaps postpone, because a country project for Portugal alone rarely pays for itself. On this route Portugal is not a project. It is one more market on an integration your company already has, with licensed providers initiating each payment inside the payer's Portuguese bank and a read-only confirmation that the transfer reached your own C2B account.
- OneIntegration covering Portugal and the rest of the European map
- Read-onlyConfirmation of the transfer on your own C2B account
- LicensedPartner providers hold the payment initiation permission
- ZeroBanking credentials passing through viaBanking
Definition
The three parties behind a Portuguese bank payment
- 01
The Portuguese bank operates the channel
Banks in Portugal run a regulated open access interface that a licensed provider may call when a customer instructs it. The bank API accepts a payment request and returns payment status. It sits apart from the online banking screens a Portuguese customer logs into every day, and it is what makes open banking in Portugal a regulated arrangement rather than a private agreement between a bank and a vendor.
- 02
The payer approves inside their bank
A payer in Portugal chooses their bank, lands in that bank's own environment, sees the beneficiary and the amount, and approves the transfer. That approval is the user's payment consent, and the authentication happens on the bank's side without anything reaching your servers.
- 03
Licensed institutions carry the permission
The initiation is performed by a licensed PIS provider. The bank authenticates and sends the funds. viaBanking contributes the open banking API layer, the routing and the payment data model, which is software rather than a regulated payment activity. The same division holds on every open banking route across Europe, and Portugal is no exception to it.
The regulation behind the arrangement is explained on the PSD2 open banking page.
Capabilities
In scope and out of scope, stated plainly
A capability matrix is more useful than a feature list, because what a platform declines to do says more about it than what it advertises. Open banking solutions are frequently sold with the account data half implied and never delivered, so this table states both halves.
| Capability | In scope | Detail |
|---|---|---|
| One payment endpoint | Yes | Same call in Portugal as in every other market on the platform |
| Portuguese bank selection | Yes | The institutions the routed provider reaches, presented to the payer |
| Normalised status | Yes | One status vocabulary across providers and countries |
| Confirmed credit on your account | Yes | Read-only, through a licensed AIS partner, on your C2B account |
| Payer account data | No | Balances, statements and transaction history are outside this product |
| Account ownership checks | No | viaBanking neither performs nor sells any account verification |
| Funds held by viaBanking | No | Money moves between the payer's bank and your C2B account only |
The problem
Why Portugal keeps slipping down the roadmap
Portugal is rarely anybody's first integration
A payments roadmap gets written around the largest markets in Europe, and Portugal sits below the line where a dedicated country project can be justified. The volume is real and it is not large enough to fund its own build, so it waits behind the open banking work already queued for bigger markets.
A single country contract is expensive per euro collected
Signing an open banking provider for Portugal alone means legal review, commercial negotiation, an API integration and a support arrangement, all amortised over one market. The same effort spread across a European footprint looks completely different on a spreadsheet, which is why most Portugal projects only happen as part of a Europe wide one.
Portuguese customers pay by transfer anyway
Bank transfers are a normal way to settle an invoice or a large purchase in Portugal, and much of that volume moves manually today. The money already travels on bank rails without any payment reference discipline attached to it.
Waiting has a cost that nobody measures
While Portugal stays out of scope, the finance team keeps matching incoming transfers by hand and the sales team keeps quoting bank details in email. That work is invisible in the payment budget and very visible in the month end close.
The platform
Portugal as a configuration line, not a country project
- 1
Portugal arrives with everything else
Switching Portugal on is a configuration change on a route your company already uses. There is no separate Portuguese contract to negotiate, no second open banking API to learn and no additional reconciliation path to design. Companies that already run our European solutions add Portugal in an afternoon.
- 2
One payment model, one reconciliation
A transfer approved in a Portuguese bank comes back in the same shape as one approved anywhere else in Europe on the platform. Your finance systems do not learn a country specific format, and your payment reporting stays one report.
- 3
The account credit confirmed, not assumed
A licensed partner checks your own C2B account in read-only mode and we raise one event per payment when the expected amount lands. Order release can hang off that event rather than off a provider acknowledgement.
- 4
Coverage maintained without your releases
As licensed providers extend their Portuguese bank lists, those banks appear in the selection your payers see. Nothing ships on your side for that to happen.
The full catalogue of open banking solutions we operate across Europe is on the open banking solutions page, and the API surface behind these solutions is documented on the API reference. Nothing in this list requires a Portuguese payment licence on your side, because the licensed part of the open banking flow is not on your side at all.
Integration
Five stages of a Portuguese payment
- 1
One call creates the payment
Amount, currency, reference and your C2B account. No Portuguese bank identifiers in the payload.
- 2
The payer chooses their bank
From the Portuguese institutions reachable on the routed licensed provider.
- 3
Consent and authentication
Given and performed inside the payer's own bank, never on your pages or ours.
- 4
Status comes back normalised
The provider reports, we translate into one vocabulary and pass the meaning through unchanged.
- 5
The account credit is confirmed
A read-only check on your account raises the event your systems act on.
- 1API integration covering Portugal and the wider European map
- 2Signals per payment: provider status and confirmed credit
- 0Portugal specific fields in the payment payload
Iberian region
Portugal and Spain as a paired rollout
Almost every company that asks us about Portugal asks about Spain in the same message. The two markets are neighbours commercially as well as geographically, and the integration treats them as one decision.
The two markets are usually one decision
A company that starts selling into Portugal is normally selling into Spain within the same planning cycle, and often already is. Treating them as one rollout removes a second round of contracts, a second integration review and a second support arrangement. Payment solutions bought market by market end up costing more than the volume they collect.
One integration reaches both
The same open banking payment endpoint, the same payment model and the same confirmation logic cover Portuguese banks and Spanish banks. Adding Spain after Portugal is a configuration change, and the reverse is equally true. Payers in either market see only their own bank.
The markets still differ
Spain is larger, its bank list is longer and its own considerations are set out on the Spain page. Portugal is described here on its own terms, and nothing on this page tries to summarise the Spanish market for you.
Portugal and Spain share the integration. They do not share this page. Everything specific to the Spanish market lives on the open banking Spain page, and the pan European view is on the Europe page.
Use cases
Where Portuguese transfer volume already exists
Companies expanding into Iberia
Portugal switched on alongside Spain, with one open banking API integration serving both bank lists and one set of reconciliation rules covering every transfer that arrives. The same API then covers the rest of Europe when the roadmap gets there.
B2B invoicing to Portuguese clients
A payment link opens the client's own bank with the amount and the reference already filled in, so the reference survives the journey and your ledger matches it without a person reading a bank statement.
Travel and hospitality bookings
Group bookings and long stays where the amount is uncomfortable on a card. The payer approves a transfer in their own bank and your system waits for the confirmed account credit before holding the reservation.
Funding accounts on financial platforms
Portuguese customers topping up a trading or savings product, where a credited amount rather than an accepted instruction is what should release the balance.
Education and professional fees
Course fees, certifications and professional services paid in one large transfer rather than split across several card payments to stay inside issuer limits. Open banking solutions suit this pattern well, because the payer is paying once and paying deliberately.
Recurring wholesale orders
Distributors and wholesalers repeating an order every month, where each payment is large and the buyer prefers paying from a business bank account rather than a company card. Open banking solutions here mostly replace manual transfers, not card payments.
Security and consent
What is approved, and what we can see afterwards
Nothing sensitive passes through us
The payer authenticates on their Portuguese bank's own pages. No credential, code or device confirmation reaches viaBanking, and none is stored on your side either.
One consent per payment
The user's payment consent names an amount, a beneficiary and a reference, and it ends with the payment it authorised. It is not a permission to look at anything afterwards.
Our read-only view is your account
The only account viaBanking observes is the C2B account your company holds. The check confirms an expected account credit and gives no ability to manage the account or to send money out of it.
FAQ
Six questions about the Portuguese route
-
How does open banking work for a company selling in Portugal?
Your system creates one payment, the payer selects their Portuguese bank and approves the transfer inside it, a licensed provider performs the initiation, and viaBanking confirms in read-only mode that the amount reached your own C2B account. Nothing in that sequence requires a Portugal specific integration on your side.
-
Do we need a separate setup for Spain?
No. Spain runs on the same integration and the same payment model, and switching it on is a configuration change rather than a project. The Spanish market has its own characteristics, which are covered on the Spain page rather than summarised here.
-
Which Portuguese banks are reachable?
Reach comes from the licensed providers behind the route and covers the main Portuguese banking groups, with a longer tail that varies by provider. We check your customers' actual banks against live coverage before you build, and we do not publish a Portugal coverage figure the product has not confirmed.
-
Which party in the flow holds a licence?
The PIS provider performing the initiation and the bank or EMI holding the accounts. viaBanking is a software and technology company: we route requests, normalise payment data and confirm the account credit. We hold no AIS or PIS licence in Portugal or elsewhere.
-
How is the arrival of the money confirmed?
Through a licensed AIS partner reading your own C2B account in read-only mode. When the expected amount is credited, we raise one event. It is a check on your business account and never a check on the payer's account, their balances or their transaction history.
-
How long does a Portuguese rollout take?
Sandbox on day one, and typically one to two weeks of engineering to wire the payment statuses and the credit event into your order logic. Opening the C2B account with the receiving bank or EMI is direct between your company and that institution, and it usually sets the go live date. Companies that already run our open banking API in another European market often need nothing beyond a configuration change. The wider picture across Europe is on the open banking in Europe page.
Add Portugal without adding a project
Send us the Portuguese banks your customers use and the volume you expect. We come back with live coverage from the licensed providers behind the route, and with what the C2B account setup looks like for your company. If your Portuguese volume does not justify open banking yet, we will say so, and the payment solutions you already run will keep doing the job until it does. Most companies open Portugal and Spain in the same week and then keep the rest of Europe as a later configuration decision.
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.