Mi Pass API & Open Finance Integration

Corporate reconciliation and ERP

Companies using Banco de Chile for operations need movements and balances inside their ERP. We deliver an API layer that consumes ApiStore Movimientos y Saldos (with client ID/secret and Mi Pass–backed authorization where required), returning transaction lists and balance snapshots. Data maps to Open Finance: structured movements with date, amount, type, and account; you feed your reconciliation engine or general ledger. Consent and retention follow Chile’s SFA and your policies.

Real-time treasury and notifications

Treasury teams need immediate visibility of incoming and outgoing transfers. We implement webhook or polling consumption of ApiStore Notificaciones and Movimientos notificaciones so your system receives transfer and payment events in real time. Fields typically include amount, date, counterparty, and status—suitable for cash positioning and liquidity dashboards.

Payment and deposit automation

Automating payments to suppliers and deposits via ApiStore Pagos and Abono en línea reduces manual work and errors. We deliver request/response integration and error-handling patterns (e.g. idempotency, retries) so your back office can initiate payments and deposits programmatically, with full audit trails aligned with local regulations.

Open Banking aggregation (Floid-style)

Where direct ApiStore access is not in scope, aggregators like Floid provide standardized access to Banco de Chile accounts, transactions, and income data. We can implement or document the consent and API flow (products, balances, transactions) so your app offers a unified view across Banco de Chile and other Chilean banks (Santander Chile, Scotiabank, BCI, etc.) under the SFA.

Compliance and audit reporting

Banks and regulated entities need exportable authorization and transaction logs. Our protocol analysis documents Mi Pass authorization events and session handling; combined with ApiStore or aggregator data, you get a coherent trail for CMF and internal audit—always with explicit consent and minimal retention.

ApiStore auth (pseudo)

// ApiStore uses client_id + client_secret (pseudo)
POST /oauth/token
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials
  &client_id=<CLIENT_ID>
  &client_secret=<CLIENT_SECRET>

Response 200: { "access_token": "...", "expires_in": 3600 }
Response 401: { "error": "invalid_client" }
// Mi Pass / user auth may be required per product

Movimientos y Saldos (pseudo)

// Movements and balances (pseudo, ApiStore)
GET /api/movimientos-saldos?account_id=xxx&from=2025-01-01&to=2025-03-12
Authorization: Bearer <ACCESS_TOKEN>

Response: {
  "account_id": "xxx", "balance": { "amount": 1234567, "currency": "CLP" },
  "movements": [ { "date": "...", "amount": 1000, "type": "TRANSFER", "description": "..." } ]
}
Error 429: rate limit; retry with backoff

Webhook / notification (pseudo)

// Incoming transfer/payment notification (pseudo)
POST <YOUR_WEBHOOK_URL>
Content-Type: application/json
X-Signature: <HMAC or similar>

{
  "event": "transfer.received",
  "account_id": "xxx", "amount": 50000, "currency": "CLP",
  "date": "2025-03-12T10:00:00Z", "counterparty": "..."
}
// Verify signature; respond 200 quickly; process async

Deliverables

• API specification (OpenAPI / Swagger) for movements, balances, notifications, payments
• Protocol and auth flow analysis (Mi Pass, ApiStore client credentials, aggregator consent)
• Runnable API source code (Python / Node.js) for the agreed endpoints
• Test scripts and interface documentation
• Compliance notes (Chile Fintec Law, CMF SFA, consent, retention)

Key integration areas

Authorization protocol (Mi Pass), Movimientos y Saldos, Notificaciones and webhooks, Pagos and Abono en línea, and optional aggregator integration (e.g. Floid). We support Android and iOS protocol analysis and deliver source code you can host and extend.

About us

We are a technical service studio specializing in app interface integration and authorized API integration. We provide protocol analysis, interface refactoring, Open Data integration, and third-party interface integration, plus automated data scripting and interface documentation. Our team has years of experience in mobile and fintech; we serve global clients with compliant, professional solutions. Services start at $300, with an option to deliver results first and pay upon satisfaction.

• Banking and fintech: transaction records, statement queries, payment integration
• Compliant, lawful implementations to meet local and privacy requirements
• Android and iOS; ready-to-use API source code, docs, and test plans

Contact

For inquiries, quotes, or to submit your target app and requirements, please use the link below:

Contact us

Process

1. Confirm requirements: integration scenario and interface needs (e.g. movements, balances, notifications, payments).
2. Protocol analysis and interface design (2–5 business days, depending on complexity).
3. Development and internal validation (3–8 business days).
4. Delivery of documentation, examples, and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; complex or multi-party approval may take longer.

FAQ

What do I need to provide?

How long until delivery?

How do you ensure compliance?