Payment Platforms for Nordic SaaS and POS Providers: One Stack for Every Channel

Nordic software providers rarely get to pick one payment channel. A booking system takes a deposit online and the rest at the salon. A journal system charges a patient at reception today and a care plan next month. A POS vendor sells terminals into stores that also run a webshop. And the payment methods those merchants' customers expect differ in every one of the four countries. This guide explains which payment platforms actually support in-store terminals, online payments and subscriptions in one stack, what that stack has to cover in Sweden, Norway, Denmark and Finland, and how to compare the options.

It is written for the people who make that decision inside a Nordic SaaS, POS or booking company: the CTO who has to integrate it, the product lead who has to explain it to merchants, and the CEO who wants a share of the payment revenue rather than a referral fee.

Key Takeaways: Payment Platforms for Nordic SaaS and POS Providers

• Few platforms offer in-store terminals, online payments and recurring billing through one integration in the Nordics. Adyen, Stripe and Surfboard Payments do. Most other providers sell a bundle of separate products under one contract, or cover only one channel.
• Nordic consumers pay by card and phone almost everywhere, but the local method is different in every market: Swish in Sweden, Vipps and BankAxept in Norway, MobilePay and Dankort in Denmark, MobilePay and online bank payments in Finland. A platform that supports one of them has not covered the region.
• "Unified" should mean one order object, one customer token that works at the terminal and online, one settlement and one onboarding flow. If any of those are missing, you are stitching a stack, not buying one.
• For subscriptions, evaluate tokenization with merchant-initiated transactions, network tokens with automatic card updates, and whether the local wallets support recurring agreements. Stripe's Swish, for instance, is single-use only.
• Surfboard Payments puts every method, including American Express, Swish, Vipps, MobilePay, Dankort, BankAxept and Klarna, on one contract and one payout, across in-person, online and unattended channels, with API onboarding, white-label branding and partner-set pricing built in for software providers.

Which payment platforms support both in-store terminals and online payments?

Start with the direct answer. Across the Nordics today, the platforms that let one merchant account accept card payments on a physical terminal and in a web checkout, from the same provider, fall into three groups.

Unified platforms with one API. Adyen, Stripe and Surfboard Payments expose terminals, online checkout, tokenization and recurring charges through a single integration, with a platform model for software companies that onboard their own merchants. Adyen describes it as connecting "your online and offline payments in one system using unified commerce". Stripe's Terminal page promises to "manage online and in-person payments in one place for simplified reporting and a unified customer view". Surfboard Payments uses one order object with a channel field that switches between in-store, online and unattended, and one customer token across all of them.

Bank-owned and incumbent acquirers selling a bundle. Swedbank Pay and Nexi (formerly Nets) operate in all four countries and sell terminals, a hosted checkout and the local wallets under one agreement with next-bank-day payout. Swedbank Pay's pitch is "allt du behöver i ett paket, från kortterminal till inlösenavtal". What they do not publish is an API-driven sub-merchant onboarding model for software providers. Their platform story is a reseller or partner program, which is a different thing.

Small-business readers. Zettle by PayPal and SumUp offer inexpensive card readers with blended pricing in every Nordic market. Zettle accepts Swish, SumUp does not. Neither offers a payment facilitator model or cross-channel tokens, and their online acceptance runs through third-party webshop plugins or payment links. They are the right answer for a sole trader and the wrong answer for an ISV.

Two names come up in every Nordic conversation and belong in neither list. Mollie launched online payments in Sweden in April 2025 but has only rolled out terminals in Belgium, Germany and the Netherlands. Klarna is a payment method your platform should offer, not a platform to build on: it reaches the checkout through payment platforms and the store through partner terminals and its own consumer wallet.

Comparison table: payment platforms for Nordic software providers

