Cards Miss Over Half of Eurozone Online Payments: Meet the SaaS Payment Solutions That Don’t

Online payments already make up 21% of consumers’ day-to-day transactions in the euro area and 36% of their value. Yet cards cover only 48% of online purchases, while payment wallets and mobile apps take a further 29%. For a SaaS company that bills in one currency through one acquirer (the provider that processes its card payments), each new European market quietly costs conversion, margin and finance-team hours. This guide maps the journey from that starting point to mature SaaS payment solutions: which payment rails (the networks that actually move the money) a scaling business needs and in what order to add them.

‍

Key Takeaways

• A single-currency, card-only setup works at home but loses conversion abroad, because every European market reads checkout through its own currency, payment habits and banking rules.
• Consumers and businesses pay differently: B2C buyers expect local methods such as wallets and mobile apps, while finance teams at larger customers expect an invoice they can pay by bank transfer.
• A multi-rail stack combines cards for self-serve plans, SEPA and SEPA Instant for euro invoices, refunds and payouts, and SWIFT for clients and contractors outside the SEPA area.
• Holding revenue in a multi-currency account removes the double conversion margin, and virtual IBANs with a single statement across rails turn month-end reconciliation into a review of exceptions.
• Few SaaS businesses need the full stack on day one: adding each rail when a clear trigger appears, from the first foreign revenue to declines clustering by country, keeps cost in line with growth.

‍

Why Does a Single-Currency Setup Stop Working for Global Business Payments?

Imagine a Berlin-based HR SaaS with prices only in euros and card-only checkout, expanding into Poland, Sweden and the UK. Polish buyers see a zloty figure that includes their own bank’s FX markup, and Swedish procurement teams ask for an invoice they can pay by transfer. British customers on annual plans, meanwhile, hit card limits that were never designed for five-figure invoices.

‍

None of these problems shows up in domestic reporting, because the model works at home. The reason is simple: every market reads the same checkout through its own currency, its own habits and its own banking rules.

‍

What Do European SaaS Customers Expect at Checkout and on the Invoice?

Consumer and business buyers expect very different things. In B2C, payment habits are local: e-payment solutions such as payment wallets and mobile apps accounted for 76% of online purchases in the Netherlands and 46% in Germany, while cards led in most other euro-area countries. A checkout that ignores this mix loses buyers it never sees. Choosing between digital payment solutions is therefore a country-by-country decision rather than a single integration.

‍

In B2B the pattern differs again: finance teams at mid-market and enterprise customers expect an invoice they can pay by bank transfer in their own currency. Bank transfers already carry most of the money in Europe: credit transfers accounted for 92% of the value of non-cash payments in the euro area in the second half of 2025.

‍

Consider an annual-plan SaaS closing a Dutch mid-market account: the deal stalls until procurement can pay a euro invoice by SEPA transfer. International business payments by invoice are the default in European enterprise buying, and card-only billing shuts a SaaS out of them.

‍

The Barriers That Slow SaaS Expansion in Europe

None of the barriers below is exotic: each is a specific point where a payment setup built for one market starts to strain under several. These seven appear most often when SaaS companies expand across Europe, and a business can plan for every one of them in advance.

‍

Payment Methods Fragment by Country

A card-first setup that converts well in France underperforms in markets where buyers default to local schemes. A provider or international payment gateway covering only cards leaves those markets half-served. The symptom is easy to miss: a SaaS sees its Dutch trial conversion lag its French one, for reasons that have nothing to do with the product.

‍

Non-Euro Currencies Add a Cost to Every Transaction

Poland, Sweden, Czechia, Hungary, Denmark, Switzerland and the UK all use currencies other than the euro. Each payment in PLN, SEK or GBP gets converted on the way in and often again on the way out, and both conversions take a cut. FX payment solutions exist to stop revenue losing a conversion margin twice.

‍

Cards Issued Outside the EEA Cost More

Interchange is the fee a merchant’s provider pays to the cardholder’s bank on every card transaction. Since Brexit, UK-issued cards paying EEA merchants count as inter-regional, and card-not-present interchange on these payments rose more than fivefold. Consumer debit went from 0.2% to 1.15% and consumer credit from 0.3% to 1.5%.

‍

The UK regulator plans to cap these fees, and in January 2026 the High Court confirmed its power to do so. The level and start date of the cap are still undecided, so until it takes effect, a SaaS with a growing British subscriber base pays the higher fee on every renewal.

‍

PSD2 Authentication Shapes Subscription Billing

Strong Customer Authentication (SCA) is the two-factor approval PSD2 requires for electronic payments. The first charge of a subscription needs it. Later renewals run as merchant-initiated transactions: charges the merchant triggers under a mandate the customer approved at the start. Once that mandate has been authenticated, these renewals sit outside SCA. For a Cologne-based SaaS whose trials convert to paid plans, getting the first authenticated charge right decides whether later renewals can run without asking the customer to approve each one.

‍

VAT OSS Adds a Reporting Layer for B2C

