Coco Wallet API integration services (USDT / USDC remittance & OpenFinance)
Protocol analysis, on-chain reconciliation, and production-ready APIs for Coco Pago accounts, balances, and Polygon stablecoin transactions
Bring Coco Wallet account data, USDT/USDC balances, and on-chain transfer history into your stack
Coco Wallet (Coco Pago) is a Venezuela-focused digital wallet that lets users send dollars and bolivares using Tether (USDT) and USD Coin (USDC) stablecoins on the Polygon network. We deliver authorized integration services so fintechs, accounting tools, treasury platforms, and remittance partners can read account state, transaction history, and settlement events without rebuilding client logic from scratch.
0xc213…, USDC contract 0x2791…) to confirm settlement, gas paid, and final block confirmation.Why Coco Wallet data matters
Coco Wallet was launched out of Y Combinator (S'19) by Victor A. Charles, Kevin Charles, and Francisco Martin under the company Coco Mercado. The Venezuela rollout in March 2022 quickly turned it into a routing layer for diaspora remittances, with the largest sending cohort located in Europe — which is why in 2024 Coco Wallet integrated Ramp Network's on/off-ramp coverage to ease European top-ups. By Q1 2026 Venezuela had risen to the 17th largest cryptocurrency market globally, with roughly $17.9 billion in retail volume, and USDT alone accounted for more than 90% of P2P listings against the bolívar. This is the macro context in which Coco Wallet's account and transaction data has become genuinely valuable: it is the closest thing many Venezuelan households have to a structured, dollar-denominated bank statement.
The data that flows through Coco Wallet — wallet balances, inbound remittances, in-store payments, peer-to-peer transfers, and Polygon settlement metadata — is precisely the kind of structured, server-anchored OpenData that downstream systems want to query: accountants reconciling family transfers, freelancer platforms auto-paying contributors, merchants matching sales to wallet credits, and analytics teams measuring corridor flow.
Data available for integration
The table below summarizes the structured data sets we typically expose for Coco Wallet integrations. Each entry maps to a specific in-app surface, defines the granularity our APIs return, and points at the most common downstream use case.
| Data type | Source (in-app) | Granularity | Typical use |
|---|---|---|---|
| Account profile | Sign-in & KYC screen | User ID, handle, country, KYC tier | Identity binding for partner platforms |
| Stablecoin balance | Wallet home (USDT, USDC) | Per-asset balance, last refresh timestamp | Treasury dashboards, real-time net-worth display |
| Transaction history | "Movimientos" / activity tab | Per-transfer: amount, asset, counterparty, fee, status | Accounting reconciliation, expense reports |
| On-chain settlement | Polygon blockchain | Tx hash, block, confirmations, gas, contract | Audit trail, regulator-ready proof of transfer |
| Remittance corridor metadata | Send-money flow | Sender region, recipient region, FX reference | Corridor analytics, AML risk scoring |
| Merchant payment | Pay-in-store & QR scan | Merchant ID, amount, USDT/USDC channel | POS reconciliation for stores accepting Coco Pago |
| Bolívar reference rate | Quote screen | USD/VES rate snapshot at tx time | Local-currency reporting, tax filings |
Typical integration scenarios
Below are five end-to-end scenarios we ship most often. Each one names the business context, the specific Coco Wallet data or API call involved, and how it maps to the broader OpenFinance pattern.
1. Diaspora-to-family remittance reporting
A European user sends EUR via an on-ramp that converts to USDC on Polygon, then forwards it to a relative's Coco Wallet. We bind both accounts under a single consent token, then expose a unified ledger so the sender can prove deliverability and the recipient can issue a tax-friendly statement. Maps to OpenFinance "account information service" + on-chain proof of settlement.
2. Freelancer payroll for Venezuela-based contractors
A global staffing platform pushes monthly USDC payouts into contractor wallets and needs a confirmation webhook plus a downloadable PDF statement per contractor. The integration uses our balance API, an outbound payment endpoint, and a webhook that fires when the corresponding Polygon block reaches six confirmations.
3. Local merchant POS reconciliation
A bodega in Caracas accepts USDT from Coco Wallet customers via QR. Their POS calls our merchant-side endpoint to fetch the day's USDT credits, matches them to printed receipts, and exports a daily VES-denominated summary using the official BCV reference rate captured at tx time.
4. Accounting and ERP sync for SMBs
SMBs operating in both bolívares and dollars feed Coco Wallet movements into QuickBooks, Xero, or in-house ERPs. We deliver a CSV/JSON export job that runs nightly, joins on-chain settlement data, and tags each line with a chart-of-accounts code. The OpenData mapping is the same one PSD2 AISPs use — only the asset class is stablecoin instead of fiat.
5. Compliance & AML risk scoring
Compliance teams need counterparty risk on cross-border flows. We surface counterparty wallet addresses, on-chain history depth, and a heuristic risk tag drawn from public chain analytics. This maps to FATF travel-rule expectations for VASPs without exposing raw user PII to third-party scoring engines.
Deliverables checklist
- Protocol & auth flow report (OAuth-style token chain, refresh logic, device fingerprint behavior)
- OpenAPI / Swagger specification for every endpoint we wrap
- Runnable source code in Python and Node.js (login, balance, statement, webhook handler)
- Polygon on-chain reconciliation worker (USDT & USDC ERC-20 transfer parser)
- Test harness with replay fixtures for sandbox and production-like scenarios
- Compliance brief: SUDEBAN context, FATF travel rule, GDPR for European senders
Technical implementation — login & session
// Bind a Coco Wallet account under user consent (pseudocode)
POST /api/v1/coco-wallet/auth/bind
Content-Type: application/json
{
"handle": "user@cocopago",
"device_id": "dvc_8a91...",
"consent_scope": ["balance:read", "tx:read", "webhook:settlement"]
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rft_3f...",
"expires_in": 3600,
"consent_id": "cns_2026_04_28_001"
}
Technical implementation — statement export
// Pull a paginated USDT + USDC statement with on-chain proof
POST /api/v1/coco-wallet/statement
Authorization: Bearer <ACCESS_TOKEN>
{
"account_id": "acc_ve_1198...",
"from_date": "2026-03-01",
"to_date": "2026-03-31",
"assets": ["USDT", "USDC"],
"include_chain_proof": true,
"page": 1, "page_size": 100
}
200 OK
{
"items": [
{
"id": "tx_19a2...",
"asset": "USDT",
"amount": "125.00",
"direction": "in",
"counterparty": "anon_eu_sender_88",
"ves_rate_snapshot": "36.42",
"chain": { "network": "polygon", "tx_hash": "0xabc...", "confirmations": 128 }
}
],
"next_page": 2
}
Technical implementation — settlement webhook
// Outbound webhook fired when a remittance is finalized
POST https://partner.example.com/hooks/coco-wallet
X-Coco-Signature: t=1714305000,v1=8d5f...
{
"event": "remittance.settled",
"consent_id": "cns_2026_04_28_001",
"account_id": "acc_ve_1198...",
"tx_id": "tx_19a2...",
"asset": "USDC",
"amount": "200.00",
"settled_at": "2026-04-28T14:11:09Z",
"chain_proof": {
"network": "polygon",
"tx_hash": "0xabc...",
"block_number": 60134221
}
}
Compliance & privacy
Coco Wallet operations sit at the intersection of three regulatory frames. In Venezuela, SUDEBAN supervises banking activity and the broader effort to bring crypto-adjacent payment services into a supervised perimeter — including the Conexus initiative that handles roughly 40% of domestic electronic transfers and is building regulated rails for stablecoin services. Globally, the FATF "travel rule" applies to virtual asset service providers above the typical $1,000 threshold and shapes how we surface counterparty data without leaking raw PII. For European senders, we follow GDPR-aligned consent capture, data-minimization, and right-to-erasure handling.
We work strictly under explicit user authorization or documented public/authorized endpoints, store consent records with a verifiable timestamp, log every API call for audit, and never resell raw account data. NDAs and DPAs are available on request, and all source code shipped in the engagement is delivered with a least-privilege configuration template.
Data flow / architecture
A typical Coco Wallet integration follows a four-stage pipeline: Client App → Authorized API gateway → Storage & on-chain enrichment worker → Partner-facing API or webhook. The gateway brokers the in-app session and produces partner-scoped tokens. The enrichment worker joins each in-app movement with its Polygon ERC-20 transfer record so downstream consumers see one canonical row instead of two half-views. From there, partners either pull via REST (statements, balances) or subscribe to webhooks (settlements, merchant payments). For high-volume flows we add a queue (e.g. SQS, Kafka) between the worker and the partner-facing API to absorb chain reorg or app-side retries.
Market positioning & user profile
Coco Wallet's primary user is a Venezuelan household receiving remittances, plus an outbound cohort of senders concentrated in Europe (its largest geographic group) and, secondarily, the United States. On the merchant side, small Venezuelan retailers — bodegas, salons, restaurants — use Coco Pago as a low-fee acceptance channel that bypasses fragile card rails. Platform-wise the app ships on both Android and iOS, with the Android Google Play listing under com.cocomercado.cocowallet and an iOS App Store presence. Compared with adjacent products, Coco Wallet sits in the same competitive space as Airtm, Reserve, Zinli, Wally, and Valiu, while sharing the underlying USDT/USDC stablecoin rails with global tools like Trust Wallet, MetaMask, and Binance P2P. This positioning matters for integration partners: any reconciliation layer needs to handle the same stablecoin assets across multiple consumer wallets, not Coco Wallet alone.
Screenshots
Click any thumbnail to view a larger version.
Similar apps & integration landscape
Teams that work with Coco Wallet often also need data parity with adjacent stablecoin and remittance apps used across Latin America. The list below is purely descriptive — these products share the same broader ecosystem and shape the integration patterns our clients ask for.
About us
We are an independent technical service studio focused on App interface integration, OpenData/OpenFinance protocol analysis, and authorized API engineering. Our team has shipped integrations across digital banks, stablecoin payment rails, e-commerce platforms, OTT services, and mobility apps, with a particular focus on Latin American remittance corridors.
- Stablecoin payments, custodial & non-custodial wallets, and cross-border clearing
- Mobile protocol reverse engineering for Android and iOS, in compliant scopes
- Data extraction pipelines, ERP/accounting connectors, and analytics warehousing
- Custom Python / Node.js / Go SDKs and replayable test harnesses
- 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 with no upfront fee, ideal for usage-based teams
Contact
Send us the target app name and your concrete requirements (data types, expected QPS, deployment region) and we will reply with a scoped quote and a delivery timeline.
Engagement workflow
- Scope confirmation: integration scenarios, target endpoints (login, statement, on-chain proof), and consent model.
- Protocol analysis & API design (2–5 business days, complexity-dependent).
- Build & internal validation (3–8 business days), including Polygon reconciliation harness.
- Documentation, sample code, and test cases (1–2 business days).
- Typical first delivery: 5–15 business days; third-party approvals (e.g. Ramp Network access, KYC partner sign-off) may extend timelines.
FAQ
What do you need from me to start?
How long does a first delivery take?
How do you handle compliance for Venezuela-related flows?
📱 Original app overview (appendix)
Coco Wallet — Banca Digital (package com.cocomercado.cocowallet) is the consumer-facing product of Coco Mercado, a Y Combinator S'19 company whose stated goal is to be the #1 remittance and payment service in Venezuela. The app lets anyone with a phone send and receive money locally and internationally with very low fees, using the Tether (USDT) and USD Coin (USDC) stablecoins that track the U.S. dollar — a deliberate design choice to avoid the volatility of other crypto assets and the devaluation of the bolívar.
- Send and receive funds in seconds, locally and across borders
- Protect savings from devaluation in a single click by holding USDT or USDC
- Make and receive unlimited transfers; pay at participating Venezuelan stores
- Funds are not held by a financial institution — only the user can access them via a unique password
- Settlement runs on the Polygon network for fast, low-fee USDT/USDC transfers
- Available on both Android (Google Play) and iOS (App Store), with help and support at https://www.cocopago.app
Coco Wallet launched in Venezuela in March 2022 and processed over $300k in early remittances; by 2024 it had integrated Ramp Network's on/off-ramp infrastructure to better serve its European sender base. The broader context is rapid Venezuelan stablecoin adoption — by Q1 2026 the country had risen to roughly the 17th largest crypto market globally, with USDT featuring in over 90% of bolívar P2P listings.