Platform	Terminals in the Nordics	Swish, Vipps, MobilePay	Dankort, BankAxept	Recurring / subscriptions	API merchant onboarding for ISVs	One contract and payout for all methods
Surfboard Payments	✓ Own terminal range, SoftPOS, kiosks	✓ All three, in-store, online, unattended	✓ Both, routed domestically	✓ Tokens + merchant-initiated	✓ Built-in KYB, partner billing, white-label	✓ Incl. American Express
Adyen	✓ Incl. Swish QR on terminal	✓ All three, Swish recurring-capable	Dankort ✓, BankAxept not published	✓ Network tokens, cross-channel	✓ Adyen for Platforms	✓ Minimum invoice applies
Stripe	✓ Stripe Terminal, Tap to Pay	Swish single-use only, MobilePay ✓, Vipps not published	Not published	✓ Stripe Billing (cards)	✓ Stripe Connect	✓ Blended pricing
Swedbank Pay	✓ PAX terminals	✓ All three	✓	✓ Card tokens	Partner portal, not API	✓
Nexi / Nets	✓ SmartPOS	✓ All three	✓ Dankort processor	✓ Card-on-file	Not published for the Nordics	✓
Zettle by PayPal	✓ Readers from 249 kr	Swish ✓, others not published	Not published	✗	✗	Partial
SumUp	✓ Readers from 225 kr	✗	Not published	Limited	✗	Cards only
Mollie	✗ No Nordic terminals	Swish and MobilePay online	✗	✓ Subscriptions API	✓ Connect for Platforms	Online only

Sources are each provider's public documentation and pricing pages as of September 2026. "Not published" means the provider does not state the capability for the market publicly, which in an evaluation should be treated as a question to put in writing, not as a no.

Why Nordic software providers need one payment stack rather than three

The Nordic markets punish fragmentation harder than most because customers move between channels constantly, pay with their phones more than almost anyone else, and expect every channel to work.

In Sweden, the Riksbank's Payments Report 2026 found that 61 percent paid their last in-store purchase with a physical card and 18 percent with a card in their phone, while cash was 5 percent. In the previous 30 days, 91 percent had used Swish and 80 percent had shopped online. In Norway, Norges Bank reports that 27 percent of payments at physical terminals in 2025 were made with a mobile phone, up from 12 percent a year earlier, and that online payments were 28 percent of all Norwegian card payments. In Denmark, Danmarks Nationalbank puts mobile wallets at around 38 percent of card payments in physical commerce by the end of 2024. Finland has been Europe's most enthusiastic pay-by-bank market online for years.

E-commerce keeps growing on top of physical retail, not instead of it. Swedish e-commerce alone reached SEK 153 billion in 2025 according to PostNord's E-barometern, up 10 percent and the highest figure ever recorded. A wellness studio, a clinic, a restaurant group or a specialty retailer using your software is running both channels, in whichever country it sits.

The Riksbank's survey of Swedish small businesses adds a detail that matters for pricing conversations across the region: one in three do not know what their payments cost, and 56 percent say getting paid immediately rather than in one to three days is important. A software provider that can put all channels and all methods on one settlement report with one fee schedule is solving a problem merchants feel every month.

For POS and journal system vendors there is also a regulatory reason. Sweden requires sales paid by card, cash or Swish to be registered in a certified cash register connected to a control unit or a certified control system, with SKVFS 2021:17 mandatory from 1 January 2027. Norway has its own cash register systems act with product-declared systems, and Denmark requires digital sales registration systems in selected sectors. If the payment layer and the register are integrated once, compliance is one project per country. If the terminal comes from one vendor and the checkout from another, the reconciliation between register journal and payment data is yours to maintain.

What Nordic payment methods must the platform cover?

The Nordic countries share a language family, a design sensibility and a habit of paying with a phone, but they do not share payment methods. A platform that treats "Nordic" as "card rails plus one wallet" will cost you conversions in three of the four countries.

Sweden: Swish, cards and Klarna

Swish is the account-to-account standard, used by 91 percent of Swedes in a given month, and it belongs in-store, online and at unattended kiosks. Klarna leads buy now, pay later online. Apple Pay and Google Pay are growing fast at the terminal, with card-in-phone payments doubling from 9 percent of last in-store purchases in 2023 to 18 percent in 2025. Confirm that Swish is a native integration on every channel rather than a redirect, and read the fine print: Stripe's Swish is single-use, is not supported in subscription mode, and Stripe appears as the recipient in the customer's app because Stripe acts as merchant of record.

Norway: Vipps and BankAxept

Vipps is the wallet, and the merged Vipps MobilePay group reported 12.4 million users, 580,000 sales units and 1.4 billion transactions across the Nordics in 2025. Norway also has a domestic debit scheme most international platforms ignore. According to Norges Bank, BankAxept carried 70 percent of payments at physical terminals in Norway in 2025. A platform that routes BankAxept-capable cards over an international scheme instead of the domestic rail hands Norwegian merchants a higher bill, and with online at 28 percent of Norwegian card payments, Vipps has to work in the checkout as well as at the counter.

