IBAN · QR-IBAN · QR-ref · RF-ref · BIC + LEI + UID lookup · ISO 20022 addresses. Client-side only; nothing leaves your browser. (… CH/LI banks loaded.)
Live data from api.six-group.com/api/epcd/bankmaster/v3 — the official SIX participant directory (IID, BIC, address, SIC/IP capability). Cached in your browser for 24 hours.
Validate any PAN (mod-10 Luhn), identify the scheme + product, and — for Swiss-issued cards — name the actual issuer (Viseca, Cornèrcard, Swisscard, Swiss Bankers, PostFinance, Cembra). Generate Luhn-valid test PANs per scheme for fixtures / sandbox seeding.
Check individual / entity names against the US OFAC Specially Designated Nationals (SDN) list, UN Security Council consolidated list and EU Financial Sanctions File. Data from api.sanctions.network — fetched on first use, cached in your browser for 24 hours. Informational only — not a substitute for a regulated screening tool.
No public registry of fraud-reported Swiss IBANs exists — banks share via closed SCC/Bankenstamm channels only.
Build and validate the <PstlAdr> block for CBPR+ / SWIFT MX (pacs.008, pain.001),
SIC RTGS and the Swiss QR-bill. Hybrid addresses are allowed since SR November 2025; fully unstructured addresses
are rejected in CBPR+ for value dates from 14 Nov 2026 and in SIC from the
20 Nov 2026 release. The QR-bill accepts only structured addresses (type S) since
22 Nov 2025 (IG v2.3 — the old combined type K is rejected).
The two demo buttons fill the same fields from a Swiss and a Chinese address, which
is where structured addressing gets awkward: BldgNb precedes StrtNm in the Chinese
reading order (969 West Wen Yi Road), PstCd is 6 digits rather than 4, and the district
(Yuhang) is an administrative level with no slot here at all — in ISO 20022 it belongs in
<DstrctNm>, never folded into StrtNm or TwnNm.
UUIDv4 used by SWIFT gpi and ISO 20022 (CBPR+) to correlate a payment across all participating institutions. Lowercase, 36 chars including hyphens.
UTF-8 → SHA-256 → hex. Useful for payment-message fingerprinting (sha256(MT103) for idempotency keys, file digests, etc.).
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.