兴趣爱好BCV TWINT API Integration
============================
Swiss Open Banking for BCV TWINT Payment Data
============================
INTRODUCTION
--------------------
BCV TWINT is the Banque Cantonale Vaudoise distribution of the Swiss TWINT
mobile payment system — and unlike many fintech wallets, it sits on a real
bank account. The TWINT layer is funded directly from the holder's BCV current
or joint account, which means the data behind it spans two distinct surfaces:
regulated account data reachable through the SIX bLink multibanking hub, and
TWINT-specific activity (P2P transfers, parking sessions, loyalty card links,
buy-now-pay-later balances) that lives inside the TWINT app session itself.
For integrators building personal finance apps, expense trackers, fleet tools,
or multibank aggregation services in Switzerland, BCV TWINT represents one of
the richest mobile payment data sources in the Swiss open banking landscape.
The November 2025 launch of SIX bLink retail multibanking — which named Banque
Cantonale Vaudoise as a participating institution — opened a formal, standards-
based consent channel into the BCV account side, while the TWINT layer remains
reachable through an authorized session-based integration approach.
This article covers what data surfaces are available, which integration routes
apply to each, and how those surfaces map onto real-world use cases.
SUPPORTED API FEATURES
--------------------
BCV TWINT integration through OpenBanking Studio exposes the following
functional areas:
• BCV Account Data via bLink AIS
Per-IBAN balance and transaction history through the SIX bLink consent
channel; JSON responses conforming to SFTI Common API message shapes;
paginated transaction lists with booking date, value date, amounts in CHF,
remittance information, and creditor identifiers.
• TWINT P2P Transfer History
Per-counterparty send and receive records from the TWINT messaging rail;
near real-time granularity; counterparty TWINT IDs and linked mobile
numbers included; free-text references preserved.
• Merchant Payment Records
In-store (QR/contactless) and online merchant charges through the TWINT
acceptance network; merchant identifier, channel, and funding source
(BCV account or linked credit card) per transaction.
• Parking Session Data
Per-session timing, station identifier, paid amount, and refunded amount
from the TWINT parking module; suitable for mobility expense tracking.
• Loyalty Card and BNPL Data
Linked loyalty card numbers (Supercard, Cumulus, Jelmoli); buy-now-pay-
later outstanding balance, due dates, and individual deferred charges.
• Profile, Vouchers, and Donations
TWINT account profile fields, digital voucher purchase records, and
per-donation receipts from the TWINT donations module.
USE CASES & APPLICATIONS
--------------------
[1] Personal Finance Management and Expense Tracking
• Aggregate BCV account transactions alongside TWINT P2P flows
into a single normalized account-and-transactions view.
• Automatically categorize merchant charges by channel and retailer.
• Surface BNPL outstanding balances for cashflow forecasting.
• Flag recurring TWINT sends for budget tracking tools.
[2] Business Expense Reporting and Reconciliation
• Split personal versus business inflows based on P2P counterparty
type and free-text reference fields.
• Export merchant payment records with merchant IDs for VAT tracking.
• Reconcile parking session data against per-vehicle expense policies
for freelancer or small-fleet billing.
• Timestamp-matched transaction records streamline audit trails.
[3] Mobility and Fleet Management
• Pull TWINT parking sessions — start time, end time, station ID,
paid and refunded amounts — for per-trip mobility cost analysis.
• Match parking charges against calendar events or route data.
• Generate monthly per-driver mobility expense reports automatically.
• Detect unused time refunds to validate reimbursement claims.
[4] Loyalty Programme Integration and Rewards Analytics
• Cross-reference Supercard, Cumulus, and Jelmoli card numbers against
the underlying TWINT merchant spend that earned them.
• Build spend-to-reward attribution pipelines for partner retailers.
• Identify high-value merchant categories for loyalty campaign targeting.
• Sync voucher purchase records against redemption data from issuer feeds.
[5] Swiss Multibank Aggregation and Open Banking Platforms
• Slot BCV TWINT into a normalized multibank data model that already
handles ZKB TWINT, PostFinance TWINT, UBS TWINT, and Raiffeisen TWINT
on the same shared TWINT rail.
• Use the bLink AIS consent channel for standards-based account access
without maintaining a private API contract per institution.
• Extend to Neon, Yuh, or Revolut Switzerland accounts as counterparties
already appearing in P2P transaction histories.
• One normalized schema covers both the BCV banking layer and the TWINT
payment layer, so downstream code stays bank-agnostic.
BENEFITS & ADVANTAGES
--------------------
✓ Standards-Based Account Access
The BCV account side is reachable through the SIX bLink platform using
SFTI Common API message shapes — a durable, industry-standard contract
rather than a private API dependent on a bilateral agreement.
✓ Two-Layer Data Coverage
A single build covers both the regulated BCV banking surface (balance,
transactions, IBAN) and the TWINT-specific layer (P2P, parking, loyalty,
BNPL), normalized into one schema for downstream simplicity.
✓ Scoped Delivery Options
Builds can be scoped to a single TWINT surface — parking-only, P2P-only,
or loyalty-only — so the engagement stays focused and cost-efficient.
✓ Swiss Regulatory Alignment
Integration is structured under the revised Swiss Federal Act on Data
Protection (revFADP, in force September 2023), with explicit bLink consent
IDs, validity windows, and logged audit trails for FINMA compliance.
✓ Modular Source-Code Architecture
Delivered source splits into a bLink module and a TWINT session module,
so either can be used independently or extended to a second cantonal
partner without rewriting shared TWINT rail logic.
✓ Canary-Protected Maintenance
A recorded canary call is wired into the test suite against the TWINT
session layer; if an app update shifts a payload shape, the canary fails
the build before production traffic is affected.
✓ Re-Consent and Rotation Handling
The integration surfaces a re-consent prompt one week before bLink consent
expiry, and maintains a local audit trail so a TWINT mobile-number
rotation event on the user side does not appear as a data-loss event on
the integration side.
SUBSCRIPTION PLANS
--------------------
OpenBanking Studio offers two delivery models for BCV TWINT integration:
Source-Code Delivery
------------
Starting at $300 USD, paid after delivery once you have reviewed and run
the code. Includes: runnable Python and Node.js client modules (bLink
module and TWINT session module); OpenAPI 3.1 specification; auth-flow
report covering bLink TPP onboarding and TWINT session chain; normalized
schema; integration tests against a recorded consent; interface
documentation. Cycle time: 1 to 2 weeks.
Pay-Per-Call Hosted Endpoint
------------
No upfront fee. Route your calls through the hosted endpoint and pay per
call. The retention scope for session and consent data under this model
is named explicitly in the service agreement. Cycle time matches the
source-code model.
Both paths support scoped builds — commission only the surfaces your project
actually needs.
CONCLUSION
--------------------
BCV TWINT sits at the intersection of Swiss open banking standards and the
shared TWINT payment rail that runs beneath the majority of Swiss mobile
payment apps. The November 2025 bLink multibanking launch removed the biggest
structural obstacle to formal account-side access, and the TWINT session layer
above it is reachable through an authorized integration approach that OpenBanking
Studio has mapped and maintains.
Whether the goal is personal finance aggregation, business expense automation,
fleet mobility tracking, or a full Swiss multibank data layer, the BCV TWINT
data surface provides the transaction-level granularity to support it — in CHF,
with IBAN-level attribution, and with the TWINT-specific context (merchant,
counterparty, parking station) that standard account statements omit.
For integrators ready to move from exploration to delivery, the full technical
breakdown, data surface table, pseudo-code walkthrough, and engagement terms
are available at:
https://openbankingstudio.com/bcv-twint.html
Send the surface or use case you need through the contact page, and the
integration desk will return a delivery plan within one business day.
============================
OpenBanking Studio — authorized API and protocol integration,
one Swiss app at a time.
BCV TWINT and the BCV brand belong to Banque Cantonale Vaudoise.
This article is an independent integration reference and is not
affiliated with BCV or TWINT AG.
============================