Denmark: Dankort and MobilePay

Dankort is the national debit card, usually co-badged with Visa, and Danmarks Nationalbank puts its interchange for physical commerce at 0.125 percent, far below international scheme cards. Correct co-badge handling at the terminal is therefore a merchant economics question, not a compliance detail. Danish shoppers are also the region's fastest adopters of wallets at the counter, mostly Apple Pay and Google Pay, while MobilePay dominates mobile payments online.

Finland: online bank payments, MobilePay and Epassi

Finland is the euro market in the group, and Finnish consumers still prefer to pay online directly from their bank, according to PostNord's 2025 Nordic e-commerce research, with cards and mobile wallets gaining ground since 2024. That makes Pay by Bank a first-class method rather than an experiment, and MobilePay the wallet to support. For booking systems serving gyms, studios and clinics, Epassi employee benefits are a baseline expectation at Finnish wellness merchants and increasingly in Sweden.

Across all four: cards, wallets, Klarna and invoice

Visa and Mastercard are universal. American Express matters for corporate buyers, travel and hospitality, and is often the card a platform quietly leaves off the payout or routes through a separate agreement. Klarna is expected online everywhere in the region. Invoice remains an unusually normal way to pay in the Nordics, both B2C and B2B, so check that invoicing is a payment method on the platform rather than a bolt-on.

Four countries also means four currencies. SEK, NOK and DKK float independently and Finland uses the euro, so ask how the platform settles a merchant operating in more than one of them and what the foreign exchange pricing looks like.

What "unified commerce" actually means, and what it does not

Every provider in the table above uses the word omnichannel. The test is whether the following four things are literally the same object in their API.

One order and one payment lifecycle

The same endpoint should create an order whether it will be paid at a terminal, on a hosted page or by a stored token. Webhooks should carry the same event names regardless of channel. If the in-store product has its own authentication scheme, error codes and event schema, you will build two integrations and maintain two.

One customer token across channels

A card saved online should be recognised when the same customer taps at the counter, and a card tapped at the counter should be chargeable later for a subscription. Adyen documents this explicitly: a token created at the point of sale can be used in a later online payment. Surfboard Payments provisions network tokens through Visa and Mastercard so the same token works online, at terminals and for recurring charges, and the card updates automatically when it is replaced. Providers that cannot do this force your merchants to ask customers for their card twice.

One settlement and one report

Merchants want one payout per day covering cards, local wallets and domestic debit, and one report that reconciles against their POS or booking data. Ask whether that still holds when the merchant adds a second store, a webshop, a subscription product and an American Express card. On Surfboard Payments, every method rolls into the same settlement report and the same payout, Amex included.

One onboarding flow and one contract

If a new merchant has to sign a terminal agreement, an acquiring agreement, a gateway agreement and a separate agreement per local payment method, onboarding will take weeks and your sales team will spend them chasing signatures. A unified platform runs know-your-business checks once, provisions every channel and every method from the same merchant record under one contract, and lets you do it through an API embedded in your own signup flow.

How to evaluate in-store terminal support

In-store is where platforms differ the most, because hardware, certification and logistics are hard to fake.

Terminal range and who controls the software on it

Ask which devices are available in each Nordic market, whether they are countertop, handheld, self-service or unattended, and whether your own application can run on the terminal. Android-based terminals that are openly programmable let a POS or journal system run directly on the device beside the payment application, with no separate cash register hardware and no cable between them. Surfboard Payments' range covers countertop printers such as SurfPrint Pro, handhelds such as SurfTouch Pro, the compact SurfMini, and SurfAlone and SurfXpress for unattended and self-service scenarios, and every device runs the same payment application against the same API.

SoftPOS as a hardware alternative

Tap to Pay on iPhone and Android SoftPOS turn phones and tablets the merchant already owns into certified terminals. Availability differs by country, so confirm which Nordic markets a provider has live rather than announced. Surfboard Payments offers Tap to Pay on iPhone and CheckoutX for Android. For booking systems whose merchants are mobile, such as home services, personal trainers or market traders, this removes hardware logistics entirely.

