TWINT Switzerland Mobile Payment API
TWINT Switzerland mobile payment REST API (via PSP gateway integration) for Swiss merchants to accept smartphone-based mobile payments from TWINT's 5M+ Swiss users directly linked to their bank account or prepaid balance, covering in-store QR code, e-commerce redirect, and order-ahead scenarios through the Swiss banking industry's collective mobile payment standard embedded in all major Swiss banking apps. Enables AI agents to manage TWINT checkout for Swiss mobile payment automation, handle QR code generation for in-store TWINT payment automation, access e-commerce redirect for online TWINT payment automation, retrieve payment confirmation for Swiss transaction verification automation, manage refund processing for TWINT payment reversal automation, handle payment status webhook for TWINT event automation, access merchant TWINT for gastronomy and retail automation, retrieve cashback and coupon for TWINT loyalty automation, manage TWINT order for food and service ordering automation, and integrate TWINT via certified PSP gateways (Datatrans, Stripe CH, PayRexx, Mollie) for end-to-end Swiss mobile payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Swiss mobile payment. FINMA, FADP. PSP gateway API. CH. Bank account and payment data.
⚡ Reliability
Best When
A Swiss merchant, restaurant, or online shop wanting AI agents to accept TWINT mobile payments from 5M+ Swiss users through a TWINT-certified PSP gateway integration.
Avoid When
TWINT-CERTIFIED PSP IS REQUIRED: TWINT does not provide direct merchant API; automated direct TWINT connection creates no endpoint; automated TWINT acceptance requires TWINT-certified PSP (Datatrans, Stripe CH, PayRexx, Mollie CH). SWISS MERCHANT REQUIRED: TWINT merchant account requires Swiss commercial registration; automated foreign entity TWINT merchant creates eligibility rejection. PAYMENT IS CONFIRMED ASYNC VIA APP: TWINT payment requires consumer to approve in banking app; automated synchronous payment confirmation after QR display creates premature success; automated must await webhook or polling for consumer approval. CHF ONLY: TWINT is CHF-denominated only; automated multi-currency TWINT assumption creates CHF-conversion-required error; automated TWINT checkout must present amount in CHF.
Use Cases
- • Accepting TWINT QR payments from Swiss consumers for retail and restaurant POS automation agents
- • Processing TWINT e-commerce checkout for Swiss online shop payment automation agents
- • Integrating TWINT into food delivery and order-ahead app for Swiss hospitality automation agents
- • Receiving TWINT payment webhooks for Swiss marketplace and service fulfillment automation agents
Not For
- • Non-Swiss markets (TWINT is Switzerland-only CHF payment method)
- • International customers without Swiss bank accounts or TWINT (TWINT is Swiss-resident focused)
- • Direct TWINT network integration (TWINT is only accessible via TWINT-certified PSP gateways)
Interface
Authentication
TWINT accessed via TWINT-certified PSP gateways with gateway API key auth. REST API with JSON. Zurich, Switzerland. TWINT established 2016 by Swiss banking consortium (UBS, Credit Suisse, PostFinance, Raiffeisen, ZKB, etc.). Products: TWINT QR, TWINT e-commerce, TWINT order, TWINT loyalty/coupons. Accessible through: Datatrans, Stripe Switzerland, PayRexx, Mollie CH. FINMA regulated. 5M+ users covering 50%+ of Swiss smartphone users. Switzerland's dominant mobile payment method. CHF only.
Pricing
Zurich CH. Swiss banking consortium. Gateway-accessed. CHF. FINMA. Per-transaction gateway fees.
Agent Metadata
Known Gotchas
- ⚠ TWINT-CERTIFIED PSP REQUIRED: TWINT has no direct merchant API; automated direct TWINT integration creates non-existent endpoint; automated TWINT acceptance requires TWINT-certified PSP gateway (Datatrans, Stripe CH, PayRexx)
- ⚠ SWISS COMMERCIAL REGISTRATION REQUIRED: TWINT merchant account requires Swiss company registration; automated foreign entity TWINT merchant creates eligibility rejection at TWINT-certified PSP onboarding
- ⚠ CONSUMER APPROVAL IS ASYNC IN BANKING APP: TWINT payment confirmation requires consumer to approve in their Swiss banking app (UBS, PostFinance, Raiffeisen, etc.); automated synchronous result creates premature success; automated must poll or await webhook
- ⚠ CHF ONLY — NO MULTI-CURRENCY: TWINT transactions are CHF-only; automated multi-currency price display for TWINT creates CHF conversion required; automated TWINT checkout must present order total in Swiss Francs
- ⚠ QR CODE EXPIRY FOR IN-STORE: TWINT QR codes for in-store payment have expiry (typically 5-10 minutes); automated static QR assumption creates expired QR for slow customers; automated in-store QR must be regenerated or use dynamic QR
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for TWINT Switzerland Mobile Payment API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.