Kamina API integration services (OpenFinance & financial wellness)

1. Partner-bank embedded wellness

A regulated bank in Mexico embeds the Kamina financial wellness index directly into its mobile app's "Cuida tu salud financiera" tab. Data & APIs: POST /v1/diagnosis/run returns the wellness score, contributing factors and an action plan, while GET /v1/alerts?since=… streams new prevention alerts. OpenFinance mapping: the score acts as a derived OpenFinance attribute that the bank can attach to its existing PFM and credit decisioning records under Mexico's Ley Fintech consent rules.

2. Underwriting affordability check

A digital lender enriches its credit application by pulling the applicant's Kamina debt portfolio and 90-day expense history. Data & APIs: GET /v1/debts returns each open balance with issuer and APR, GET /v1/expenses?from=…&to=… returns categorized transactions. OpenFinance mapping: the debt and expense feeds combine with bank-account aggregator data (e.g. Belvo) to compute a true debt-to-income ratio that meets the lender's affordability guidance.

3. Collections deflection

A collections team subscribes to Kamina's prevention-alert webhook so that, the moment a customer enters a "high stress" risk band, an empathic outreach playbook is triggered instead of a hard-call. Data & APIs: webhook event alert.created with payload {user_id, risk_band, contributing_factors, suggested_action}. OpenFinance mapping: aligns with consumer-protection guidance that emphasises proactive support before delinquency.

4. Cross-LATAM CRM sync

A multi-country fintech operating in Ecuador, Peru and Colombia centralises Kamina wellness signals in its CRM to coordinate financial-coaching campaigns. Data & APIs: nightly batch via POST /v1/exports/wellness producing a signed S3 URL; coach interaction summaries via GET /v1/coach/sessions. OpenFinance mapping: wellness data is treated as user-derived data, kept separate from raw transaction data so consent revocation does not invalidate other sources.

5. Regulatory reporting & audit

A bank runs a quarterly report on how prevention alerts converted into resolved cases. Data & APIs: GET /v1/reports/prevention?period=2026Q1 returns aggregate counts, segments and outcome metrics. OpenFinance mapping: the dataset is shaped to feed financial-inclusion KPIs that supervisors increasingly request for OpenFinance pilots.

Authentication & consent

POST /v1/auth/consent
Content-Type: application/json

{
  "client_id": "of_lab_demo",
  "user_external_id": "USR_42891",
  "scopes": ["wellness.read", "debts.read", "expenses.read"],
  "country": "MX",
  "consent_text_version": "2026-05-01"
}

200 OK
{
  "access_token": "ey...",
  "refresh_token": "rf...",
  "expires_in": 3600,
  "consent_id": "cns_8a1c..."
}

Financial wellness diagnosis

GET /v1/diagnosis/latest
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "user_id": "USR_42891",
  "score": 64,
  "band": "amber",
  "trend_30d": -3,
  "factors": [
    {"name": "debt_to_income", "weight": 0.34, "value": 0.51},
    {"name": "expense_volatility", "weight": 0.21, "value": 0.18},
    {"name": "savings_ratio", "weight": 0.18, "value": 0.04}
  ],
  "next_review_at": "2026-06-08"
}

Debt & expense export

GET /v1/exports/debts?format=json
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "as_of": "2026-05-08T14:00:00-05:00",
  "items": [
    {"issuer": "Banco Pichincha", "type": "credit_card",
     "balance": 1240.55, "currency": "USD",
     "apr": 0.42, "due_date": "2026-05-25"},
    {"issuer": "Diners Club", "type": "installment",
     "balance": 800.00, "currency": "USD",
     "apr": 0.31, "due_date": "2026-05-18"}
  ],
  "page": {"next_cursor": null}
}

# Webhook (alert.created)
POST <your_callback>
{
  "event": "alert.created",
  "user_id": "USR_42891",
  "risk_band": "red",
  "contributing_factors": ["missed_due_date", "expense_spike_food"],
  "suggested_action": "soft_outreach_v2"
}

Regulatory alignment

Kamina operates in a region where OpenFinance is moving from voluntary to supervised. Our integrations align with Mexico's Ley para Regular las Instituciones de Tecnología Financiera (Ley Fintech, 2018) for consent and data-sharing, with Ecuador's monetary and financial code where Kamina is headquartered, and with Brazil's LGPD when users are present. For consumer-data protection we follow Mexico's LFPDPPP and, where European stakeholders are involved, GDPR Article 6 lawful-basis mappings.