Local methods at the counter

Swish, Vipps and MobilePay in-store are QR or number-based flows. Confirm the platform supports them on the terminal screen rather than on a printed card, that refunds work from the same interface, and that they land in the same reporting as cards. Confirm too that Dankort co-badging and BankAxept routing are handled at the terminal without the merchant choosing anything. The Riksbank notes that although 74 percent of Swedish small firms accept Swish, only about 12 percent of their business payments arrive that way, so the point is coverage, not volume.

Offline handling and terminal management

Ask how the terminal behaves when the network fails and how many devices one operations person can manage remotely. Zero-touch configuration, remote key updates and a device management API matter once you have hundreds of merchants rather than five, and they matter more in rural Norway and Finland, in mountain and archipelago locations, and at outdoor events.

How to evaluate online payment acceptance

Hosted page or self-hosted checkout

A hosted payment page keeps card data entirely off your servers and out of your PCI DSS scope. A self-hosted checkout gives you pixel-level control of the flow inside your product. Good platforms offer both from the same order API. PCI DSS v4.0.1 became the only active version at the start of 2025, and its future-dated requirements took effect on 31 March 2025, including the payment-page script inventory and tamper-detection requirements that e-commerce integrators cite most often. Ask the platform how their hosted fields help you meet those two.

Strong Customer Authentication without losing the sale

3-D Secure 2 with sensible exemption handling is the difference between a checkout that converts and one that fails silently on the second step. Ask for authorisation rate data by card type and country, and ask how the platform handles merchant-initiated transactions so that your subscription renewals are not challenged every month.

Whose name the customer sees

With account-to-account methods the payee name is visible in the customer's banking app. If the platform acts as merchant of record, the customer sees the platform, not the merchant, which is a real problem for a clinic or a salon. Ask explicitly for Swish, Vipps and MobilePay.

How to evaluate subscription and recurring billing

Subscriptions are where "supports online payments" and "supports our business model" diverge. A gym membership, a clinic's care plan, a SaaS seat fee charged to the merchant, and a monthly box are all recurring, and they need different things.

Tokenization and merchant-initiated transactions

The customer's first payment should tokenize the card and record the recurring agreement, including frequency, amount type and whether the first payment was authenticated. Subsequent charges are merchant-initiated transactions against a server-to-server terminal, with no customer present. Surfboard Payments' recurring payments guide walks through exactly this lifecycle, including fixed and variable amounts, twelve frequency options from daily to annual, and an unscheduled mode for usage-based billing.

Network tokens and automatic card updates

Cards expire and get replaced. Network tokens from Visa and Mastercard update automatically, so the subscription survives a new card. Adyen provides this through its account updater, and Surfboard Payments provisions network tokens by default. Providers that only store a PAN-derived token will have a failed-payment problem every time a bank reissues cards.

Recurring agreements in the local wallets

Swish now offers merchant-initiated recurring payments, called Swish Återkommande betalningar, where the customer approves the agreement with BankID in the Swish app. It is offered through each bank rather than centrally, requires a Swish API connection, and consumer-side management in the app was initially limited to certain banks. Swedbank prices it at 3.50 kr per transaction with a monthly fee per Swish number. Vipps and MobilePay have their own recurring agreement products for subscriptions. If your merchants sell memberships to Nordic consumers, ask each platform which of these it supports, and treat "cards only" as a meaningful gap.

Billing the merchant, not just the customer

If you are a software provider, you also need to bill merchants for the payment service itself. Stripe Billing charges 0.7 percent of billing volume in Sweden, or a fixed monthly fee for larger accounts, to run subscriptions. Surfboard Payments' Billing API works the other way round: partners define their own pricing plans per merchant, store or terminal, choose fixed or interchange-plus models, add usage-based charges, and let the platform handle invoicing and settlement deductions. That is the mechanism through which embedded payments become revenue.

How to evaluate the platform model for software providers

The software provider's relationship with a payment platform is structurally different from a merchant's. You are not the one accepting payments. Your customers are. Four capabilities decide whether a platform understands that.

API-driven merchant onboarding with built-in KYB

Adyen for Platforms and Stripe Connect both let you create sub-merchant accounts, collect know-your-business information and go live without a sales call for each merchant. Surfboard Payments offers programmatic onboarding that runs identity checks against the company registry in each country, orders terminals and configures branding in one flow, with a record of five hours from signup to first live transaction. Partner portals where you can create agreements and follow status are useful, but they are not an API.

