Accepting payments in the Nordics. 6 chapters and a final quiz.

Chapter 1. Scoping the launch: four markets, four currencies.

Launching in “the Nordics” means launching in four markets, not one: Sweden collects in Swedish kronor, Norway in Norwegian kroner, and Denmark in Danish kroner. Only Finland uses the euro. The consequence is immediate. The SEPA schemes are denominated in euros, so a SEPA direct debit mandate cannot reach any Swedish account held in SEK. Nor is there a single regional contract: the project meant to create one, P27 Nordic Payments, withdrew its application for a clearing license in 2023.

The order of these four decisions matters. A team that starts with cards ships quickly, then gets stuck. Enrolling a Swedish subscriber requires BankID, and without relying party access the flow stops dead. A team that starts with identity moves more slowly at first but never hits a wall. So identity work starts in week 1, in parallel with everything else, never after card testing.

Chapter 2. Wiring up identity: BankID, MitID, and Finland’s trust network.

In these markets, electronic ID is not just one authentication factor among many. It is the gateway to financial life: opening an account, signing a contract, approving a transfer, enrolling in a wallet. A flow that cannot call on it does not just deliver a worse experience; it does not work at all. In Sweden, Norway, and Denmark, the connection follows the same pattern: the company becomes a relying party and receives a certificate that authorizes it to request authentications. Finland is the exception, because there is no single operator to contract with.

POST /rp/{version}/auth          # client certificate required (mTLS)
{ "endUserIp": "203.0.113.10" }

201 →  { "orderRef": "131daac9-…", "autoStartToken": "7c40b5c9-…",
         "qrStartToken": "67df3917-…", "qrStartSecret": "d28db9a7-…" }

# the server then polls for status until the order resolves
POST /rp/{version}/collect      { "orderRef": "131daac9-…" }
200 →  { "status": "pending",  "hintCode": "userSign" }
200 →  { "status": "complete", "completionData": { … } }

# merchant abandons: release the session on the provider side
POST /rp/{version}/cancel       { "orderRef": "131daac9-…" }

Two side effects are worth planning for. The first concerns strong customer authentication. When bank ID carries the approval, the flow and the burden of proof shift to the ID provider, and checkout design changes: redirect or QR code, polling while the user approves, and recovery after a device switch. The second concerns business KYC, because onboarding a company relies on public registers accessed with those same identities. A project budgeted without this line item is only half budgeted.

Chapter 3. Swish, Vipps, and MobilePay: integrating and pricing.

The three apps look alike on screen but diverge underneath. Swish moves account-to-account for almost all of its payments, which settle in RIX-INST, the Riksbank’s instant payment system. Vipps in Norway runs its merchant payments on card rails. MobilePay in Denmark mostly goes account-to-account in store, and by card in e-commerce. Same kind of label, three sets of economics. Modeling costs without that distinction produces an error of several dozen basis points.

curl -X PUT \
  https://cpc.getswish.net/swish-cpcapi/api/v2/paymentrequests/AB12CD34EF56 \
  --cert merchant.pem --key merchant.key \
  -H "Content-Type: application/json" \
  -d '{
        "payeeAlias": "1231181189",
        "amount": "499.00",
        "currency": "SEK",
        "callbackUrl": "https://shop.se/swish/callback",
        "payeePaymentReference": "ORD-2026-1042"
      }'

# 201 Created, Location header = URI of the new request.
# The result does NOT come back in this response: it arrives at callbackUrl.

This call reveals three constraints. First, the only currency accepted is the Swedish krona. Second, the merchant supplies the instruction ID, so the call can be retried without creating a duplicate. Third, the callback must land on an HTTPS address reachable from the internet, which a closed test environment cannot provide. Swish’s merchant simulator exists precisely to run through failure cases before you open that port.

Chapter 4. Dankort and BankAxept: routing cards at the right cost.

Denmark and Norway are among the few European markets with an active national debit scheme. The European Central Bank now counts only eight in the EU, all of them losing ground. Most of these cards are co-badged, carrying both the domestic scheme and an international one. A payment can therefore take two routes, at two different costs. The terminal configuration and the acquiring contract decide which one.

• Check what the acquiring contract covers. A pan-European Visa and Mastercard agreement includes neither Dankort nor BankAxept. They are separate schemes, with their own rules and their own national clearing.
• Check the terminal’s brand priority. On a co-badged card, the application selected determines the cost. A priority left on the international scheme incurs interchange for no reason.
• Respect the payer’s choice. In Denmark, Regulation (EU) 2015/751 gives the cardholder the choice of brand on a co-badged card. The terminal suggests; the customer decides.
• Reconcile statements by brand. The figure to watch is the domestic versus international split, not the overall average rate.
• Track the Danish opening. A political agreement reached in June 2025 aims to fund Dankort’s development and open its acquiring to players other than Nets.
• Test offline behavior. It differs between domestic and international schemes, and it has become a policy criterion for acceptance across the region.

Chapter 5. Recurring payments, invoicing, and Klarna: collecting beyond cards.

In these four markets, subscriptions, invoices, and bulk payouts run outside the card networks, and SEPA direct debit is almost useless. It does not cover kronor or kroner, and Finnish banks, the only ones operating in euros, have largely chosen not to offer it. Denmark, Norway, and Sweden each run a long-standing domestic direct debit that is still in service, and from a distance the three rails look alike. They differ on the calendar, and that alone constrains a subscription model.

The Danish monthly cycle, from submission to possible refusal

Klarna occupies a place of its own in this landscape. The merchant delivers, Klarna pays, and Klarna collects from the buyer, either through an invoice with a due date or in installments. The operational question is timing rather than the rate: payouts follow a contractual frequency plus a settlement delay designed to absorb returns before funds are released (Klarna Docs, Settlements). The settlement report is available the day after the payout date, when the payment leaves Klarna’s account. That delay is set in the contract. Read it before signing, not when the first cash flow gap appears.

Chapter 6. Cashless society, settlement times, and go-live.

Cash has retreated further here than anywhere else, and the resulting regulatory backlash hits merchants directly. Norway made cash acceptance mandatory on retail premises through a law that took effect on October 1, 2024. A merchant that deploys checkouts without a cash drawer there risks a penalty, whatever its customers actually use.

Vipps MobilePay lets merchants choose their payout frequency: daily, weekly on Mondays, or monthly on the first of the month. The setting looks trivial, but it can shift up to a month of revenue into working capital needs. Daily payouts reduce that need but multiply the lines to reconcile; monthly payouts do the opposite. The decision belongs to treasury, not to the tech team.

• Start identity access in week 1. The contract, company verification, and certificate drive the go-live date, not the card integration.
• Set the payout frequency before go-live. It determines working capital needs and the volume of daily reconciliation.
• Document the rail behind every brand you accept. Card or account-to-account: that line drives accounting, the dispute reserve, and what customer service tells customers.
• Check how terminals behave offline. Dankort and BankAxept offer fallback modes that international schemes do not replicate exactly.
• Treat Norway’s cash requirement as a checkout design requirement, on par with the terminal.
• Add the 2026–2027 timeline to your watch list. A new Bankgirot system and the ISO 20022 deadline in Sweden, a new batch system in Denmark, and the retirement of NICS proprietary standards in Norway.