MI FONDO de Fiducia API integration services (Ecuador investment funds & OpenFinance)

1. Account & KYC bridge

Mirror the in-app authorization handshake (cedula + password + OTP, with biometric on supported devices) into an OAuth-style token your backend can refresh. Use it to bind a MI FONDO investor to your CRM record without storing raw credentials.

2. Fund catalog & NAV sync

Daily NAV (valor cuota) for each fund — Mi Ahorro (short term), Mi Futuro (medium term), Mi Retiro (long-term retirement) and the Fondo Inmobiliario — with historical series for charting and benchmark calculations.

3. Contribution & redemption engine

Programmatic aporte calls from $25, automatic monthly debit scheduling, and rescate (partial or total) requests that honor each fund’s notice period. Useful for goal-based reconciliation: tuition, retirement, or down-payment tracking.

4. Statement & portfolio APIs

Per-fund and consolidated movement statements with date ranges, paging and a stable transaction ID. Drives ERP imports, advisor dashboards and Excel-based tax reporting for the SRI (Servicio de Rentas Internas).

5. Goal & simulator data

The app guides users through 4 onboarding steps and simulators (education, retirement, travel, home). We expose the simulator inputs/outputs as a typed API so external planners and robo-advisors can replicate FIDUCIA projections.

6. Health-plan extension (SALUD S.A.)

Since the 2024 product expansion, MI FONDO sells medical and dental plans from $5.25/month with SALUD S.A. backing. Policy issuance, premium status and claim history can be exposed as a complementary insurance API alongside the investment data.

Scenario 1 — Wealth dashboard aggregation

An Ecuadorian fintech wants to show an investor a consolidated view of cash, mutual funds and term deposits. We mirror MI FONDO’s Mi resumen screen as a GET /portfolio endpoint that returns a list of participaciones with current USD value, last NAV, and 30/90/365-day return. Mapped to OpenFinance, this is a classic “account information” flow over an authorized session.

Scenario 2 — ERP reconciliation for SMEs

A small business holds reserve liquidity in Mi Ahorro. Their ERP needs to reconcile each monthly aporte against the bank ACH debit. We expose GET /movements?from=&to=&fund= with paging and a stable transaction_id, so the ERP can match transfers automatically and feed Ecuadorian accounting requirements (formato XML/SRI compatible).

Scenario 3 — Robo-advisor goal tracking

A goal-based planning service wants to update progress in real time when an investor adds a child’s education goal in MI FONDO. We listen to the goal-creation event, fetch GET /goals/{id} with target amount and monthly aporte, then sync to the planner. This maps to OpenData “event sharing” on top of an OpenFinance account.

Scenario 4 — Tax & SRI reporting

End-of-year tax certificates from FIDUCIA must be packaged for the Servicio de Rentas Internas. The integration delivers GET /tax-certificates?year=2025 returning a signed PDF and a structured JSON twin so an accountant’s software can ingest both — covering investment income and any health-plan deductions exposed via the SALUD S.A. extension.

Scenario 5 — Internal audit & risk control

FIDUCIA-aligned compliance teams or large family-office clients want an immutable feed of contributions and redemptions for audit. We push every movement.created event to an internal Kafka topic with masked PII, supporting downstream BI (Looker, Power BI) and risk control without re-deriving data from screenshots.

Auth — investor login & session

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

{
  "id_type": "CEDULA",
  "id_number": "1712345678",
  "password": "<hashed>",
  "device_id": "a8f5...c3",
  "otp": "482910"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_9b2c...",
  "expires_in": 3600,
  "investor_id": "INV-0027431",
  "kyc_level": "FULL"
}

Statement — movement query

GET /api/v1/mifondo/movements
  ?fund_code=MI_AHORRO
  &from=2025-09-01
  &to=2026-04-28
  &page=1&size=50
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "page": 1, "total": 137,
  "items": [
    {
      "transaction_id": "TX-MA-0001872",
      "type": "APORTE",
      "amount": 25.00,
      "currency": "USD",
      "fund_code": "MI_AHORRO",
      "units": 24.7831,
      "nav": 1.0088,
      "channel": "AUTO_DEBIT",
      "executed_at": "2026-04-05T13:22:11-05:00",
      "status": "SETTLED"
    }
  ]
}

Webhook — redemption status

POST https://your-app.example/webhooks/mifondo
X-MIFONDO-Signature: t=1714291200,v1=8a52...

{
  "event": "redemption.status_changed",
  "investor_id": "INV-0027431",
  "transaction_id": "TX-MR-0009321",
  "fund_code": "MI_FUTURO",
  "amount": 1500.00,
  "currency": "USD",
  "status": "PROCESSING",   // or APPROVED, SETTLED, REJECTED
  "expected_settlement": "2026-05-02",
  "occurred_at": "2026-04-28T09:15:42-05:00"
}

# Recommended: verify HMAC signature, then idempotency-check transaction_id
# before persisting. Honor each fund’s reglamento on notice periods.

Deliverables checklist

• OpenAPI / Swagger spec covering login, portfolio, movements, NAV, redemption
• Protocol & auth flow report (token chain, OTP, device fingerprint, signature)
• Runnable source code (Python or Node.js) for the core flows
• Webhook reference implementation with HMAC verification
• Automated tests (happy path + error states) and Postman collection
• Compliance guidance aligned with Ecuador’s LOPDP and Superintendencia rules
• Optional: sample BI dashboard for portfolio & movements

Engagement workflow

1. Scope confirmation: which MI FONDO surfaces (investments only, or also SALUD S.A. health plans).
2. Protocol analysis & API design (2–5 business days).
3. Build & internal validation against test investor (3–8 business days).
4. Documentation, samples and test plan (1–2 business days).
5. Typical first delivery: 5–15 business days; regulatory or KYC dependencies may extend.

About us

We are an independent technical studio specialized in App interface integration and authorized API integration. Our engineers come from banks, payment processors, OpenFinance vendors and protocol-analysis backgrounds. For Ecuadorian investment apps like MI FONDO de Fiducia, we combine:

• Hands-on protocol analysis on Android & iOS builds
• OpenFinance and Open Banking patterns adapted to Ecuador’s emerging framework
• Custom Python / Node.js / Go SDKs and test harnesses
• End-to-end pipeline: protocol analysis → build → validation → compliance
• Source code delivery from $300 — runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted MI FONDO connector and pay only per call, no upfront cost; ideal for teams that prefer usage-based pricing

Contact

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

Contact page

We can also work under NDA and against documented public/authorized APIs only — no unauthorized access.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Can you cover the SALUD S.A. health-plan extension?

Why an integration studio (vs. doing it in-house)

Building one MI FONDO connector means handling Android + iOS quirks, certificate pinning, OTP flows, token rotation and subtle changes between fund types (Mi Ahorro vs. Mi Retiro vs. Inmobiliario). Doing it once for one team is a multi-month project; doing it as a packaged service compresses it to days, with a documented surface that survives app updates.

For finance and ops teams, that means moving faster from “we have an idea” to “we have transactional data flowing into our dashboard.”