White-label branding

Your merchants trust your brand. Ask whether the terminal screen, receipts, hosted checkout, merchant portal and customer emails can carry your name and colours rather than the platform's. Surfboard Payments' white-label system covers every customer-facing surface with no "powered by" line anywhere. Neither Adyen nor Stripe publishes terminal branding options for the Nordics, so ask.

Acquirer flexibility

Most platforms tie you to their own acquiring. That is convenient until pricing changes or authorisation rates drop. An acquirer-agnostic platform lets you switch or add processing relationships without re-integrating, and negotiate. Sweden and Finland run every card transaction on Visa or Mastercard rails, while Norway and Denmark have domestic debit schemes with much lower cost, so a platform that can route to the right rail per country is worth real money to merchants in every market.

Revenue share versus referral fee

Adyen and BCG estimated the embedded payments and finance opportunity for SaaS platforms at 185 billion dollars in 2024, with top platforms earning more than half their revenue from it. Whether you see any of that depends on the contract. A referral fee pays you once. A revenue share on interchange-plus pricing pays you on every transaction for as long as the merchant stays, and a billing layer where you set the price lets you decide what the margin is.

What Surfboard Payments covers under one contract

Since this guide is written by one of the platforms in the table, here is exactly what that row means, so you can hold us to it in the same evaluation.

• One contract, one payout, every method. Visa, Mastercard and American Express, Swish, Vipps, MobilePay, Dankort, BankAxept, Klarna, Pay by Bank, Epassi and B2B invoice all sit on the same merchant agreement and roll into the same settlement report and the same payout. Amex is not a separate agreement or a separate payout. There is no per-method paperwork to chase.
• Every channel from one API. Terminals, Tap to Pay on iPhone and Android SoftPOS, self-service kiosks and unattended devices, hosted payment pages and self-hosted checkout all use the same order object, the same webhooks and the same reporting. A merchant's customer token works across all of them and for recurring charges.
• Built for the software provider. Merchant onboarding with built-in KYB, terminal ordering and branding through the API. A Billing API where you set the merchant's pricing, fixed or interchange-plus, and keep the margin. White-label down to the terminal screen and the receipt.
• Nordic by design, acquirer-agnostic. Live in Sweden, Norway, Denmark and Finland as well as the UK, France, Ireland and Estonia, with domestic schemes routed correctly and local methods native on every channel. Acquirer-agnostic, so the processing relationship can change without a re-integration.
• Licensed and resilient. Surfboard Payments AB is a payment institution licensed by Finansinspektionen in Sweden and passported across the EEA, headquartered in Stockholm. The platform runs PCI DSS certified infrastructure across Google Cloud, AWS and Azure at the same time, with 99.99 percent uptime.

Put the same list in front of every other provider you evaluate. The answers that come back in writing are the comparison that matters.

How to compare pricing, settlement and contract terms

Interchange-plus or blended

Adyen prices on interchange-plus with a fixed processing fee and a minimum monthly invoice that depends on the business model. Stripe publishes blended rates per country; in Sweden they are 1.5 percent plus 1.80 kr for standard European cards online and 1.4 percent plus 1.00 kr for cards at a Stripe Terminal, with interchange-plus available on custom deals. Zettle charges 1.85 percent flat in Sweden and SumUp 1.49 percent, or 0.79 percent with a monthly plan. Swedbank Pay advertises rates from 0.99 percent.

Blended pricing is easy to explain to a small merchant. Interchange-plus is cheaper at volume, reflects the low domestic interchange on Dankort and BankAxept, and is the only model in which a software provider can transparently add a margin. Ask for both and model your merchant base against each, country by country.

Settlement speed

Next bank day is the Nordic norm. Swedbank Pay promises "pengarna på kontot redan nästa bankdag". Adyen pays out on a sales-day basis with a delay of typically two business days. Zettle moves funds to a PayPal business account within minutes, with a further one to two days to a bank account. Given that a majority of small firms tell the Riksbank they want to be paid immediately, settlement speed is a real differentiator, not a footnote. Check separately whether every method, Amex and local wallets included, settles on the same schedule, and in which currency.

Lock-in and minimums

