Nordic App Development: BankID, Vipps, Swish

In short: an app for Swedish, Norwegian, Danish or Finnish users usually needs three things a generic app does not: local login (BankID in Sweden and Norway, MitID in Denmark, bank and mobile IDs through the Finnish Trust Network), local payments (Swish in Sweden, Vipps MobilePay in Norway, Denmark and Finland), and EU-level compliance (GDPR everywhere, the European Accessibility Act for consumer services in the EU). None of these is hard to build, but most require an agreement through a bank or a certified broker before you get production access – so start the paperwork while the app is still being designed.

This guide walks through what to plan for each Nordic market, which integrations need agreements, how testing works and how to keep the schedule realistic. Technical details below come from the providers' own developer documentation.

The Nordic checklist at a glance

Cards, Apple Pay and Google Pay through a payment service provider work in all four countries; the local wallets are what users often look for first. Identity is only needed if your service requires strong identification – many apps work fine with email or social login.

Login and identity

BankID in Sweden

Swedish BankID is accessed through its relying-party (RP) API, currently version 6.0. According to BankID's documentation, the API can only be accessed with a valid certificate, which you order from the bank you have your BankID agreement with. In practice that means: agreement with a bank first, then certificate, then production integration. BankID has also ended support for static QR codes in API version 6 – login on another device uses an animated QR code, while on the same device the app opens BankID directly. Older RP API versions 5.0 and 5.1 have been discontinued, so check any existing integration.

BankID in Norway

Norway's BankID is a different scheme from Sweden's, with its own providers and integration path. Do not assume a Swedish integration covers Norwegian users.

MitID in Denmark

Danish services connect to MitID through certified MitID brokers rather than directly. Choose a broker early – its onboarding and pricing become part of your project plan.

Finland: the Finnish Trust Network

In Finland, banks, telecom operators and the Digital and Population Data Services Agency provide strong identification means, and identification brokers forward identification events to online services. A service typically integrates with one broker and reaches the bank and mobile IDs through one agreement and one interface. Traficom, the Finnish regulator, keeps a public register of providers.

Payments

Vipps MobilePay (Norway, Denmark, Finland)

Vipps MobilePay offers developers three main APIs – ePayment, Login and Recurring – plus supporting APIs such as QR, Webhooks and Order Management. Key points from its documentation:

• Merchants with API access get a separate Merchant Test environment with its own credentials, test users and a test app; normal Vipps or MobilePay credentials do not work there.
• Test sales units follow the merchant's country, so a Norwegian merchant creates Norwegian sales units, a Danish merchant Danish ones and a Finnish merchant Finnish ones.
• Payments switch from your app to the Vipps or MobilePay app and back. The production URL scheme is vipps://, the test app uses vippsMT://, so both can be installed side by side.
• The ePayment API recommends the web-redirect flow; the native-redirect flow is not recommended except where the merchant has no web presence.
• There are no settlements in the test environment, and test support is available during office hours (CET).

Swish (Sweden)

Swish is always connected through a bank. According to Swish, the merchant signs an agreement with a bank, the bank creates a Swish number for that agreement and registers who may generate the API certificate (the certificate point of contact). That person creates the certificate in Swish Certificate Management after logging in with BankID. A technical partner can integrate the Swish API for you, but payments always go to and from your own bank account. Swish also provides a Merchant Swish Simulator for testing.

Compliance: GDPR and accessibility

• GDPR applies in Sweden, Denmark and Finland as EU members, and in Norway through the EEA Agreement. Plan data minimisation, consent where needed, retention and a written processor agreement with every supplier that handles personal data, including your development team.
• The European Accessibility Act applies from 28 June 2025 to consumer services such as e-commerce, consumer banking and passenger transport apps in EU countries – Sweden, Denmark and Finland. Norway is in the EEA rather than the EU; check the current status of the act there. Our European Accessibility Act guide for apps explains scope, exemptions and testing.
• Payment and identity providers' own rules – brand guidelines for buttons, required user flows and security requirements – are part of acceptance by the provider.

Localisation is more than translation

• Languages: Swedish, Norwegian, Danish and Finnish are separate languages; Finland is officially bilingual (Finnish and Swedish). Many Nordic users read English well, but consumer apps are expected in the local language.
• Formats: currency (SEK, NOK, DKK, EUR in Finland), decimal commas, date formats and 24-hour time.
• Store listings: localised App Store and Google Play texts and screenshots for each market.
• Support and legal texts: terms, privacy information and accessibility information in the local language.

Typical Nordic app scenarios

Most projects start in one country and expand. Designing the login and payment layer so that a second provider can be added later is cheaper than rebuilding it.

How to plan the project

1. Decide the markets for version one. Launching in one country first keeps integrations and translations manageable.
2. Choose identity and payment providers during scoping and apply for agreements immediately – bank and broker onboarding runs on their schedule, not yours.
3. Build against test environments (Vipps MobilePay Merchant Test, the Swish simulator, provider test setups) while agreements are processed.
4. Design for accessibility and localisation from the first screens – longer Finnish words and larger text sizes break tight layouts.
5. Leave time for store review and provider acceptance before your launch date. Our app development timeline guide lists the fixed waiting times.

Working with a partner in the same time zone

Stockholm, Oslo and Copenhagen share Central European Time with Prague, and Helsinki is one hour ahead, so a Czech team works your working day. We explain the model in nearshore app development in Europe.

VIA Marketing builds Android and iOS apps – including booking, e-commerce, loyalty and fintech apps with payment flows and integrations – with published starting prices from €4,900 for a smaller MVP. See our mobile app development services, get a range from the cost calculator or send us your brief with the markets and providers you need.

FAQ

Do I need a bank agreement to integrate Swedish BankID?

Yes. BankID's documentation says the API can only be accessed with a valid certificate, which you order from the bank you have your BankID agreement with. Plan the agreement before production integration.

Which payment app should a Nordic app support?

Swish in Sweden and Vipps MobilePay in Norway, Denmark and Finland are the local mobile payment methods users expect. Cards, Apple Pay and Google Pay through a payment provider cover all four markets.

Can I test Vipps MobilePay before I have a live agreement?

Merchants with API access get a separate Merchant Test environment with test users and a test app. The test environment has its own credentials and no settlements, and it can be installed alongside the production app.

How does a Danish app add MitID login?

Through a certified MitID broker. The broker provides the integration and its own terms, so choosing one is part of the project plan.

Does GDPR apply in Norway?

Yes. Norway is not an EU member, but it applies the GDPR through the EEA Agreement, so the same data protection rules apply to Norwegian users as in Sweden, Denmark and Finland.

Does a Nordic consumer app have to be accessible?

In EU countries – Sweden, Denmark and Finland – the European Accessibility Act applies from 28 June 2025 to services such as e-commerce, consumer banking and passenger transport, including their mobile apps. Microenterprises providing services are exempt.

Sources (checked 2 November 2026): BankID — API references (RP API v6.0), integration guide, static QR support ended, RP API 5.0/5.1 discontinued; Vipps MobilePay — developer documentation, test environment, ePayment API; Swish — getting started, environments; MitID — MitID broker; Traficom — electronic identification (Finnish Trust Network); Directive (EU) 2019/882, Article 2.