Privacy controls shipped by default

• Versioned consent strings with revocation endpoint and audit log
• Field-level data minimization (a buyer cannot pull more than its scopes allow)
• Tokenized user IDs across environments — no national IDs in payloads
• Configurable retention windows with automated purge
• Rate-limited webhooks with HMAC signatures and replay protection

YNAB (You Need A Budget)

A long-running zero-based budgeting app holding category-level spending plans and goal balances. Users who also work with YNAB often need unified expense exports across both platforms so a single dashboard can show plan-vs-actual.

Goodbudget

Envelope-based budgeting app with shared household budgets, debt tracker and sync across devices. Goodbudget's debt module pairs well with Kamina's APR-aware debt portfolio for couples-coaching scenarios.

Monefy

A widely installed expense tracker with simple categorized spending records. When users move from Monefy to Kamina, our migration helper can ingest a Monefy CSV export and seed Kamina's expense API.

Buxfer

Web-first personal finance tool with bank sync for Mexican institutions. Buxfer's transaction feed is a natural complement to Kamina's wellness index — accounts go in, score comes out.

Money Manager — Budget Planner

One of Mexico's top-downloaded finance apps in 2025; primarily local, manual entry. Pairing it with Kamina lets users keep their familiar entry UI while gaining AI prevention alerts on top.

Waleeto

A LATAM-focused expense tracker with AI-powered budgeting and multi-currency support. Sits in the same wellness-coaching segment as Kamina, with Waleeto leaning toward planning and Kamina toward prevention.

Mint

Historic US PFM that defined the category. A reference architecture point — many partner banks ask "we want a Mint-style experience but with Kamina's prevention logic," which is exactly the embedded pattern we deliver.

Fintonic

Spanish-language PFM popular in Spain and Mexico, blending bank aggregation with credit offers. Customers often pull Fintonic transaction feeds into the same OpenFinance bus that consumes Kamina wellness scores.

Belvo

A LATAM Open Finance API platform, not a consumer app, but central to the same ecosystem. Belvo provides raw bank-account data while Kamina contributes the derived wellness layer; many integrations call both.

Kamino

A separate financial-management product (different company) often searched alongside Kamina. We disambiguate the two during scoping so naming-similar searches do not confuse the integration brief.

Deliverables checklist

• API specification (OpenAPI / Swagger) for wellness, debts, expenses and webhooks
• Protocol and auth flow report (OAuth-style consent, token rotation, device binding)
• Runnable source code in Python and Node.js (Go and Kotlin available on request)
• Postman collection and contract-test suite that runs in your CI
• Compliance pack: consent template, retention policy, scope-to-lawful-basis mapping
• Optional embedded SDK for partner-bank mobile apps (Mastercard Start Path style)

About us

OpenFinance Lab is an independent studio focused on fintech and OpenData API integration. Our team includes engineers from banks, payment networks, mobile-protocol analysis and cloud platforms. We have shipped end-to-end financial APIs across LATAM, EMEA and Southeast Asia, and we work under either source-code delivery from $300 or pay-per-call hosted billing — clients pick whichever lifecycle fits.

• Source code delivery from $300 — runnable API source + full documentation; pay after acceptance.
• Pay-per-call API billing — hosted endpoints, no upfront cost, ideal for usage-based pricing teams.
• Full pipeline: protocol analysis → build → validation → compliance.

Contact

For quotes or to submit your target app and requirements, open our contact page:

Contact page

Engagement workflow

1. Scope confirmation — pick the data classes you need (wellness, debts, expenses, alerts, coach signals).
2. Protocol analysis & API design (2–5 business days).
3. Build, internal validation and contract tests (3–8 business days).
4. Documentation, code samples, Postman collection (1–2 business days).
5. Typical first delivery: 5–15 business days; bank-side approvals can extend timelines.

FAQ

What Kamina data can I integrate via OpenFinance APIs?

How long does a Kamina API delivery take?

How do you stay compliant with Latin American data laws?

Can you replicate the Kamina + Mastercard Start Path embedded model?