Once a SaaS sells more than €10,000 a year in digital services to consumers in other EU countries, it charges VAT at each customer’s local rate. The optional One Stop Shop lets it declare that VAT through a single registration. VAT is context here rather than a payment problem, and handling tax is a separate workstream from choosing payment rails.

‍

Onboarding Takes Longer for Young Cross-Border Businesses

Consider a two-year-old SaaS registered in Estonia with founders spread across two countries. Every regulated provider has to verify ownership, source of funds and business model before opening an account, and a cross-border structure gives it more to check. A company that prepares these documents in advance and knows what a compliance team will ask moves through the review faster and keeps its expansion timeline intact.

‍

Receipts From Several Rails Resist Matching

Once card payouts, SEPA credits and SWIFT transfers arrive through different channels with different references, matching them to invoices becomes manual work. This barrier gets its own chapter below, because it grows with every rail added.

‍

What Multi-Rail Means: Cards, SEPA, SEPA Instant Payments and SWIFT Side by Side

A multi-rail stack runs each payment over whichever network fits it best. Four rails cover the European SaaS map:

‍

‍

The instant rail is becoming standard. Euro-area banks had to be able to receive instant euro payments by 9 January 2025 and send them by 9 October 2025, while payment and e-money institutions follow by 9 April 2027. An instant transfer can cost no more than a standard one, and instant transfers already made up 25% of all credit transfers by number in the second half of 2025.

‍

With no price premium, SEPA Instant payments suit refunds, payouts and supplier payments even before customers ask for them. Cards reach the business through an international payment gateway, while SEPA, SEPA Instant and SWIFT come through accounts. A capable provider should therefore give access to both rather than force a choice between them.

‍

Payment Orchestration: Routing Each Card Payment to the Right Acquirer

Payment orchestration is a layer above acquirers that sends each transaction to the provider most likely to approve it and cascades to another when the first declines. It starts paying for itself when a SaaS works with several acquirers or sees declines cluster by country.

‍

Take a Lyon-based SaaS that notices Spanish-issued cards fail far more often than French ones. Routing those transactions through a local Spanish acquirer recovers a share of them without any change to pricing or product. Well-built integrated payment solutions combine orchestration with acquiring and accounts, so orchestration becomes a routing decision rather than a separate vendor relationship.

‍

COLIBRIX ONE plays its part at the acquiring and account level, connecting to orchestration partners rather than replacing them.

‍

Holding Revenue in a Multi-Currency Business Account Instead of Converting It

Another example is a SaaS earning dollars from American customers while paying cloud infrastructure and US contractors in the same currency. Converting every receipt to euros and back again for every outgoing payment costs the business two conversion margins. A multi-currency account ends that cycle by letting revenue stay in the currency it arrived in until the business spends it in that same currency.

‍

Open your multi-currency account →

‍

This is where FX payment solutions stop being a pricing detail and become a margin decision: conversion happens when the business chooses, at a rate it can see.

‍

Payment Reconciliation: Keeping the Books Straight Across Rails

Reconciliation means matching every incoming and outgoing payment to its invoice and ledger entry. Picture the finance team at a Milan-based SaaS closing the month with hundreds of SEPA credits that carry no usable reference: someone has to guess which customer each one belongs to.

‍

Dedicated account details change the mechanics. A virtual IBAN gives each customer or invoice its own account number, routed into one master account, so incoming transfers identify themselves. Combined with a single statement across rails, reconciliation shrinks from days of detective work to a review of exceptions.

‍

A Staged Roadmap for Scaling SaaS Payment Solutions Across Europe

Few companies need the full stack on day one, and adding each rail when a clear trigger appears keeps cost and complexity in line with revenue. The four stages below follow the order in which SaaS businesses usually grow into their payments, each with its own trigger for moving to the next.

‍

Stage 1: one currency, one acquirer, domestic sales only. The trigger to move on is the first meaningful revenue from abroad.

‍

Stage 2: local-currency pricing and a multi-currency account. The trigger is FX complaints or a visible conversion drop in new markets, as in the Berlin example above.

‍

Stage 3: bank rails for B2B. Adding SEPA, SEPA Instant and SWIFT unlocks invoice-paid enterprise deals, as in the Dutch procurement scenario. The trigger is the first buyer who asks to pay by transfer.

‍

Stage 4: orchestration and unified reconciliation. The trigger is declines clustering by country or a month-end close that keeps getting longer.

‍

Each stage builds on the previous one, and mature SaaS payment solutions are this sequence completed: every market served by its own rail, every payment visible in one place.

‍

How COLIBRIX ONE Supports SaaS Businesses Scaling Across Europe

COLIBRIX ONE brings the pieces together under one provider: business accounts, local and cross-border transfers and card acquiring for subscription billing. A SaaS receives a dedicated IBAN in its company name, SEPA Instant for time-sensitive euro payments, recurring card charging for self-serve plans and FX pricing that is visible before money moves. The difference lies in service rather than in tariff tables: every client works with a personal manager and a technical support team who help at each stage of the roadmap above.

‍

Get universal payment stack →

‍

If your payment setup was built for one market and your roadmap was not, discuss your payment scheme with a COLIBRIX ONE manager.