Powstania Warszawskiego 15
31-539 Kraków
Payments in Switzerland
Every Swiss household knows the QR bill: it is how invoices have been paid since the old payment slips were retired in 2022. For apps that sell events, memberships or services in Switzerland, it can be a simpler alternative to a card checkout. This guide explains how a QR bill flow works in an app, what it needs on the backend, and when it is the right choice.
To use the Swiss QR bill in a mobile app, the backend generates a bill with the amount, the creditor account and a unique reference, sends it as a PDF by email or shows it in the app, and the user pays it by scanning the QR code in their banking app. The payment is then matched to the purchase by its reference, automatically from bank statement files or manually. It suits events booked ahead, memberships and invoices, where instant confirmation is not required.
Key takeaways for Swiss founders and product owners
The QR bill is the standard Swiss payment slip, introduced in 2020 and the only format since the orange and red slips were withdrawn in autumn 2022. The payment part carries the Swiss QR code, marked with the Swiss cross, which contains everything the bank needs: the creditor account, the amount in CHF or EUR, and a reference for the payment.
The format follows the Swiss implementation guidelines published by SIX, so any compliant bill can be paid in any Swiss banking app, by scanning the code or by uploading the PDF in e-banking.
From the user's side it takes a few taps. Behind them sit five steps that the product and the backend have to design together.
A member signs up for an event, renews a membership or confirms an order. The app records it as waiting for payment.
The backend creates a bill with the amount, the creditor account and a unique reference for this purchase, and renders it as a PDF with the Swiss QR code.
The PDF goes out by email or is shown in the app. No card details and no payment provider SDK touch the app.
The member scans the QR code in their banking app, which fills in the account, amount and reference, and confirms the payment.
When the money arrives, it is matched to the purchase by its reference, either automatically from the bank statement files or manually by the team, and the app marks it as paid.
The QR bill moves the payment out of the app and into the user's banking app. The product work is in what happens before and after.
This is general guidance, not payments or legal advice. The bank that holds the account is the best source for the exact setup of QR IBANs and statement files.
The QR bill is not a replacement for every payment method. It fits some purchases very well and others poorly.
Many Swiss products combine them: a QR bill for events and memberships booked ahead, and TWINT or cards where the user needs access immediately. Real world services such as events can usually be sold outside Apple and Google in app purchase; our guide to in app purchase fees explains where the line runs.
For Souly, a social networking app for a Zurich community, we built event payments around the QR bill. Members sign up for an event in the app, a QR bill arrives by email, and they pay it in the banking app they already use for invoices.
The Souly case study shows the product, and our guide to building an app for the Swiss market covers languages, formats and data protection around it.
About the source
Yes. The backend generates a QR bill with the amount, the creditor account and a reference, sends it to the user by email or in the app, and the user pays it in their banking app. The payment is then matched to the purchase by its reference.
No. The money arrives with the bank transfer, so the app needs a waiting state between purchase and confirmed payment. For instant access, TWINT or card payments fit better.
Only if you want to use the QR reference. A standard IBAN works with an international creditor reference or without a reference. Your bank can advise which setup fits your reconciliation.
By the reference on each bill. Swiss banks provide statement files in the ISO 20022 format listing incoming payments with their references, which a system can read to mark orders as paid. A small first version can confirm payments manually.
It depends on what is sold. QR bills suit events booked ahead, memberships and invoices; TWINT and cards suit purchases that need instant confirmation. Many products combine them. Our page on app development for Swiss companies covers how we work with clients in Switzerland.
Real world services, such as events held in person, can usually be sold outside Apple and Google in app purchase. Digital content used inside the app follows different store rules.
Thomas sets the company's long term strategy and direction, identifies market opportunities, and owns business development and client acquisition. He builds strategic partnerships that last beyond a single project. He works with clients from the first strategy conversation, so their business goals, not just their feature list, drive every decision.
We work on Central European Time, the same as Zurich, and have built Swiss QR bill payments into a live product. Tell us about yours and we will give you a fixed price.
30 minutes, no preparation needed.