Sweden · Regional page
Open banking Sweden: bank payments on one API
Sweden runs on digital payments by default, and the payer experience is the whole argument for open banking here. A customer approves the payment inside the banking app they already open several times a week, a licensed provider performs the initiation, and viaBanking confirms in read-only mode that the amount reached the C2B account your business holds.
Definition
The Swedish arrangement in three sentences each
- 01
The bank provides the channel
Swedish banks operate a regulated access interface that a licensed institution may call on a customer's instruction. It carries a payment request and returns payment status, and it exists because European rules oblige the bank to provide it rather than because a commercial deal was struck.
- 02
The payer approves in an app they already trust
A Swedish customer approves the payment inside their own banking app, seeing the amount, the beneficiary and the reference. Authentication happens there. In a market this comfortable with digital banking, that step reads as normal rather than as an interruption.
- 03
The regulated work belongs to licensed providers
Payment initiation is a regulated service performed by a licensed PIS provider, and the funds move on bank rails. The read-only account information service behind the account credit confirmation is delivered by a licensed AIS provider. viaBanking supplies the open banking API, the routing and the payment data model, holds no payment authorisation of its own, and sells no regulated services.
The platform
Three things this route is built to do
One API for Swedish bank payments
Your systems call one endpoint. viaBanking routes each payment to the licensed provider that reaches the customer's Swedish bank and returns a single payment model whichever provider answered.
The payer experience stays inside the bank
Nothing in the flow asks a Swedish customer to trust your checkout with banking details. They select a bank, approve in their own app and come back. That is the whole interaction from their side.
A confirmed account credit, not an acknowledgement
Through a licensed AIS partner in read-only mode, we confirm that the expected amount reached your own C2B account and raise one event per payment. Your business logic can act on the money rather than on a message about it.
- OneAPI for Swedish bank payments and the rest of Europe
- In appEvery approval happens inside the customer's own bank
- Read-onlyConfirmation of the credit on your own C2B account
- LicensedPartner providers deliver the regulated payment services
Capabilities
Six steps and their owners
| Step | What happens | Performed by |
|---|---|---|
| Create a payment | One call, no Swedish bank specific fields | Your systems |
| Route to a provider | Selection based on the customer's bank and route health | viaBanking |
| Initiate the payment | Performed on the user's payment consent | Licensed PIS provider |
| Authenticate the payer | Strong customer authentication in the banking app | The customer's bank |
| Normalise the status | One vocabulary across providers and European markets | viaBanking |
| Confirm the account credit | Read-only check on your own C2B account | Licensed AIS provider, surfaced by viaBanking |
Use cases
Where Swedish businesses use the route
Ecommerce with considered purchases
Bicycles, electronics, furniture and outdoor equipment, where a Swedish customer is comfortable approving open banking payments and the business would rather have the confirmed credit before dispatch.
B2B invoicing
An invoice sent as a payment link arrives in the payer's banking app with the amount and the reference already set, so the accounts receivable side matches the credit automatically.
Account funding
Savings, trading and insurance platforms where the customer balance should only appear once the money is genuinely on the company account.
Marketplaces and platforms
Every incoming payment arrives in the same shape with its reference intact, whichever Swedish bank the buyer used, which keeps the platform ledger simple.
Cross border Nordic sellers
A business selling into Sweden and its neighbours runs one integration, with each additional market a configuration rather than a project.
The problem
What happens when Sweden stops being enough
- 1
One market is never the end of the plan
A Swedish company that gets open banking payments working at home nearly always wants the same thing in Norway, Denmark, Finland or Germany next. Payment services bought for Sweden alone have to be replaced for each of those markets, and the second project is rarely cheaper than the first.
- 2
Every provider draws its own map
Coverage differs by licensed provider and the differences are sharpest at the borders. Services that reach Swedish banks well may reach very little in the market you plan to open next, and you find that out after the integration is written.
- 3
Reconciliation multiplies quietly
Each new set of payment services brings its own reporting format and its own status names. The finance team ends up maintaining a translation for every market instead of one payment model for the business, and open banking is supposed to remove that work rather than add to it.
- 1Integration, however many markets follow Sweden
- 1Payment model your finance systems ever learn
- 0New contracts needed to add the next market
Nordic context
Sweden as the way into the region
Sweden is usually the first Nordic market
Companies expanding into the region tend to start here, because the market is the largest of the group and the payment habits are the most digital in Europe. What is learned in Sweden about statuses, references and confirmation transfers directly to the markets next door, and the same open banking services carry over with it.
Norway sits outside the European Union
The neighbouring Norwegian market runs on its own arrangements, and the practical experience for a payer is close. The specifics, including what the difference in legal framework means for a business, are set out on the Norway page rather than summarised here.
One integration covers the region
Adding a second Nordic market on this platform is a configuration change on the open banking API you already use. The payment model does not change, the reconciliation logic does not change, and no second contract for payment services elsewhere in Europe is required.
Everything specific to the Norwegian market, including how a country outside the European Union changes the framing, is on the open banking Norway page.
Integration
Create, select, approve, status, confirm
- 1
Create
One call with an amount, a currency, a reference and your C2B account.
- 2
Select
The customer chooses their Swedish bank from the reachable list.
- 3
Approve
Consent and authentication happen inside that bank's own app.
- 4
Status
The licensed provider reports and viaBanking normalises the result.
- 5
Confirm
The read-only check raises the credit event when the money lands.
Security and consent
Where trust actually lives in this flow
Nothing sensitive leaves the bank
The customer's credentials and authentication factors exist only between them and their Swedish bank. viaBanking has no mechanism through which they could arrive.
The consent is single use
It names one amount, one beneficiary account and one reference, and it ends with the payment. It grants nobody continuing access to the customer's account.
We see your account, not theirs
The read-only check runs against the C2B account your business holds. It confirms an expected account credit and gives no ability to manage the account or move money from it.
FAQ
Six answers for a Swedish rollout
-
What does open banking give a Swedish business?
A payment route where the customer approves inside their own banking app and your business receives a confirmed credit on its own account. Open banking payments suit considered purchases, invoices and account funding, and they produce payment data that reconciles without anybody reading a bank statement. Across Europe the same route behaves the same way, so a Swedish business expanding does not start over.
-
How many Swedish banks are reachable?
The major Swedish banks are broadly reachable through the licensed providers behind our routes, with a longer tail that varies by provider. We check your customers' actual banks against live coverage before you build rather than quoting a national figure that ages badly.
-
What does the payment look like from the customer's side?
They select their bank, land in their own banking app, see the amount and the beneficiary, approve, and return. There is no card number, no new account to create and no credential typed into your checkout. In a market used to digital banking, that sequence needs no explanation.
-
Which party holds the licence?
The PIS provider performing the initiation, the AIS provider performing the read-only account check, and the bank or EMI holding the accounts. viaBanking is a software company with no authorisation of its own, and it does not execute payments or hold funds.
-
What does a confirmed credit mean here?
That the expected amount has been credited to the C2B account your business holds, checked in read-only mode. It is a fact about your account rather than a message about an instruction, and it is the event your systems should act on.
-
Does this cover the rest of the Nordic region?
Sweden and its neighbours run on the same integration, and switching another market on is a configuration change rather than a new build. Actual bank reach differs by market and by provider. The Norwegian market is covered on the Norway page and the regional overview on the Europe page.
Start in Sweden, keep the option on the region
Tell us which Swedish banks your customers use and where you expect to sell next. We come back with live coverage from the licensed providers behind our routes and with what the C2B account arrangement would be for your business. If open banking payments do not fit what you sell, we will say so, and the payment services you run today will keep doing the job. Most Swedish companies we work with open one market and then quietly add Europe.
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.