Twint payments
Twint integration allows cross-border merchants to capture the Swiss retail market by connecting checkouts to Switzerland's dominant mobile application. The Cardflo platform routes Twint payments through regulated acquirer partners, managing QR generation and CHF settlement logic.
- Category
- Methods
- Capabilities
- 6
- Available on
- All plans
Cross-border retailers entering the Swiss market encounter a consumer base heavily reliant on a specific domestic application for daily transactions. Integrating this method requires managing unique numeric token exchanges and dynamic imaging sequences, rather than processing standard card details. Merchants must handle fast authentication timeouts while pricing and clearing entirely in Swiss francs.
Cardflo orchestrates the technical connection to the Swiss mobile infrastructure, enabling merchants to process Twint payments alongside international methods. The gateway handles the necessary redirection logic for mobile browsers and generates the required imaging for desktop displays. Finance teams receive consolidated reporting that reconciles domestic CHF volume with broader European traffic.
Twint transactions are processed in real-time with immediate confirmation through Cardflo's network of Swiss acquirer partners, ensuring efficient handling of payments. This integration provides a robust solution for merchants looking to expand their presence in the Swiss market using a favoured local method.
Twint payments overview
Expanding e-commerce operations into Switzerland demands native connectivity to the country's central payment infrastructure. Consumers expect to scan desktop screens or approve mobile prompts using their domestic bank-linked application.
Cardflo provides the necessary gateway orchestration to facilitate this interaction, routing authorisation requests and capturing confirmed transactions without requiring merchants to maintain local banking infrastructure. The platform standardises the implementation of Swiss app connectivity, normalising the data flow for reconciliation purposes and ensuring predictable settlement timelines in CHF.
While operators handling pan-European volume might route standard clearing through SEPA payments, capturing the distinct Swiss retail segment relies on processing the native mobile token.
By placing merchants with regulated acquirer partners capable of handling this specific traffic, Cardflo ensures checkout pages remain relevant to local buyers, converting cross-border traffic into settled revenue through familiar domestic interfaces.
How twint payments works
Displaying the payment prompt
The orchestration layer detects the customer device and determines the appropriate interaction method. For desktop users, the gateway generates a unique graphic that the user scans using their smartphone. For mobile shoppers, the system uses deep linking to open the domestic banking application directly, passing the transaction value and merchant identifier through the secure API payload.
Capturing the user authorisation
Customers review the purchase amount within their familiar local interface and confirm the transaction using biometric authentication or a personal identification number. The Swiss network verifies the available funds directly against the linked bank account or stored card token, placing an immediate hold on the requested balance to guarantee the merchant against default or insufficient funds.
Routing the final settlement
Upon receiving the network's authorisation confirmation, Cardflo triggers the checkout success state and updates the backend order management system. The transaction clearing instructions move through the designated acquirer partner, resulting in predictable, batched deposits in Swiss francs. Finance teams access detailed ledger reports that isolate these specific domestic transfers from broader international payment flows.
Why twint payments matters
Capturing Swiss market share
Penetrating the lucrative Swiss e-commerce landscape requires offering the exact interface consumers trust for daily purchasing. Relying solely on international credit networks artificially limits conversion rates among local buyers who prefer direct application approvals. Integrating the dominant domestic method ensures cross-border retailers look and function like native entities, directly increasing checkout completion metrics.
Reducing cross-border friction
Standardising the technical connection to regional networks removes the complexity of managing distinct integration paths for specific countries. The orchestration platform normalises the unique token exchanges and authentication webhooks into a unified transaction format. This allows scaling merchants to accept Twint Switzerland volume without committing engineering resources to build and maintain bespoke local integrations.
Regulatory notes for twint payments
Swiss data protection and authentication compliance
Transactions flowing through the domestic Swiss infrastructure must comply with the Federal Act on Data Protection, which dictates strict controls over consumer financial information.
By routing checkouts via application redirection, merchants ensure the sensitive authentication credentials remain entirely within the regulated banking environment, reducing the retailer's own compliance burden.
The underlying network enforces strong customer authentication natively through the application interface, typically requiring biometric verification or secure passcodes. This architecture shifts the primary liability for fraudulent capture away from the merchant, provided the gateway passes the correct initial transaction payload to the regional API.
Regional settlement and banking requirements
Operating cross-border commerce into Switzerland has to be built around regional clearing protocols. Acquirer partners facilitating these domestic application payments enforce specific merchant category code restrictions and maintain distinct underwriting criteria tailored to the Swiss financial ecosystem.
Retailers must pass accurate corporate registration details during the gateway onboarding phase.
Additionally, managing native volume demands careful attention to local refund regulations and consumer rights frameworks.
The payment orchestration layer maintains the necessary transaction ledger and metadata to support dispute resolution queries, ensuring merchants can present compelling evidence to the clearing network if a customer questions an application-approved capture.
Twint payments use cases
Swiss fashion QR checkout
Fashion retailers entering Zurich and Geneva need Twint QR code scanning at checkout, where Swiss shoppers expect to approve CHF purchases in the Twint app rather than enter card details. Cardflo configures the payment handoff, routes the transaction through the appropriate acquirer partner pathway and reports the resulting CHF settlement.
Twint for Swiss digital services
Online retailers serving Swiss mobile shoppers need checkout redirection into the Twint app, followed by a reliable return to the merchant’s order confirmation page. Cardflo orchestrates the redirect and callback workflow, maps payment status to the order record and routes confirmed Twint transactions through its acquirer partner network.
Swiss travel bookings with Twint
Cross-border retailers offering Swiss click and collect must confirm a Twint payment before reserving stock at a local collection point, while keeping refunds aligned with cancelled or uncollected orders. Cardflo connects payment status to the fulfilment workflow, supports refund messaging and provides reconciliation records for finance and store teams.
Twint at Swiss tills
Retailers operating temporary or permanent Swiss shops need till-generated Twint QR codes that customers can scan and approve without slowing the queue. Cardflo supports the QR payment flow, relays confirmation to the POS, routes transactions through its acquirer partner network and separates store-level CHF activity for reconciliation.
Twint payments by the numbers
This reflects the typical number of active users within the Swiss domestic market, where a large majority of the adult population utilises mobile banking integrations for daily commerce.
Typical range for authenticated mobile wallet transactions in Switzerland, as the direct bank link reduces declines associated with credit limits or card expiry issues.
Industry-standard time for the communication between the mobile app, the clearing system, and the merchant gateway to confirm a successful authorisation.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Twint payments
- Automatic generation of dynamic desktop images for Twint QR code checkout scanning and rapid authentication.
- Mobile browser redirection flows that push consumers directly into the domestic app environment for approval.
- Intelligent routing algorithms that direct Swiss volume to acquirer partners with dedicated regional processing connectivity.
- Native handling of CHF settlement routing to ensure merchants avoid unnecessary cross-border currency conversion fees.
- Consolidated gateway reporting that standardises Swiss domestic transactions alongside traditional card and bank transfer volumes.
- Real-time webhook notifications confirming captured funds immediately after the customer authorises the prompt via fingerprint.
A short scoping call, then a written plan for your MIDs.
Questions about Twint payments
How does the gateway handle desktop versus mobile checkout flows?
The orchestration platform relies on device fingerprinting during the checkout session to trigger the correct sequence. When the system detects a desktop browser, it requests a dynamic graphic from the Swiss network API and displays it on the merchant site.
The user must physically scan this image with their smartphone. Conversely, when the session originates on a mobile device, the gateway constructs a deep link payload that automatically forces the local application to open, bringing the payment confirmation screen directly to the foreground.
Can merchants refund transactions processed through this regional network?
Retailers can initiate full or partial refunds directly through the Cardflo control panel or via API, matching the capability of standard international networks.
The orchestration layer routes the refund instruction back through the original acquirer partner, referencing the unique transaction identifier generated during the initial capture. The Swiss infrastructure then credits the funds back to the user's linked bank account or underlying funding source.
Merchants must ensure their current CHF clearing balance holds sufficient funds to cover the outbound refund request before initiation.
Does this method support recurring billing or subscriptions?
The integration supports initial capture and subsequent merchant-initiated transactions for recurring models. During the primary checkout, the consumer authorises a continuous payment mandate within their domestic application environment.
The gateway securely stores the resulting token, allowing operators to trigger future billing cycles automatically without requiring the customer to scan a new image or manually approve a prompt.
This architecture ensures subscription businesses can maintain reliable billing schedules for Swiss cohorts without causing repeated authentication friction.
How does Twint merchant routing impact foreign exchange rates?
Processing domestic Swiss traffic natively allows merchants to bypass traditional global scheme interchange and automated currency conversion fees. Cardflo configures the routing rules to direct the transaction through acquirer partners that support direct clearing in Swiss francs.
This architecture ensures the merchant receives the exact settled amount in CHF, allowing treasury teams to manage their own foreign exchange strategies and repatriation schedules rather than accepting unfavourable spot rates applied automatically by international processing networks.
Related guides.
See how Cardflo compares.
From the blog
A merchant acquirer is a licensed bank that holds your account, takes liability for transactions, and settles funds. The payment processor is the technology layer routing data between the checkout, card networks, and issuing banks. Every card payment requires both components to manage technical encryption and financial liability. They are often separate entities with distinct fee structures.
Read articleA merchant acquirer is a financial institution that processes card transactions and verifies funds. The payment gateway acts as the technological bridge, encrypting sensitive data between the website and the acquirer. Merchants need both components to ensure that electronic payments are accepted, authorised, and settled. Together, they create a seamless and secure payment experience for customers.
Read articleA merchant account is a specialised business account used to accept electronic payments like Apple Pay and Google Pay. It acts as a bridge between the business and the customer bank. Funds are held here for verification and compliance before being transferred to a main bank account. This process ensures that all transactions are secure and reduces the risk of fraud for the merchant and the customer.
Read articleReady to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.