Nothing is easier than using TWINT, and now it’s available for Swiss QR bills too.

With TWINT invoice, your customers can pay QR bills quickly, securely and easily with the TWINT app, anytime and anywhere. Activate TWINT for your Swiss QR bills and discover the benefits.

Enjoy faster incoming payments via Switzerland’s most popular payment app with 6 million active users.

Create QR bills as before and send them by post or e-mail. There’s no need to change anything.

You can also easily convert any QR bill into an HTML button or payment link. This means all the invoice details will be embedded in a button or link. You can find detailed instructions on how to do this here.

Customers scan the invoice with TWINT, select the execution date and confirm the payment. The invoice amount will be transferred to the account you have saved in TWINT on the execution date.

Please note that TWINT collects invoice amounts on a daily basis and transfers the amount as a net collective payment (invoice amount minus the TWINT fee).

As soon as the transfer is made to your bank account, you can check the payment confirmation for all invoices in two ways:

• TWINT Business Portal
• SFTP (camt.054 file), on request

You can upload the reports to your accounting software if you need to.

You can find the fee per completed transaction in our price sheet.

The TWINT fee will be deducted directly from the invoice amount when payment is made.

TWINT may only be used to collect payment for Swiss QR bills after goods or services have been delivered or provided to the consumer. You can find a detailed explanation here.

Your QR bill must be marked accordingly to make customers aware of the TWINT payment option. You can find detailed instructions in our design guidelines.

This diagram illustrates the payment process for a TWINT invoice across all parties involved (customers, merchants, the TWINT scheme and the acquirer) and the chronological sequence of how the money is transferred (processed on T+2).

The money flow takes place in three consecutive steps:

1. From the customer’s bank to the TWINT scheme bank account (T)
2. From the TWINT scheme bank account to the TWINT acquirer bank account (T+1)
3. From the TWINT acquirer bank account to the merchant or CSP bank account (T+2)

The amount will be credited to the merchant account two working days after the payment instruction (T+2).

Step 0: receipt of invoice and confirmation of payment

• The customer receives a Swiss QR bill – from a merchant or utility company, for example – via post, e-mail or a digital customer portal
• The customer scans the QR code using the TWINT app or taps on the payment link, selects the execution date and confirms the payment

Step 1: payment execution in the TWINT scheme (T)

• The amount is transferred from the customer’s bank to the TWINT scheme bank account
• The scheduled payment is executed in the TWINT scheme

Step 2: payment and provision of data (T+1)

• The amount flows from the TWINT scheme bank account to the TWINT acquirer bank account
• The payment is executed and transmitted to the payment bank
• The camt.054 file is generated and made available to the merchant or CSP

Step 3: credit to merchant account (T+2)

• The bank transfer to the merchant or CSP account is executed
• The invoice amount (minus the TWINT fee; net) is credited to the merchant bank account

Swiss QR bills do not need to be modified or expanded to be used with TWINT invoice. Billers can continue to use their existing invoicing and ERP processes as they are.

Technical implementation is limited to the registration and activation of the biller for TWINT invoice. As part of the onboarding process, the relevant account details (IBAN or QR IBAN) are stored with TWINT. Once activation is complete, existing Swiss QR bills can be recognised and paid via all TWINT apps.

Unlike QR bills, integrating online buttons requires a degree of technical implementation on the part of the biller. This involves generating a TWINT payment link using the QR bill data and embedding it in e-mails, customer portals or apps via a button or link.

The payment link forms the technical basis of the integration process. The online button visually displays this payment link and enables the user to initiate the payment process in the TWINT app.

A payment link is used to initiate a TWINT payment. It contains all the relevant invoice information for a Swiss QR bill and is processed by the TWINT app.

Online button

The online button is a visual representation of the payment link (paylink) and enables the user to initiate the payment process via TWINT. Technically, the button links to the same payment link, which can also be used directly.

The online button is particularly suitable for integration into

• customer portals;
• mobile applications;
• HTML e-mails; and
• digital invoicing processes.

The button enables users to initiate payments directly from the respective digital channel without having to scan a QR code.

The online button is available in several language and design options and can be customised to suit the application or website in question.

Available languages:

• German (DE)
• English (EN)
• French (FR)
• Italian (IT)

Available designs:

• Light
• Dark

This ensures a consistent user experience, regardless of the language or design of the application.

Language	Light	Dark
German
English
French
Italian

The TWINT online button is intended exclusively for the digital sending of invoices after a service has been provided. The integration must not be used to offer immediate payment in the shopping basket or checkout process (such as TWINT in e-commerce or with card payment).

Please note that the TWINT online button is not a checkout payment method and must NOT be used as an instant payment option in the shopping basket or as part of the checkout process.

In practical terms, this means that in e-commerce and similar scenarios, the online button must not be displayed, communicated to or sent to the customer until the goods ordered have been dispatched or the service has been provided.

The invoice (with an integrated TWINT online button or payment link) is sent to the customer once the service has been provided, usually by e-mail, via the customer portal or as a document in the app. The use of the online button solely for prepayment is prohibited. In the checkout process itself, the button must not appear as an option for instant payment; it is expressly intended solely for digital invoicing after delivery.

Best-practice process (e-commerce example):

