Connect UBS TWINT payments, balances and statements to your stack — under authorization
UBS TWINT is Switzerland's most widely used mobile payment app, with well over a million UBS registrations and more than 773 million TWINT transactions across the network in 2024. That activity sits behind a 6-digit PIN or fingerprint and never leaves a single device by default. We build authorized UBS TWINT API integration layers — account login mirrors, transaction history export, balance sync and statement endpoints — so finance, accounting and analytics teams can use that data through clean, documented interfaces instead of screen-scraping.
Feature modules
Each module below names the concrete data or capability it exposes and one operational use. We scope only what you are authorized to access — either through your own credentials and consent, or through documented, authorized interfaces such as the Swiss open-banking platform bLink.
Account login & authorization mirror
Reproduces the UBS TWINT activation and sign-in flow — device binding, 6-digit PIN / biometric gate, session tokens and refresh — so your backend can re-establish an authorized session on the user's behalf. Used to keep a long-running data feed alive without re-prompting the user every call.
Transaction history & movement feed
Returns sent / received / requested money, in-store QR payments, parking and fuel charges, online-shop authorisations and in-app ticket purchases as one normalised list with amount, currency (CHF), counterparty, merchant, category, timestamp and status. Used for automated reconciliation against an ERP or accounting ledger.
Balance & funding-source sync
Exposes the linked UBS account balance or prepaid TWINT balance, recent top-ups, and pending authorisations. Used to drive low-balance alerts, cash-flow dashboards and pre-authorisation checks before a batch payout.
Statement export & document API
Generates a date-ranged statement with paging and filters (by type: P2P, retail, mobility, parking, donations) and renders it to JSON, CSV/Excel or a PDF document. Used for monthly bookkeeping close and for handing auditors a clean activity record.
KeyClub loyalty & vouchers
Reads KeyClub points accrued when paying via TWINT with the registered UBS credit card, plus purchased / received digital voucher and credit balances. Used to reconcile rewards liabilities and to feed a unified loyalty view in a CRM.
Merchant & payment-event webhooks
For merchant-side accounts, pushes payment-confirmed, refund and settlement events (QR / Beacon / store terminal) to your endpoint within seconds. Used to mark orders paid in real time and to trigger downstream fulfilment.
Data available for integration (OpenData perspective)
The table maps the data UBS TWINT holds to the screen or feature it comes from, the granularity you can expect, and a typical downstream use. Field availability depends on the authorization path and the account type (personal vs. merchant).
| Data type | Source (screen / feature) | Granularity | Typical use |
|---|---|---|---|
| P2P transfers | Send / request / receive money | Per transaction: amount, CHF, counterparty alias, message, timestamp, status | Expense splitting, cash-flow analytics, anti-fraud signals |
| Retail & QR payments | In-store QR / Beacon at Coop, Migros, SBB, Swiss Post | Per transaction: merchant, store, amount, category, timestamp | Reconciliation against POS, spend categorisation, loyalty matching |
| Online-shop payments | E-commerce checkout (Ticketcorner, microspot, SBB, Swisscom) | Per order: merchant, order reference, amount, authorisation result | Order-to-payment matching, chargeback handling, reporting |
| Mobility & parking | Parking meters, fuel QR, in-app tickets (Fairtiq, Lezzgo, SBB) | Per session: location/zone, duration, amount, vendor | Travel-expense automation, mobility analytics, compliance logs |
| Account / prepaid balance | Home screen, funding-source settings | Current balance, top-ups, pending holds | Low-balance alerts, pre-payout checks, treasury dashboards |
| Statements | Activity / statement download | Date-ranged, paged, per-line records with references | Bookkeeping close, audit packs, tax preparation |
| KeyClub points | Loyalty section (UBS credit card) | Points balance, accrual events, redemption history | Rewards reconciliation, CRM enrichment, campaign ROI |
| Vouchers & credit | Vouchers / gifts feature | Voucher code state, value, expiry, sender/recipient | Promo liability tracking, gifting flows, fraud checks |
Typical integration scenarios
Five end-to-end patterns we have shipped variants of. Each lists the business context, the data or API involved, and how it maps to OpenData / OpenFinance / OpenBanking thinking.
1 · Accounting & ERP reconciliation
Context: a Swiss SME accepts TWINT in-store and online and wants its books to close without manual matching. Data/API: the transaction history and statement export endpoints provide per-line merchant, reference and category fields. OpenFinance mapping: consented, read-only account-information access feeds an Abacus/Bexio/KLARA-style ledger, exactly the pattern bLink standardises for Swiss banks.
2 · Multibanking & personal finance dashboard
Context: a PFM app aggregates a user's UBS account, TWINT activity and other banks into one view. Data/API: balance sync plus transaction feed, refreshed via token-backed sessions. OpenBanking mapping: mirrors the retail multibanking service that went live in Switzerland via SIX bLink in late 2025, where users aggregate UBS, ZKB and PostFinance accounts in one interface.
3 · Merchant order-to-cash automation
Context: an online retailer needs orders marked paid the instant a TWINT QR is scanned. Data/API: merchant payment-event webhooks (paid / refunded / settled) with order reference and amount. OpenFinance mapping: a payment-status notification channel layered on top of authorized merchant data, the same role payment service providers like Worldline or PPRO play for TWINT acceptance.
4 · Travel & expense capture
Context: a company wants employee parking, fuel and SBB ticket spend pulled into its expense tool automatically. Data/API: the mobility & parking records (zone, duration, vendor, amount) and statement filtering by type. OpenData mapping: structured, categorised spend data exported on a schedule into a reporting pipeline with consent and audit trails.
5 · Loyalty & rewards unification
Context: a retailer cross-references KeyClub points and TWINT vouchers with its own loyalty programme. Data/API: KeyClub points balance / accrual events and voucher state. OpenFinance mapping: read-only enrichment data joined to a CRM, with redemption history used for campaign attribution rather than for any write-back.
Technical implementation
Illustrative request/response shapes for an authorized UBS TWINT integration layer. Endpoint names, auth and payloads are examples of the depth we deliver — final contracts depend on the agreed authorization path. Errors follow a consistent envelope with retry guidance.
API example 1 — session login & token
// Establish an authorized session (pseudocode)
POST /api/v1/ubs-twint/auth/session
Content-Type: application/json
{
"device_binding": "<DEVICE_KEY>",
"credential_ref": "<CONSENT_OR_CREDENTIAL_HANDLE>",
"scopes": ["accounts:read", "transactions:read", "statements:read"]
}
200 OK
{
"access_token": "<JWT>",
"refresh_token": "<OPAQUE>",
"expires_in": 900,
"consent_id": "cns_8f31a2"
}
API example 2 — transaction statement
// Fetch a date-ranged statement (pseudocode)
GET /api/v1/ubs-twint/statements?from=2026-04-01&to=2026-04-30
&type=retail,p2p,mobility&page=1&page_size=200
Authorization: Bearer <ACCESS_TOKEN>
200 OK
{
"currency": "CHF",
"page": 1, "page_size": 200, "total": 137,
"items": [
{ "id":"txn_01H...", "ts":"2026-04-03T08:12:55Z",
"amount": -4.20, "type":"retail", "merchant":"Coop Pronto",
"category":"groceries", "reference":"QR-...", "status":"booked" }
]
}
API example 3 — payment-event webhook
// Merchant webhook delivered to your endpoint (pseudocode)
POST https://your-app.example/hooks/ubs-twint
X-Signature: sha256=<HMAC>
Content-Type: application/json
{
"event": "payment.settled",
"order_ref": "ORD-99213",
"amount": 79.00, "currency": "CHF",
"channel": "qr", "occurred_at": "2026-04-29T14:03:11Z"
}
// respond 2xx within 5s or the event is retried with backoff
Data flow / architecture
A typical pipeline has four nodes: Client app / authorized session → Ingestion API (login mirror, polling & webhooks) → Normalised store (transactions, balances, statements, loyalty) → Consumer outputs (your API, BI dashboards, accounting export, alerts). Consent records, request logs and a dead-letter queue sit alongside the store so every pull is traceable and replayable.
Compliance & privacy
Regulatory alignment
UBS TWINT operates under Swiss financial-market rules: it meets the security standards of Swiss banks, all data remains in Switzerland, and access is protected by a 6-digit PIN or fingerprint. We build to that baseline — handling personal data in line with the revised Swiss Federal Act on Data Protection (revFADP / nFADP, in force since September 2023), respecting FINMA expectations for outsourced processing, and following the consent model used by the Swiss open-banking platform TWINT and SIX bLink. For EU-facing flows we also map to GDPR and PSD2-style strong customer authentication.
How we keep it clean
- Work only under customer authorization or documented, authorized interfaces — never undocumented bypasses
- Consent capture, scoping and revocation built into the session layer
- Data minimisation: pull only the fields a use case needs, drop the rest
- Request and access logging, plus retention controls aligned to your policy
- NDAs and a written processing description on request
- Note: the public TWINT/UBS TWINT API is not openly available; merchant acceptance is via authorized payment service providers, and we scope engagements accordingly
Market positioning & user profile
UBS TWINT is a B2C app for retail customers — primarily existing UBS Switzerland clients and natural persons domiciled in Switzerland — and is explicitly not intended for residents of Australia or the USA. Its users are everyday Swiss consumers paying for groceries, parking, fuel, public transport and online shopping, plus a large P2P money-transfer base. On the acceptance side, around 81% of physical stores and 84% of online shops in Switzerland support TWINT, and roughly 77 million 2024 transactions were in mobility and public transport alone. The platform is Android and iOS, with 2024 additions like home- and lock-screen payment widgets, in-app loyalty cards and a "Pay later" option (immediate or within 30 days). Integration demand therefore concentrates among Swiss SMEs and retailers reconciling TWINT revenue, accounting and ERP vendors, PFM/multibanking apps, and expense-management tools.
Screenshots
App screenshots from the store listing. Click any thumbnail to view a larger version.
Similar apps & integration landscape
Teams that integrate UBS TWINT data often work with the wider Swiss and European payment ecosystem. These apps are part of that landscape — listed here for context, not ranked or criticised — and the same protocol-analysis and OpenFinance patterns apply across them.
PostFinance TWINT
The PostFinance-issued TWINT app holds the same P2P, QR-payment and statement data as UBS TWINT for PostFinance customers. Organisations reconciling TWINT revenue often need a unified transaction export across both issuer apps.
Yuh
Swissquote's neobank Yuh ships its own TWINT integration alongside accounts, cards, trading and crypto balances. Unified spend and portfolio exports across Yuh and UBS TWINT are a common request from PFM builders.
Neon
Neon offers a Swiss IBAN account and Mastercard with categorised transaction data, and links to the prepaid TWINT app. Its movement feed is a natural companion dataset when aggregating a user's everyday spending.
Revolut
Revolut holds multi-currency balances, card transactions, transfers and (in selected European markets) Wero payments. Cross-border users frequently want Revolut and UBS TWINT activity normalised into one ledger.
Wise
Wise stores multi-currency account balances and international transfers with detailed fee breakdowns. Finance teams pair Wise exports with Swiss-franc TWINT data for FX-aware bookkeeping.
Apple Pay
Apple Pay surfaces card transactions and pass data on iOS devices. Where a user pays with both Apple Pay and TWINT, a combined receipt and spend view is a typical integration goal.
Google Pay
Google Pay holds linked-card transactions and is broadly accepted by Swiss online merchants. Its activity history complements TWINT data for full coverage of a shopper's payment methods.
Samsung Pay
Samsung Pay carries tokenised card transactions on Galaxy devices. It appears in the same wallet-aggregation projects that also need UBS TWINT transaction history.
Wero
Wero, the European Payments Initiative wallet launched in 2024, handles account-to-account transfers across several European markets. It is increasingly relevant for cross-border flows alongside Switzerland's TWINT.
PayPal
PayPal holds balances, transaction history and merchant settlement records used widely in Swiss e-commerce. Reconciling PayPal and TWINT receipts into one accounting feed is a recurring deliverable.
What we deliver
Deliverables checklist
- API specification (OpenAPI / Swagger) for the agreed endpoints
- Protocol & auth-flow report (device binding, token / refresh, consent chain)
- Runnable source for login, transaction and statement APIs (Python / Node.js)
- Webhook receiver sample with signature verification and retry handling
- Automated tests, Postman collection and written API documentation
- Compliance guidance: consent, revFADP/GDPR notes, retention and logging
Engagement workflow
- Scope confirmation: integration scenarios and data needs (login, statements, balances, events)
- Protocol analysis and API design — 2–5 business days, complexity-dependent
- Build and internal validation — 3–8 business days
- Docs, samples and test cases — 1–2 business days
- Typical first delivery: 5–15 business days; third-party approvals may extend timelines
About us
We are an independent studio focused on fintech and open-data API integration. Our engineers come from banks, payment gateways, protocol analysis and cloud platforms; we know FINMA, SIX bLink and multi-region privacy rules, and we ship end-to-end financial APIs under security and compliance constraints.
- Payments, digital banking and cross-border reconciliation
- Enterprise API gateways and security reviews
- Custom Python / Node.js / Go SDKs and test harnesses
- Full pipeline: protocol analysis → build → validation → compliance
- Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
- Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost
FAQ
What do you need from me to start a UBS TWINT integration?
How long does delivery take?
Is this compliant with Swiss financial regulation?
Which engagement models are available?
Contact
For quotes or to submit your target app and requirements, open our contact page:
Tell us which UBS TWINT data you want — transactions, balances, statements, loyalty points or merchant events — and your target stack, and we'll come back with a scoped quote and timeline.
📱 Original app overview (appendix)
UBS TWINT is the most widely used mobile payment app in Switzerland — Switzerland's "digital cash" — with well over a million UBS registrations and the Swiss number-one position in mobile payment. It lets users send, request and receive money via smartphone, pay in online stores by scanning a QR code at checkout, and pay cashless at the register via QR codes or the TWINT Beacon (e.g. at Coop and Swiss Post).
- Send, receive and request money quickly and securely to and from friends, family and colleagues
- Pay in online shops (Ticketcorner, microspot, SBB, Coop, Swisscom, Migros) by QR or by switching to the app to authorize
- Collect KeyClub points when paying via TWINT with the registered UBS credit card
- Buy, send and receive digital vouchers and credit as gifts
- Pay parking fees via location tracking or a QR code on the meter; fuel up by scanning the QR code at the pump
- Use TWINT as a payment method in apps like SBB, Fairtiq and Lezzgo to buy tickets without cash
- Withdraw cash via the integrated "Sonect" feature without an ATM; donate to Swiss aid organisations
- Benefit from weekly "Super Deals" discounts; order Nespresso coffee via the partner feature
Security: meets the security standards of Swiss banks; all data remains in Switzerland; protected by a 6-digit PIN or fingerprint; the UBS TWINT account can be blocked at any time. UBS Switzerland AG makes the app available only to existing clients of UBS Switzerland AG and certain other non-US UBS Group subsidiaries domiciled in Switzerland, and to natural persons domiciled in Switzerland; it is not intended for and cannot be used by persons resident in Australia or the USA. Additional information: www.ubs.com/twint.