Connect Spin by OXXO accounts, transfers and Visa card data to your stack — under Mexican fintech rules
Spin by OXXO-Tu Cuenta Digital, operated by Compropago S.A. de C.V. IFPE under FEMSA, ended 2024 with 13.1 million active users and processed an average of 73.7 million transactions per month in Q2 2025. That volume sits behind a wallet, a Visa card and 24,000+ OXXO cash points — a uniquely rich dataset for Mexican OpenFinance use cases. We deliver protocol analysis, OAuth-style login flows, SPEI/CoDi transfer endpoints, Visa transaction history, OXXO cash-in/out events and Spin Premia loyalty exports as runnable Python or Node.js source, ready to drop into reconciliation, accounting or remittance products.
What we deliver
Deliverables checklist
- OpenAPI 3.1 specification for every endpoint we ship
- Protocol & auth flow report (token chain, device binding, signing)
- Runnable login, statement and SPEI source (Python, Node.js or Go)
- Webhook receivers for CoDi, SPEI and Visa authorization events
- Excel/CSV/PDF export utilities for accounting handoff
- Postman collection, integration tests and sandbox seed data
- Compliance notes: CNBV/Banxico, Fintech Law, Llave MX, INE/CURP handling
Engagement models
Two ways to work with us, both designed to reduce upfront risk:
- Source code delivery from $300 — runnable API source plus documentation, paid only on acceptance.
- Pay-per-call hosted API — call our managed Spin by OXXO endpoints with a bearer token; pay only for what you use, no setup fee.
Both models can be combined: prototype on the hosted endpoint, then take delivery of the source for in-house operation.
Data available for integration
Below is the data inventory we typically expose for Spin by OXXO. Each row maps a data type back to the originating in-app screen or feature, the granularity of the export and a typical downstream use. The list is derived from the public Spin by OXXO product description, FEMSA quarterly disclosures and our own protocol traces.
| Data type | Source (screen / feature) | Granularity | Typical use |
|---|---|---|---|
| Account profile & KYC status | Onboarding (phone + INE scan) | Per user, with timestamps | Identity verification, compliance gating |
| Wallet balance | Home screen "Saldo" | Real-time MXN | Treasury dashboards, low-balance alerts |
| SPEI transfers (in/out) | Transfer module | Per transaction, clave de rastreo | Reconciliation, fraud screening |
| CoDi QR collections | Cobrar / pagar QR | Per QR, per settlement | POS reporting, merchant payouts |
| Visa card authorizations | Tarjeta digital / física | MCC, merchant, amount, FX | Spend analytics, expense management |
| OXXO cash deposits / withdrawals | OXXO store events | Per store, per ticket | Cash flow analytics, AML signals |
| Bill payments & airtime | Servicios / Recargas | Per biller, per recharge | Subscription tracking, household budgeting |
| Spin Premia loyalty points | Triple-points engine | Per accrual / redemption | Loyalty CRM, partner-brand attribution |
| Cross-border remittances | US → MX inbound (Kira-style) | Per remittance, FX, sender ID | Diaspora finance, compliance reporting |
Typical integration scenarios
1. SME accounting reconciliation
A Mexican SME using Spin by OXXO as its operating wallet needs daily SPEI and Visa card data inside Contpaqi, Aspel or QuickBooks. We deliver a nightly job that pulls SPEI inbound/outbound and Visa authorizations, normalises them into a common ledger schema and pushes the rows through the accounting tool's import API. This is a textbook OpenFinance read-only use case under the upcoming CNBV technical standard.
2. Remittance corridor onboarding
A US-side remittance operator wants to deposit funds directly into Spin by OXXO wallets, mirroring the 2025 Kira partnership. Our integration covers beneficiary lookup by phone or CLABE, FX conversion logging, SPEI deposit initiation and a webhook back to the sender app with the clave de rastreo for receipt generation.
3. Embedded finance for retailers
A retail chain wants to pay supplier invoices from a Spin by OXXO business sub-account and reconcile cash drops at OXXO stores against expected ticket totals. We expose CoDi QR generation for collections, SPEI payouts for supplier invoices and a daily cash-in feed that matches store-level deposits to invoice IDs.
4. Loyalty & CRM enrichment
A consumer brand sponsoring Spin Premia triple-points campaigns wants attribution data: which Visa card transactions at which merchants triggered which point accruals. The export pipeline joins Visa authorisation events with Spin Premia accrual records and pushes the union into Segment, mParticle or a customer data warehouse.
5. AML & risk monitoring
A compliance team needs near-real-time visibility into cash deposits and withdrawals across 24,000+ OXXO stores plus SPEI velocity per user. Our webhook fan-out delivers events to a rule engine (Sardine, Unit21 or in-house) with structured fields for amount, store, device, geolocation and KYC tier — useful inputs for SAT and CNBV-style reporting.
Technical implementation
OAuth-style login (pseudocode)
POST /api/v1/spin/auth/login
Content-Type: application/json
X-Device-Id: 5e9b...
{
"phone": "+52 55 1234 5678",
"password": "***",
"device_fingerprint": "android:14:pixel-7"
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rt_2f8c...",
"expires_in": 1800,
"kyc_tier": 2,
"curp_verified": true
}
Statement query (pseudocode)
POST /api/v1/spin/statement
Authorization: Bearer <ACCESS_TOKEN>
{
"account_id": "spin:5215512345678",
"from_date": "2026-04-01",
"to_date": "2026-04-30",
"types": ["SPEI_IN","SPEI_OUT","CARD","OXXO_CASH"],
"page": 1, "page_size": 100
}
200 OK
{
"items": [
{"id":"tx_01","type":"SPEI_IN","amount":1500.00,"currency":"MXN",
"clave_rastreo":"SPEI20260415...","counterparty_clabe":"012180...",
"ts":"2026-04-15T10:22:11-06:00"},
{"id":"tx_02","type":"CARD","amount":-249.50,"currency":"MXN",
"merchant":"OXXO 1234 CDMX","mcc":"5499",
"ts":"2026-04-15T18:45:02-06:00"}
],
"next_page": 2
}
SPEI payout webhook (pseudocode)
POST {your_webhook}
X-Spin-Signature: t=1714560000,v1=8a3f...
{
"event":"spei.payout.settled",
"payout_id":"po_9f2c",
"clave_rastreo":"SPEI20260501ABC123",
"amount":2500.00,"currency":"MXN",
"beneficiary_clabe":"012180001234567890",
"status":"SETTLED",
"settled_at":"2026-05-01T09:14:55-06:00"
}
# Verify HMAC, ack 200, then update ledger.
Error handling follows standard HTTP semantics with a small problem-details JSON envelope (code, message, request_id). Idempotency keys are required on all SPEI/CoDi mutations. Token refresh, device-binding rotation and rate-limit back-off are wired in by default.
Compliance & privacy
Mexican fintech framework
Spin by OXXO operates as an IFPE (Institución de Fondos de Pago Electrónico) authorised by the Comisión Nacional Bancaria y de Valores (CNBV) under the 2018 Fintech Law and the 2025 Fintech Law 2.0 amendments. Our integrations stay inside that perimeter: explicit user consent, KYC mirroring rather than KYC bypass, and adherence to forthcoming CNBV/Banxico Open Finance technical standards and consent guidelines, plus alignment with the new Llave MX national digital identity.
Privacy & data minimisation
All deliveries follow Mexico's Federal Law on Protection of Personal Data Held by Private Parties (LFPDPPP). Only data required for the agreed scenario is transmitted, INE/CURP fields are tokenised, and PCI-relevant card data is referenced by network token rather than PAN. SPEI rails align with the public SPEI specification maintained by Banco de México.
Data flow & architecture
A typical Spin by OXXO integration uses a four-stage pipeline:
- Client / mobile: Spin app or a server-side replay client authenticates with phone + password + device fingerprint, stores the refresh token in a vault.
- Ingestion API: our gateway brokers calls to login, statement, SPEI and CoDi endpoints, applies idempotency keys and rate-limit guards.
- Storage: events are persisted in PostgreSQL (transactions) and S3 / GCS (raw payloads, exports), with row-level encryption on personally identifiable fields.
- Analytics / output: downstream consumers — accounting tools, BI dashboards, risk engines or partner APIs — read normalised data via REST/GraphQL or scheduled Excel/CSV exports.
Market positioning & user profile
Spin by OXXO targets unbanked and underbanked Mexican consumers — a B2C base skewing 18–45, mobile-first on Android and iOS, frequently transacting in cash through OXXO stores while using the digital wallet for SPEI, e-commerce and bill payments. Active users grew from 9.8M in Q4 2023 to 13.1M in Q4 2024, and FEMSA has publicly explored a banking licence to deepen the product. The integration audience for our APIs is largely B2B: Mexican SMEs, US-Mexico remittance operators, regional retailers, accounting platforms and fintech aggregators that want to read or write Spin by OXXO data on behalf of authorised users.
Screenshots
Tap any thumbnail to enlarge.
Similar apps & integration landscape
Teams that integrate Spin by OXXO often need to harmonise data with other Mexican wallets and neobanks. Below is the broader ecosystem we frequently work alongside; we list each app neutrally as part of the OpenFinance landscape rather than ranking them.
- Mercado Pago — The Mercado Libre wallet holds e-commerce orders, QR payments and money-market balances; users who also work with Mercado Pago typically need unified transaction exports across both platforms.
- Cuenca — A Mexican IFPE offering SPEI accounts and a Mastercard; integration patterns mirror Spin by OXXO and are often combined for cross-wallet balance views.
- Fondeadora — Personal and business debit accounts with savings interest; finance teams often consolidate Fondeadora and Spin transactions in the same accounting feed.
- Nu Mexico (Nubank) — Brazilian neobank operating credit cards and savings in Mexico, growing fast among younger users; relevant for cross-product spend analytics.
- Klar — Digital credit and debit issuer in Mexico; statement-export logic is similar to Spin's Visa flows.
- RappiPay — Wallet attached to the Rappi delivery superapp; integration use cases overlap with retail and remittance scenarios.
- Stori — Credit-card-first neobank focused on underbanked segments; combined views with Spin help underwriters see both spend and cash-in patterns.
- Albo — Mexican neobank with personal and business accounts; often paired with Spin by OXXO in SME treasury setups.
- BBVA Wallet (Mexico) — Tokenised card and SPEI features inside Mexico's largest bank; Spin transactions are commonly reconciled against BBVA primary accounts.
- Banco Azteca — Branch-heavy retail bank with a mobile app serving similar demographics to Spin by OXXO; useful for benchmarking remittance and cash-in flows.
About us
OpenFinance Lab is an independent technical studio focused on mobile fintech protocol analysis and authorised API integration. Our engineers come from Mexican IFPEs, payment gateways, mobile reverse engineering and cloud infrastructure, and we have shipped wallet, card and SPEI integrations for clients across LATAM, the US and Europe.
- Wallet, neobank, remittance and POS integrations across LATAM
- SPEI/CoDi gateways, Open Finance read-only consent flows
- Custom Python, Node.js and Go SDKs with full test harnesses
- End-to-end pipeline: protocol analysis → build → validation → compliance review
- Source code delivery from $300, paid only on acceptance
- Pay-per-call hosted API for teams that prefer usage-based pricing
Contact
For quotes or to submit your target app and requirements, open our contact page:
Tell us the target app (e.g. Spin by OXXO), the data scope (SPEI, Visa, CoDi, Premia) and whether you prefer source-code delivery or the pay-per-call hosted API.
Engagement workflow
- Scope confirmation — which Spin by OXXO data and which write actions (SPEI, CoDi, Premia) are in scope.
- Protocol analysis and API design (2–5 business days, complexity-dependent).
- Build and internal validation against sandbox or shadow accounts (3–8 business days).
- Documentation, samples and test cases (1–2 business days).
- Typical first delivery: 5–15 business days; CNBV/Banxico-aligned consent flows may extend timelines.
FAQ
What Spin by OXXO data can be integrated through your APIs?
How long does a Spin by OXXO integration take to deliver?
How do you handle Mexican fintech compliance?
Do you support cross-border remittances into Spin by OXXO accounts?
📱 Original app overview (appendix)
Spin by OXXO-Tu Cuenta Digital is a free Mexican digital account from FEMSA's Spin unit, operated by Compropago S.A. de C.V. IFPE. Users open an account in minutes by entering a phone number and email and scanning their INE; the account ships with a Visa virtual card and an optional physical card available at any OXXO store.
Once active, users can:
- Send and receive SPEI transfers in seconds with any Mexican bank.
- Deposit and withdraw cash at more than 23,000 OXXO stores.
- Pay in person and online with the Visa card (digital or physical).
- Top up airtime for themselves or friends.
- Pay utility bills (electricity, water, internet, phone) directly from the app.
- Pay by QR code via CoDi from the digital account.
- Earn triple Spin Premia points at OXXO stores and partner brands and redeem them for products or airtime.
- Receive deposits from abroad direct to the Spin account.
By Q4 2024 Spin by OXXO had reached 13.1 million active users; by Q2 2025 it was processing roughly 73.7 million transactions per month, and FEMSA had extended its Visa partnership for another eight years while exploring a full Mexican banking licence.