• Customer orders goods or services
• Merchant delivers the goods or provides the service
• The merchant sends their invoice using the integrated TWINT online button
• The customer pays the invoice via TWINT

This process ensures that the requirements of TWINT invoice are met in terms of permitted use cases and buyer protection. The TWINT online button may therefore only be used for digital invoicing once a service has been provided.

TWINT is a secure, trustworthy payment method for end customers. This value proposition also applies to TWINT invoice. Buyer protection is governed as follows:

• A TWINT invoice may only be issued once a service has been provided
• Traditional prepayment is not permitted
• When goods are dispatched, the handover to the carrier (post office, courier, etc.) is deemed to be the time-of-service provision
• For service contracts, successful completion is the determining factor
• Only from this point onwards may a TWINT invoice be sent to the customer (with an online button or payment link)

Exceptions where invoicing is permitted prior to the provision of a service can be found in the applicable GTCs.

Notwithstanding the exceptions set out in the GTCs, the following use cases are not permitted:

• Travel bookings
• Ticketing and event transactions (e.g. festivals, concerts)
• Voucher purchases
• Use cases where payment is usually made before the service is provided

Merchants and their acquirers or PSPs are responsible for complying with these requirements. In the event of violations, the acquirer is liable to TWINT; the associated financial risk may be passed on to the merchant.

The basic approach of this model is to ensure security for TWINT users, primarily through clearly defined and controlled use cases rather than through downstream buyer protection mechanisms such as chargebacks. Disputes which arise due to inadequate service provision, incorrect deliveries or mix-ups, for example, are therefore not fully covered by TWINT. Such cases remain subject to the applicable consumer protection legislation and the merchant’s complaints and support procedures.

To make customers aware of the TWINT payment option, an information bar is placed on their Swiss QR bill. This separates the invoice section from the payment section, and the receipt slip and is a key visual branding element.

The full design guidelines are set out in the style guide and the brand guidelines.

The bar contains these elements:

• The TWINT logo
• A note saying: “This invoice can also be paid with TWINT.”
• A pair of scissors icon on the perforated edge

It is available in four languages – German, English, French and Italian – and is placed full-bleed above the payment details on a standard A4 invoice.

The following specifications apply in terms of size, colour and font:

• Width: 210 mm; height: 11 mm
• Background colour: TWINT Black (#262626)
• Font: Roboto Medium, 10 pt, white (#FFFFFF)

When integrating the bar, please note the following points:

• The bar must not be scaled or distorted in length or width
• It must not be cropped or used in sub-elements
• Changes to its colour or transparency are not permitted

The TWINT online button is the visual entry point for digital invoice payments and represents the payment link (paylink). It is available in several language and design variants so that it can be integrated seamlessly into various applications and websites.

Correct usage is governed by the provisions of the brand guidelines.

The button is available in

• German, English, French or Italian and
• light or dark.

Language	Light	Dark
German
English
French
Italian

Technical specifications:

• Standard button height: 58 px
• Automatic border radius: 6 px
• No background, no border
• Language button is integrated as an image: < img src=”button_[design]_[sprache].svg” >
• Naming convention:
  • button_light_de.svg
  • button_dark_fr.svg

Any further modification of the button, such as changes to its colour, distortions or replacing individual elements, is not permitted.

The brand guidelines, as amended, are always authoritative.

For details on the technical integration of the online button, including an integration example and HTML code, see Section 3.2. Implementing online buttons and payment links.

This diagram illustrates the complete TWINT invoice processing workflow, from the creation of the debtor item in the ERP/accounting system to the actual payment and the final debtor reconciliation.

Payment processing involves all parties concerned: the ERP/accounting system (biller), the biller, the biller’s bank, the TWINT acquirer bank, TWINT and the customer.

Step 1: invoice creation and dispatch

• The merchant’s ERP or financial accounting system opens a debtor item
• The merchant sends the invoice to the customer

Step 2: payment scheduling

• The customer receives the invoice and schedules the payment via the TWINT app

Step 3: execution on the due date

• TWINT executes the payment on the selected due date
• A camt.054 file is then created and made available via SFTP
• At the same time, a pain.001 payment order is sent to the TWINT acquirer bank

Step 4: collective payout

• The TWINT acquirer bank executes a collective payout that includes all transactions contained in the camt.054 file
• Additional e-banking invoice payments can also be included in the actual payout

Step 5: reconciliation of accounts receivable

• The merchant imports the camt.054 file from TWINT and the camt.053 file from the bank and reconciles them to ensure that all settled payments have actually been received

The camt.054 file contains all executed TWINT invoice transactions and serves as the basis for the reconciliation of accounts receivable in the accounting software. The file is generated automatically after each payment is executed and made available via the SFTP server.

An example of a camt.054 file is available for download here.

The SFTP server is the technical infrastructure through which TWINT automatically makes the camt.054 file available after each payment has been executed. The merchant can retrieve the files from there and import them directly into their accounting software.

The following steps are required to use the SFTP server:

• Setting up SFTP access as part of the TWINT onboarding process
• Configuration of the SFTP client with the access details provided (host, port, username, password)
• Regular retrieval of the camt.054 files which are made available from the specified directory on the server

The camt.054 file is automatically stored on the SFTP server after each payment has been executed and is available for download immediately after it has been created.

Detailed set-up instructions and the access details required will be provided as part of the onboarding process.