Lindo - Send Money to Cuba: API integration & OpenFinance services

Deliverables checklist

• OpenAPI / Swagger specification for every endpoint
• Protocol report (auth flow, token lifecycle, request signing)
• Runnable Python and Node.js source for login, history, and rate APIs
• Webhook receiver template with HMAC verification
• OFAC / Cuba Restricted List screening helper
• Test plan with sandbox transactions and reconciliation reports

Engagement workflow

1. Scope confirmation: corridors (US→Cuba, EU→Cuba), funding rails, and required data fields.
2. Protocol analysis and endpoint design (2–5 business days).
3. Build and internal validation against staged Lindo accounts (3–8 business days).
4. Documentation, sample requests, and reconciliation test cases (1–2 business days).
5. First delivery in 5–15 business days; payout-webhook stacks may extend to 3 weeks.

1. Diaspora finance app reconciliation

A US-based personal finance app for Cuban-American households wants every Lindo payout to land automatically in its money-tracker timeline. We expose GET /v1/lindo/transactions with cursor pagination and a normalized schema (amount_usd, amount_cup, amount_mlc, fx_quote_id). The app maps each entry to its internal "transfer to family" category, and the Lindo data closes the gap left when Plaid or MX cannot see a Zelle-funded remittance.

2. Agent-network settlement dashboard

An agent network in Florida operates physical cash-collection points. Each daily upload of cash totals must reconcile to Lindo's payout ledger before commission is paid. We deliver a webhook receiver that subscribes to payout.settled events and, together with the rate-snapshot endpoint, produces an end-of-day CSV joining funding rail, applied USD/CUP rate, and final MLC amount.

3. Compliance officer evidence pack

A FinCEN-registered MSB partner needs to demonstrate that none of its onward Lindo flows touched the State Department's Cuba Restricted List. We wire the POST /v1/screening/check helper into the payment pipeline, append the response (match, list_version, screened_at) to every transaction record, and ship a monthly evidence-pack generator that bundles JSON + signed PDF for examiner review.

4. Multi-corridor rate aggregator

A comparison site wants to publish a real-time "best USD→Cuba rate" widget. Our rate-feed crawler pulls Lindo's public quote alongside reference informal market prints (which moved from around 270 CUP per MLC in early December 2025 to roughly 280 by late 2025) and exposes a single GET /v1/rates/cuba JSON response with provider, mid-rate, fees, and freshness in seconds.

5. Crypto-on-ramp settlement loop

A non-custodial wallet wants to let users top up CUP balances directly from BTC. We bridge the wallet's on-chain confirmation event to a Lindo "Bitcoin" funding-rail order, watch the resulting payout webhook, and surface a single status timeline (broadcast → confirmed → lindo_received → mlc_credited) so the user sees one flow instead of two.

Login & session bind (OAuth-style)

POST /api/v1/lindo/auth/login
Content-Type: application/json

{
  "email": "sender@example.com",
  "password": "***",
  "device_id": "ios-7F19C2"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8c1f...",
  "expires_in": 3600,
  "kyc_level": "tier2"
}

Transaction history (paginated)

GET /api/v1/lindo/transactions?from=2026-04-01&to=2026-04-30&cursor=&limit=50
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "items": [
    {
      "id": "txn_01HZ...",
      "created_at": "2026-04-12T14:02:11Z",
      "amount_usd": 50.00,
      "amount_cup": 13500,
      "rate_usd_cup": 270.0,
      "funding_rail": "zelle",
      "recipient": { "name": "A. García", "mlc_card_last4": "4421" },
      "status": "mlc_credited",
      "ofac_check": "clear"
    }
  ],
  "next_cursor": "c_91f3..."
}

Payout status webhook (HMAC-signed)

POST https://your-app.example/webhooks/lindo
X-Lindo-Signature: t=1715300011,v1=2c5e...
Content-Type: application/json

{
  "event": "payout.settled",
  "txn_id": "txn_01HZ...",
  "status": "mlc_credited",
  "rate_snapshot_id": "rs_20260412_140",
  "settled_at": "2026-04-12T14:07:43Z"
}

# Verify: HMAC-SHA256(secret, "{t}.{raw_body}") == v1
# Reject if drift > 5 min or signature mismatch.

Regulatory anchors

Every Lindo integration we build is scoped against US OFAC rules, specifically 31 CFR § 515.570 (Cuban Assets Control Regulations — Remittances), plus the related § 515.572(a)(3) authorization for US-registered money transmitters. We also assume the operating entity is registered with FinCEN as an MSB and, where relevant, holds a state license such as Florida Part II MSB. For European corridors we layer GDPR data-minimization rules on top, since recipient PII is involved.

Privacy & data minimization

Only data you are entitled to access is touched. We avoid persisting full payment-card numbers or Cuban national IDs; sensitive recipient fields are tokenized at the integration layer. Cuba Restricted List screening is run before any payout webhook is forwarded onward, and consent records — who authorized what export, when — are kept alongside every audit row so examiner questions can be answered without re-pulling raw data.

About us

OpenFinance Lab is an independent studio focused on fintech and OpenData API integration. The team has shipped production work for payment gateways, neobanks, agent networks, and protocol-analysis projects across the Americas and Europe. For Cuba-corridor work we combine US OFAC and FinCEN compliance experience with hands-on protocol analysis of consumer remittance apps, which is what makes Lindo, Remesita, and similar platforms approachable for an engineering team that cannot afford to roll its own MSB.

• Remittance, digital banking, payment gateway and protocol analysis backgrounds
• OFAC screening, FinCEN/MSB compliance reviews and consent logging
• Custom Python, Node.js, and Go SDKs with HMAC-signed webhook receivers
• End-to-end pipeline: protocol analysis → build → validation → compliance evidence
• 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

Contact

To request a quote or share your target app and integration scope, open our contact page:

Contact page