Read for minimum monthly invoices, rental periods on terminals, early-termination fees and what happens to your merchants' tokens if you leave. Portability of stored payment methods should be in the contract before the first merchant is onboarded.

How to assess compliance, licensing and the regulatory horizon

Licensing in the Nordics

Each market has its own financial supervisor: Finansinspektionen in Sweden, Finanstilsynet in Norway and in Denmark, and Finanssivalvonta in Finland. A payment institution licensed in one EEA country can passport into the others, and Norway is covered through the EEA agreement. Passporting is legal and common, but a partner that is licensed in the region and staffed in the region makes conversations with your merchants' auditors shorter.

PCI DSS and infrastructure

Ask for the platform's PCI DSS attestation, its uptime record and how it is hosted. Whatever the provider, ask to see twelve months of incident history rather than a status page badge.

What changes between now and 2028

• PSD3 and the Payment Services Regulation. Political agreement was reached in November 2025 and the final texts were published in April 2026. Once in the Official Journal, the regulation applies roughly 21 months later, which points to 2028. Expect clearer treatment of merchant-initiated transactions under strong customer authentication and mandatory payee verification on transfers. Norway follows through the EEA.
• Instant payments. Finnish providers, being in the euro area, have been covered by the EU Instant Payments Regulation since 2025. Swedish and Danish providers must receive euro instant payments from 9 January 2027 and send them, with verification of payee, from 9 July 2027. For krona, the Riksbank expects the market to offer instant account-to-account payments outside Swish, or a plan for them, by March 2027.
• Cash register rules. Sweden's SKVFS 2021:17 applies to all cash registers from 1 January 2027, with journal memory exportable as XML and cloud control systems certified under SKVFS 2020:9 as the alternative to a physical control unit. Norway and Denmark have their own register requirements, and each is a reason to keep payments and register integration on one platform.

A platform that already treats merchant-initiated transactions, account-to-account payments and register integration as first-class features will absorb these changes. One that treats them as roadmap items will hand the work to you.

How Adyen and Stripe compare for a Nordic software provider

Both are serious options and both appear in most shortlists, so it is worth being specific about where each fits.

Adyen

The most complete global unified commerce platform, with terminals, online, cross-channel tokens, Swish, Vipps, MobilePay and Dankort, and a mature platform product. Swish works online and at the terminal and supports recurring. Enterprise minimums, interchange-plus only, and a two-business-day payout delay make it a better fit for large merchants and large platforms than for an ISV whose customers are small businesses.

Stripe

The strongest developer experience and the most complete billing product, with Stripe Terminal, Tap to Pay and Connect available in the Nordics, and MobilePay for Denmark and Finland. The local methods are the weak point: Swish is single-use, not available for subscriptions, and shown under Stripe's name, while Vipps, Dankort and BankAxept are not published for Stripe's Nordic accounts. Blended pricing is simple but leaves little room for a platform margin without a custom agreement.

Everyone else

Swedbank Pay and Nexi are reliable, locally rooted and good at bundling for a merchant who wants one invoice; for a software provider they are partners in the reseller sense. Zettle and SumUp are excellent for a sole trader who needs a reader tomorrow and not built for programmatic onboarding. Mollie is a strong online and subscriptions provider but cannot unify in-store in the Nordics without terminals.

Questions to ask before you sign

• Show me one order that is paid at a terminal, and the same customer's next order paid online with the stored token. Same endpoint, same webhook?
• Which terminals are in stock today in Sweden, Norway, Denmark and Finland, and can our application run on them?
• Do Swish, Vipps and MobilePay work at the terminal, online and for recurring agreements, and whose name does the customer see?
• Are Dankort co-badging and BankAxept routing handled at the terminal automatically?
• Is American Express on the same contract and the same payout as everything else?
• Can we onboard a merchant end to end through your API, including KYB and terminal ordering, with no ticket to your team?
• Can we set the merchant's price and keep the margin? Show me the billing configuration.
• Where does your brand appear on the terminal, receipt, checkout and portal, and can it be removed?
• What is your payout timing per country and per method, and what is the minimum monthly invoice?
• How do you integrate with certified cash register systems in each country?
• What is your incident history for the last twelve months?

In Conclusion: Choosing a Payment Platform for Nordic SaaS and POS Providers

