Accepting MobilePay in Denmark and Finland

MobilePay is the dominant mobile payment solution in Denmark and Finland, and it now operates as part of Vipps MobilePay, the combined Nordic entity that also runs Vipps in Norway. For a merchant selling into the Nordics that consolidation is useful: one commercial relationship can cover markets that used to require several.

Set-up

How to accept MobilePay as a merchant

You do not contract with the scheme directly in the usual sense. Acceptance runs through Vipps MobilePay or a PSP connected to it, and the customer authorises the payment inside their own app. It is account-based rather than card-based, and it settles without card interchange, which is the main reason the economics differ from card acceptance and the main reason those economics vanish under a blended rate.

Treat the Nordics as several markets, not one

The single entity does not mean a single market. Consumer preference, basket profile and competitive dynamics differ between Denmark, Finland, Norway and Sweden, where Swish leads. A Nordic payment strategy built as one configuration usually means one of those markets is being served with someone else’s optimum. The correction is not more methods; it is per-market measurement of what converts and what each conversion costs.

Timetable

Denmark and Finland run on different instant payment calendars

The section above says treat the Nordics as several markets. Here is the sharpest example of why, and unlike most such arguments it comes with dates.

Finland is in the euro area, so under Regulation (EU) 2024/886 its payment service providers had to be able to receive instant euro payments from 9 January 2025 and send them from 9 October 2025, and to offer verification of payee from 9 October 2025. Denmark is not in the euro area. The same regulation gives payment service providers located in a Member State whose currency is not the euro until 9 January 2027 to offer receiving instant euro credit transfers, until 9 July 2027 to offer sending them, and until 9 July 2027 to comply with the verification of payee obligation.

So the same wallet brand, run by the same company, sits on two infrastructure clocks. The euro rail underneath your Finnish volume is already instant and already name-checked; the Danish equivalent arrives in stages through 2027. It also means the name registered on the account behind your IBAN is being shown to Finnish payers today and reaches Danish payers by July 2027, and in both cases a mismatch with your trading name produces a warning at the moment of authorisation. One entity, two calendars, one checklist that has to be run twice.

EuroPA

EuroPA and the February 2026 MoU

On 2 February 2026 Vipps MobilePay signed a Memorandum of Understanding with Bancomat, Bizum, SIBS-MB WAY and EPI Company to build a central interoperability hub, with the ambition of seamless cross-border payments across Europe by 2027. The published sequence is cross-border person-to-person payments during 2026, then e-commerce and point-of-sale payments in 2027. Each solution keeps its own brand, features and user experience, with a new badge alongside to signal wider acceptance. A proof of concept for cross-border QR-based in-store payments between participating solutions completed on 16 April 2026. The EuroPA alliance now spans more than 100 million users in ten European countries.

Which payment provider supports MobilePay for merchants in the Nordics?

QuickPay and OnPay in Denmark, Paytrail in Finland and Nexi through Nets all document MobilePay, among others, as do the other gateways serving the region. The useful questions are what you pay per MobilePay transaction against your effective card rate in the same market, whether the line is reported separately, and whether your provider is positioned for the EuroPA rollout.

Configuration

One Nordic configuration across four markets, priced

A single Nordic set-up is cheap to build and expensive to run, because the optimum in one market is a compromise in the other three. That sentence is only worth reading with a number attached.

Take 12 million euros of Nordic revenue split evenly across Denmark, Finland, Norway and Sweden, so 3 million each. Suppose the domestic wallet in each market runs at 0.8 per cent and cards at 1.4 per cent, and suppose your configuration puts the wallet first in one market and cards first in the other three, out of habit rather than decision. In those three markets, assume that ordering leaves a quarter of the volume on cards that would otherwise have gone to the wallet. That is 2.25 million euros at a 0.6 point difference, so 13,500 euros a year given away to a default.

And that is before conversion. Where a domestic wallet has high penetration it usually completes better than a card, so add one point of completion on the 9 million euros running through those three markets and you have 90,000 euros of revenue that was never arriving. Building a per-market checkout configuration is a sprint. Not having one costs every year, quietly, because a Nordic report that sums four countries into one line is arithmetically correct and commercially useless.

Reviewing what MobilePay costs you

What you pay is set in your agreement, not by the scheme. Start by establishing whether you are overpaying your PSP, or move straight to cutting your PSP costs, because a cheap method priced badly still costs more than it should.

How a wallet behaves inside your flow, from one-click through to the return after a challenge, is a checkout flow optimisation question as much as a pricing one.

Relevant markets: Denmark, Finland