> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# TWINT

> Accept TWINT payments from customers in Switzerland in CHF, with delayed capture and confirmation in the TWINT app.

<picture noZoom>
  ![TWINT logo](https://assets.payrails.io/img/logos/twint/logo.svg)
</picture>

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](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-a-payment.md) later. Capture the full authorized amount in one capture.

## Supported currencies and countries

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

TWINT is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Europe**</td><td>🇨🇭 Switzerland</td></tr>
  </tbody>
</table>

## Integrate TWINT

Choose the PSP that processes TWINT for you. The guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

> [card]
>
> Checkout.com logo
>
> Checkout.comTWINT via Checkout.com
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/twint/checkout-com.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/twint/checkout-com.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate TWINT

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows TWINT when your workflow returns it as a payment option.
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `twint` as the `paymentMethodCode`. The PSP guide lists the `meta` fields that PSP requires.

In both cases, confirm the final result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status.


## Related topics

- [TWINT via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/twint/checkout-com.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.