The question "which payment platforms support both in-store terminals and online payments" has a short answer and a long one. The short answer in the Nordics is Adyen, Stripe and Surfboard Payments as unified platforms, with the bank-owned and incumbent acquirers as bundles. The long answer is that terminals plus online is the entry ticket. The decision turns on whether one token follows the customer across channels and into a subscription, whether Swish, Vipps, MobilePay, Dankort and BankAxept are first-class methods on every channel, whether every method including Amex lands on one contract and one payout, and whether the platform is built for a software provider to onboard, brand and price its own merchants.

Evaluate on those criteria, put the unpublished answers in writing, and pick the partner whose economics improve as your merchant base grows rather than the one whose price list is easiest to read.

FAQs about Payment Platforms for Nordic SaaS and POS Providers

Which payment platforms support both in-store terminals and online payments in the Nordics?

Adyen, Stripe and Surfboard Payments offer terminals and online checkout through a single integration with shared tokens. Swedbank Pay and Nexi offer both channels as a bundled agreement in all four countries. Zettle and SumUp offer readers with online acceptance through plugins or links. Mollie is online-only in the region, and Klarna is a payment method rather than an acquirer.

Which payment platform is best suited for Swedish SaaS companies with subscription-based models?

It depends on who the subscriber is. For billing your own SaaS customers by card, Stripe Billing is the most mature product. For letting your merchants sell memberships and care plans to consumers, look for tokenization with merchant-initiated transactions, network tokens with automatic updates and Swish recurring support. Surfboard Payments and Adyen support recurring tokens across channels; Stripe's Swish does not support recurring payments.

How do we choose a payment service provider that can handle both online and in-store transactions?

Test whether the in-store and online products share one order API, one customer token, one settlement and one onboarding flow. If any of those are separate, you are buying two products with one logo. Then check local method coverage on every channel in every country you sell into, terminal availability, pricing model and payout timing.

Which cloud-based payment platforms are best for software providers?

Platforms with an API-driven merchant onboarding model, white-label branding and a billing layer that lets the software provider set pricing. In the Nordics that means Adyen for Platforms, Stripe Connect and Surfboard Payments. Surfboard Payments is the only one of the three built specifically for ISVs and headquartered in the region.

How does one compare different payment platforms for journal and business systems in Sweden?

Start with the merchant's real flows: a deposit online, the balance at reception, a monthly plan charged automatically. Then check that the platform supports certified cash register integration, keeps card data out of the journal system entirely through tokenization and hosted fields, and can bill the practice's clients by card and Swish on a schedule. Finally, compare what the platform lets you, the software provider, earn and control. The same test applies to journal systems in Norway, Denmark and Finland with Vipps, MobilePay and Pay by Bank in place of Swish.

Do we need Swish, Vipps and MobilePay, or is one enough?

You need all three if you serve the whole region. Swish is Sweden, Vipps is Norway, MobilePay is Denmark and Finland. Vipps and MobilePay share an owner but remain separate consumer products with separate integrations, and consumers do not substitute one for another. Dankort in Denmark and BankAxept in Norway add two domestic debit schemes on top.

Can American Express be on the same contract and payout as other methods?

On some platforms, yes; on many, Amex is a separate agreement with a separate settlement. Surfboard Payments accepts American Express on every channel in every market it acquires, on the same merchant contract and in the same payout as Visa, Mastercard, Swish, Vipps, MobilePay and the rest. Ask each provider the question directly.

Does Swish support subscriptions?

Yes, through Swish Återkommande betalningar, where the customer approves a recurring agreement with BankID in the Swish app. It is offered bank by bank and requires a Swish API connection, so support varies by payment platform. Confirm it explicitly with any provider you evaluate.

What is the difference between a unified payment platform and a payment bundle?

A bundle puts terminals, acquiring and checkout on one contract and one invoice. A unified platform puts them on one API, one customer token and one merchant record, and adds every payment method to the same contract and payout. Bundles simplify purchasing. Unified platforms simplify engineering, onboarding and the customer experience across channels.

What settlement speed should Nordic merchants expect?

Next bank day is the norm from Nordic acquirers such as Swedbank Pay. Adyen typically pays out with a two-business-day delay. Zettle credits a PayPal business account within minutes, with one to two more days to reach a bank account. Ask each platform for its payout schedule per country, per method and per currency in writing.