Validate card numbers, identify scheme and Swiss issuer, generate Luhn-valid test PANs per scheme — and see what a TWINT test environment actually requires.
The TWINT Merchant API is not publicly accessible and not made available on
request (TWINT FAQ). Integration runs exclusively through a payment service
provider or certified plug-in; direct integration requires an application to TWINT AG. The test tooling
— the TWINT Configurator app (switches a test phone with a Swiss number onto the PAT
environment), test vouchers, and the integration portal
(portal-int.twint.ch) — is distributed only via your PSP or partner contract.
The practical test route is a PSP sandbox, and those are public: Datatrans, Saferpay / Worldline, Adyen and Computop publish their TWINT test instructions, and Datatrans/Saferpay hand out free test accounts. You cannot test against TWINT directly — but you can test TWINT payments end-to-end through a PSP sandbox today (Swiss test mobile number + Configurator + vouchers from the PSP).
QR-bill touchpoint: TWINT is one of the two registered
alternative procedures in the Swiss QR Code (lines 33/34, max 2 × 100
chars — the other is eBill, whose syntax is published). TWINT's line syntax is delegated to
TWINT AG and not public; PSP integrations show the shape twint/light/<token>, but the
token is generated by TWINT's backend — so there is nothing meaningful to generate or validate client-side.