Most payment integrations we are asked to review work. They accept money, they reconcile, and the finance team has stopped complaining. They are also, quite often, about to be rebuilt, not because the code is bad, but because a decision taken in the first week made the second year expensive.
The decisions that matter are not technical. They are about who holds the money, who holds the customer relationship, which methods your customers actually use, and what happens the first time a payment fails in a way nobody planned for.
This article is for the person who owns that decision in a company of 10 to 200 people: the finance lead of a 60-person distributor moving to online ordering, the founder of a 25-person webshop, the CTO of a 12-person platform that collects money for others.
Who is actually holding the money?
Between a customer paying and the money reaching your account, someone holds it. In a plain card or invoice setup for your own goods, that is the acquirer or the banks, briefly. In a marketplace or platform that collects on behalf of others and pays them later, it may be you, and holding third-party funds is a regulated activity in Switzerland that changes your obligations and your architecture.
The distinction is in the detail of the rules. The Banking Ordinance does not treat money received as payment for your own goods or services as a deposit. It also excludes non-interest-bearing client balances that serve only to settle client transactions at asset managers and similar companies, provided settlement happens within 60 days. Whether a particular platform fits that exception is a legal question, not a design one, and the answer depends on how long you hold funds, whose they are and what discretion you have over them.
Two further rules sit behind it. Article 2 of the Anti-Money Laundering Act treats anyone providing services related to payment transactions on a professional basis as a financial intermediary, and Article 14 requires such intermediaries to join a self-regulatory organisation. If you do hold deposits, the Banking Ordinance sandbox allows up to one million francs under strict disclosure conditions, and FINMA's FinTech licence covers up to one hundred million francs, provided the deposits are neither invested nor interest-bearing.
Companies that discover this in year two rarely discover it gently: a bank asks during an account review, or an investor's counsel asks during diligence. The cheaper path for a platform is usually to let a licensed payment provider hold the funds and split payouts, so that the money never sits on your balance sheet. That choice shapes everything downstream, which is why it comes first. How a regulatory status then shapes what a young financial company may say publicly is covered in positioning a new fintech brand in Switzerland.
How do people in Switzerland actually pay in 2025?
In person, mostly by debit card, with cash still close behind. In its 2025 payment diary the Swiss National Bank found debit cards in 37 percent of in-person transactions, cash in 30 percent, mobile payment apps in 17 percent and credit cards in 13 percent. Online and in apps the order changes: mobile payment apps are the most frequent remote method, and invoices are mostly paid through online banking.
The SNB survey puts mobile payment apps at 32 percent of remote transactions in 2025, ahead of credit cards, online banking and debit cards. The SNB notes that a change to its diary recorded fewer invoice payments than the year before, so the online banking share is understated. Read it as an order of magnitude, not a precise split.
Three conclusions follow. A consumer webshop that offers cards but not the dominant Swiss mobile payment app is turning away the method behind roughly a third of remote payments. A shop or practice with a counter still needs a cash plan, because almost a third of in-person payments are cash. And a B2B seller should not expect cards to replace invoices: the SNB's survey of companies found that companies make their own payments mostly against invoice and by transfer.
The card market itself is concentrated. In an April 2026 speech, two members of the SNB's management named Mastercard, PostFinance, TWINT and Visa as the networks that dominate in Switzerland, and noted that a card payment is complete for the customer and merchant at once, while the money usually moves between banks a day later.
What does the QR-bill actually change?
It made structured payment references the default for invoices. The QR-bill replaced the old Swiss payment slips in October 2022, and when an invoice carries a QR reference, the incoming payment tells your system exactly which invoice was paid. That makes reconciliation automatic, but only if your invoice numbering and accounting system were set up to generate and read those references from the start.
According to SIX, which operates Swiss payment infrastructure, the QR reference exists for simple reconciliation of invoices with incoming payments and may only be used with a QR-IBAN issued by your principal bank. For payments in euros or from abroad, the international Structured Creditor Reference does the same job with a normal IBAN. Choose one deliberately. A QR-bill with no reference at all is permitted, and it puts you back to matching amounts to names by hand.
The specification also moves. SIX's QR-bill standards page records that the QR-bill has been in circulation since June 2020, replaced payment slips on 1 October 2022, and that version 2.3 of the implementation guidelines, in force since 22 November 2025, introduced the structured address and an extended character set. If your invoicing software was configured years ago and never updated, check it against the current version.
Without a structured reference, someone matches amounts to names, costs more every year and is wrong more often than anyone admits. Read the specification before designing invoice numbering, because the numbering has to fit it. If you are about to replace accounting or ERP software anyway, this is the moment to get it right, which is one of the arguments in when a small company actually needs an ERP.
Cards, bank transfer, or both?
For most Swiss SMEs selling to other businesses, transfer against a QR-bill invoice remains the dominant method and cards are a convenience. For consumer-facing businesses the balance reverses. The mistake is building for one and bolting on the other later, because the two have different failure modes, different costs and different reconciliation paths, and each needs its own owner in finance.
| Card or wallet | Bank transfer with QR-bill | Instant payment | |
|---|---|---|---|
| Settlement to you | Typically one to a few days, net of fees | When the customer decides to pay | Within seconds, around the clock |
| Cost | Percentage or fee per transaction | Low per transaction | Depends on your bank |
| Failure mode | Declined at the moment of sale | Silent: nothing arrives | Rejected at initiation |
| Reconciliation | Provider file, mostly automatic | Structured reference, or manual | Same references as transfers |
| Chargeback risk | Real, and yours to manage | None in the card sense | None in the card sense |
| Fits | Consumer, low value, high volume | B2B, higher value, invoiced | Urgent or time-critical B2B |
The row that surprises people is the failure mode. A declined card is loud: the customer sees it and usually tries again. A transfer that never arrives is silent, and a silent failure is only found by whoever is watching the ledger. If nobody watches the ledger daily, build that before you build anything else.
Instant payments are the new column. They allow account-to-account transfers within seconds at any hour, as the SNB speech describes, but they are not yet possible at the cash register, and the SNB's survey of companies found that only 12 percent of companies used them in spring 2025. Most non-users said their suppliers had no need for them yet. Treat them as an option to accept, not a reason to redesign.
What does a payment setup really cost a small company?
More than the transaction fee. The fee is the visible line, but reconciliation time, terminal and outage handling, chargebacks and the cost of switching providers often matter as much for a company of 10 to 200 people. Compare providers on the total over a year of your real transaction mix, not on the headline percentage.
Merchants feel the fees. In the SNB's 2025 survey of companies, one third of companies accepting cashless payments at terminals said they were not satisfied with their payment service provider, and 74 percent of those named high costs as the reason. Around three quarters of companies perceived cash as cheaper per transaction than cards or mobile payment apps, and credit cards were seen as the most expensive method at the point of sale.
You also cannot easily pass the cost on. The April 2026 SNB speech notes that Swiss acquirers generally oblige retailers by contract to offer all cashless methods at the same price, so the fee is a margin decision, not a surcharge. That is why reconciliation time matters: in the companies we work with, it is the cost line most often missing from the provider comparison, and the one a structured reference or a clean payout file removes.
Where the integrations actually break
Four patterns account for most of the rebuilds and incidents we see.
The provider became the system of record. Refunds, partial payments and credit notes were handled in the provider's dashboard because it was quicker, so the truth about what a customer owes now lives outside your own systems. Migrating away means reconstructing history from an export.
Currency was treated as a formatting problem. CHF, EUR and the occasional USD were stored in one column with a currency field added later. Every report since has needed a caveat.
Nobody modelled the reversal. The happy path was built well; the refund, the partial refund, the refund after a partial payment and the chargeback were added one at a time under pressure. This is the same failure we describe in ERP data migration: the exceptions are the system, and treating them as edge cases is what makes them expensive.
Nobody planned the outage. Around 40 percent of companies in the SNB survey experienced at least one technical disruption a year with cashless payments, most often the terminal or the internet connection. In a disruption, 55 percent switched to cash and 45 percent let customers pay later. Decide which you will do before the terminal goes dark on a Saturday.
Card data adds one more obligation. The PCI Security Standards Council states that its data security standard applies to all merchants regardless of size or transaction volume, and that the payment brands decide whether a small merchant must validate compliance; your acquirer tells you how. The practical lesson is to keep card numbers off your own systems entirely by using the provider's hosted fields or payment page, which also keeps the rest of your security programme manageable. The broader baseline is in cybersecurity priorities for Swiss SMEs, and the customer data in your payment records falls under the revised FADP like any other.
What changes between 10 and 200 people?
The payment questions stay the same; what changes is who answers them and how much a wrong answer costs. A 10-person company can run payments from one provider account and an accounting package if one person checks unmatched payments daily. At 200 people the same mistakes are multiplied across channels, currencies and entities, and need an owner, a written process and integration with the ERP.
At 10 to 30 people, keep it to one acquirer or payment provider, QR-bill invoices with references, and a weekly review of payouts against sales. At 50 to 100 people, add a second channel only when the volume justifies it, and make the accounting system, not the provider dashboard, the record of what customers owe. At 150 to 200 people, payments usually become part of a wider systems decision, and the questions in how to measure ROI before you fund it apply to the business case.
A worked example. Take a 30-person online retailer selling to consumers and to small businesses. Consumers pay by card or mobile app at checkout; businesses pay against a QR-bill invoice with a QR reference. One person in finance owns a daily list of unmatched transfers and payouts that do not net to sales. Refunds are issued from the accounting system, which pushes them to the provider, never the other way round. None of it is clever; all of it was decided before choosing the provider.
What to do before choosing a provider
Write down, on one page: who holds the funds and for how long; which methods and currencies you will accept in the next three years; what a refund, a partial payment and a chargeback do to your ledger; what happens in an outage; and who looks at unmatched payments, daily, by name. That page is worth more than a provider comparison, because it is what makes a provider comparison answerable.
Our fintech practice starts these engagements by modelling money movement end to end, including every reversal, before discussing providers. The model usually eliminates half the shortlist on its own. For firms in financial services there is a further step: confirm early whether your model brings you into supervisory scope, because that answer changes the architecture rather than the vendor. For a retail or consumer-goods business, the same page usually settles the checkout question in an afternoon. The cost of asking is a conversation. The cost of not asking is discovering it during diligence.
Sources
- Swiss National Bank — Payment Methods Survey of Private Individuals in Switzerland 2025, in-person and remote volume shares by payment method
- Swiss National Bank — Payment Methods Survey of Companies 2025, provider satisfaction, disruptions, instant payments
- Swiss National Bank — Swipe, scan, tap: the cashless payments market, speech of 16 April 2026
- SIX — QR-bill: the digitalisation of invoicing, QR reference, QR-IBAN and SCOR
- SIX — QR-bill standards, introduction dates and implementation guidelines
- FINMA — FinTech licence, deposits up to CHF 100 million
- Fedlex — Banking Ordinance, SR 952.02, Art. 5 on what counts as a deposit and Art. 6 on the sandbox, German text
- Fedlex — Anti-Money Laundering Act, SR 955.0, Art. 2 para. 3 and Art. 14
- PCI Security Standards Council — Merchant resources, PCI DSS scope and validation for merchants
Related reading
- How does a new fintech brand get taken seriously in Switzerland?
- ERP data migration: the part that overruns, and why
- The revised FADP: what Swiss companies actually have to do
- Cybersecurity for Swiss SMEs: the five things that actually matter
- Fintech consulting
Working on this right now?
Tell us where you are in two questions. A consulting partner reviews every enquiry within 2 business days.