Skip to main content
TWINT is a mobile payment app in Switzerland. Customers link the app to their bank account and confirm each payment in the TWINT app. Payrails processes TWINT through Checkout.com.

How a TWINT payment works

TWINT is a redirect payment method that the customer completes in the TWINT app:
  1. The customer selects TWINT at checkout.
  2. Payrails creates the payment at Checkout.com and returns a redirect URL.
  3. The customer follows the redirect and confirms the payment in the TWINT app. The customer needs the TWINT mobile app to complete the payment.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from Checkout.com and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. TWINT supports delayed capture: authorize the payment first and capture it later. Capture the full authorized amount in one capture. TWINT doesn’t support partial captures.

Supported currencies and countries

TWINT supports CHF (Swiss franc) as its only presentment currency.

Supported workflows

Before you begin

Complete these steps before you send your first TWINT payment through Checkout.com:
  1. Set up a Checkout.com integration in your workspace. Follow the Checkout.com integration setup guide if you don’t have one yet.
  2. Ask Checkout.com support to enable TWINT on your Checkout.com account.
  3. In the Payrails Portal, go to Settings → Integrations, open your Checkout.com integration, select TWINT under Payment methods, and save.
  4. Add TWINT as a payment option in your workflow.

Request fields for Checkout.com

TWINT needs no method-specific fields. Send the standard authorize fields, including the returnInfo URLs for the redirect. Payrails also sends these fields to Checkout.com when they’re present:

Authorize a TWINT payment

Call authorize a payment with twint as the paymentMethodCode. The response includes the redirect for the customer.
Authorize request
After the customer confirms the payment, they return to your success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How Checkout.com handles TWINT

  • Payrails creates the TWINT payment through the Checkout.com Payment Setup API. Checkout.com needs no payment token for TWINT.
  • Payrails rejects a partial capture request for TWINT, and sends every TWINT capture to Checkout.com as a final capture.
  • If Checkout.com doesn’t return a redirect for a pending TWINT payment, Payrails fails the payment, because the customer can’t complete it.
  • Payrails doesn’t save the TWINT payment method at Checkout.com, so Save Instruments and MIT aren’t available.
Last modified on October 2, 2026