PrestaCOP API integration & OpenData services
Compliant protocol analysis and runnable source code for loan portfolio, collector, and payment data — built for microfinance operators in Colombia and Latin America.
Turn PrestaCOP loan books, collector routes, and payment histories into a queryable API
PrestaCOP is widely used by independent lenders, route-collection businesses, and small finance companies to track loans, payments, and field collectors. We turn that internal operational data — customers, balances, daily receipts, GPS routes — into structured APIs your accounting, BI, or risk-control systems can read directly, instead of forcing operators to copy data into spreadsheets.
Feature modules
Loan portfolio API
Read-only export of every active and closed loan: principal, interest schedule, instalment frequency (daily / weekly / "gota a gota" patterns), payment plan, and remaining balance. Designed so a head office can reconcile each independent collector route into a single consolidated portfolio view.
Customer master data
Customer ID, contact, address, geolocation, KYC notes, and reported-bad-customer flag. Used for cross-checking new applicants against shared blacklists and for deduplicating between branches that previously kept records on paper.
Collector & route ledger
Per-collector daily summary: receipts collected, expenses, new loans issued, payments processed, and the GPS trace while tracking is enabled. Powers commission calculation, route-coverage analytics, and field-fraud detection.
Receipt & ticket sync
Receipt records that PrestaCOP normally prints or shares via WhatsApp can be streamed as structured events (amount, customer, collector, timestamp, method) into your accounting platform — no need to retype paper tickets.
Balance sheets & profitability
Daily, weekly, and monthly profitability views derived from loans issued, capital recovered, and operating expenses. Exposed both as raw rows and as pre-aggregated KPIs for BI tools (Power BI, Looker Studio, Metabase).
Webhooks & real-time events
Push-style notifications for new payment received, loan disbursed, collector starting/ending route, and bad-ID validation alert. Lets a control-room dashboard show movements in real time, mirroring the in-app "see all movements" feature.
Data available for integration (OpenData inventory)
The table below maps each PrestaCOP data domain to its in-app source, granularity, and a typical downstream use. It is the same view we use during the discovery phase to scope a delivery.
| Data type | Source (screen / feature) | Granularity | Typical use |
|---|---|---|---|
| Loan record | "Loans" list / customer detail | Per loan, with full instalment plan | Risk control, portfolio-at-risk reporting, capital-recovery planning |
| Payment ledger | "Payment history" / receipt prints | Per payment event (amount, method, collector, timestamp) | Accounting reconciliation, cash-flow forecasting |
| Customer record | "Clients" master & bad-customer reports | Per customer (ID, contact, geolocation, status flags) | KYC reuse, deduplication, blacklist sharing |
| Collector activity | "Collectors" + GPS module | Per collector per day, plus GPS samples while tracking is on | Commission, route coverage, fraud detection |
| Cash-box / day summary | "Summary of the day" | Per route per business day | Daily P&L, audit, head-office consolidation |
| Bad-customer & certificate validation | "Validation of certificates" & reports | Per ID lookup event | Cross-company risk sharing under Habeas Data rules |
| Cloud backup snapshot | Cloud backup feature | Per snapshot (full or incremental) | Disaster recovery, parallel BI database, change-data-capture |
Typical integration scenarios
1. Daily portfolio reconciliation into ERP
Context: A regional finance company runs five collector routes through PrestaCOP and books results into an external ERP. Data involved: the loan portfolio API (outstanding balances), the day-summary endpoint, and the payment ledger. OpenData mapping: exposed as a normalized "loan account + transaction" feed similar to OpenBanking statement responses, so the ERP treats each route exactly like a bank account.
2. Field-collector oversight dashboard
Context: A microfinance operator wants live visibility into where each collector is and how much has been received in real time. Data involved: collector ledger + GPS samples + webhook events. OpenFinance mapping: the live feed becomes a "transaction notification" stream, similar to a merchant payment webhook, but scoped to in-cash field collections.
3. Bad-customer risk sharing across companies
Context: Two cooperating lenders want to know when a defaulting customer is reported by either side. Data involved: bad-customer reports + certificate validation events. Compliance mapping: exposed only with explicit data-controller agreements that respect Colombia's Financial Habeas Data regime (Law 1266 of 2008), since this concerns negative credit information.
4. BI & profitability analytics
Context: A head office runs profitability dashboards in Metabase. Data involved: balance sheets + receipts + collector expenses + day summary. OpenData mapping: data is materialized into a small warehouse (Postgres / BigQuery) with a stable schema, so reports remain valid even when PrestaCOP's internal screens change.
5. Migration / dual-running with another loan platform
Context: An operator is moving from PrestaCOP to a larger platform such as LoanPro, Nortridge, or HES LoanBox and wants to dual-run for one quarter. Data involved: cloud-backup snapshot endpoint + loan and customer master data. Integration pattern: nightly diff feed pushed to the destination platform's intake API, with a reconciliation report each morning.
Technical implementation
Authorize and refresh session
POST /api/v1/prestacop/auth/login
Content-Type: application/json
{
"tenant_id": "ancorp-co-route-07",
"operator_email": "office@example-co",
"operator_password": "<stored secret>",
"device_fingerprint": "srv-edge-01"
}
200 OK
{
"access_token": "<jwt>",
"refresh_token": "<jwt>",
"expires_in": 3600,
"scopes": ["portfolio.read", "payments.read", "collectors.read"]
}
Pull a daily portfolio statement
POST /api/v1/prestacop/portfolio/statement
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json
{
"route_id": "route-07",
"from_date": "2026-04-21",
"to_date": "2026-04-27",
"include": ["loans", "payments", "expenses"]
}
200 OK
{
"route_id": "route-07",
"loans": [ /* loan_id, customer_id, principal, balance, status */ ],
"payments": [ /* payment_id, loan_id, amount, method, collector_id, ts */ ],
"expenses": [ /* expense_id, collector_id, category, amount, ts */ ],
"page": { "next_cursor": null }
}
Real-time webhook on payment received
POST https://your-host.example/webhooks/prestacop
X-PrestaCOP-Signature: sha256=...
Content-Type: application/json
{
"event": "payment.received",
"occurred_at": "2026-04-28T15:42:11-05:00",
"route_id": "route-07",
"collector_id": "col-014",
"loan_id": "loan-9931",
"amount": 25000,
"currency": "COP",
"method": "cash",
"geo": { "lat": 4.6533, "lng": -74.0836 }
}
// Recommended: verify HMAC, dedupe by event_id,
// retry with exponential backoff on 5xx; 4xx is final.
Compliance & privacy
PrestaCOP data is mostly customer-identifiable financial information, so every integration we deliver is scoped to comply with Colombia's Habeas Data framework — Law 1581 of 2012 for general personal data and Law 1266 of 2008 for financial, credit, and commercial data. The Superintendence of Industry and Commerce (SIC) acts as the data-protection authority and, since SIC Circular 001 of 2025, has issued specific binding guidance for fintech operators around consent capture, data minimization, and processor accountability.
For exports that touch payment behavior, we additionally scope to the practice expected by the Superintendencia Financiera de Colombia for entities adjacent to credit operations. Where a deployment also serves users in the EU, we apply GDPR-style controls (purpose limitation, retention, and Data Subject Access Request endpoints) on top. Each delivery includes a written data-flow map, a retention matrix, and a consent-record schema so the operator can demonstrate compliance during a SIC inspection.
Data flow / architecture
A typical pipeline looks like this:
- Client app / cloud backup — PrestaCOP on collector phones plus the operator's PrestaCOP cloud backup.
- Ingestion / API gateway — Our adapter authenticates with the operator's account, pulls scoped data, and verifies signatures on incoming webhooks.
- Storage — Normalized tables (loans, payments, customers, collectors, expenses) in Postgres, with an append-only event log for change-data-capture.
- Analytics / API output — REST or GraphQL endpoints, scheduled CSV exports, and BI connectors (Metabase, Power BI, Looker Studio) sit on top.
Market positioning & user profile
PrestaCOP is a B2B Android application primarily used in Colombia and adjacent Spanish-speaking markets by independent lenders, family-run finance shops, route-collection ("gota a gota"-style) operators, and small cooperatives. Operator subscriptions are sold at roughly 1.66 USD per month or 16.99 USD per year, which signals a long tail of small operators rather than a few large enterprises — and that shapes integration work toward lightweight, multi-tenant patterns rather than heavyweight per-client custom builds. Recent activity in 2024 around formalizing informal lending in Colombia (such as Bogotá's program to offer cheaper credit as an alternative to "gota a gota") has pushed many of these operators to start exporting cleaner books and adopting digital records, which is exactly where API-driven data extraction becomes useful.
Screenshots
Tap any image to enlarge. These are from the official Google Play listing and illustrate the screens whose data becomes available through integration.
Similar apps & integration landscape
Operators using PrestaCOP often evaluate or run alongside other loan-management and microfinance platforms. The list below describes how each one fits into the broader OpenData / OpenFinance integration landscape — these are part of the ecosystem we routinely build adapters for.
What we deliver
Deliverables checklist
- API specification (OpenAPI 3.1 / Swagger), one route per data domain
- Protocol & auth-flow report (token chain, refresh, signing)
- Runnable source code (Python + Node.js reference clients) for portfolio, payments, collectors, and webhooks
- Automated tests (golden-file responses, signature verification, retry logic)
- Habeas Data compliance pack: data-flow map, retention matrix, consent-record schema
Engagement models
Source code delivery from $300 — runnable API source plus documentation; pay only after delivery and acceptance.
Pay-per-call hosted API — connect to our managed endpoint, pay per request, no upfront fee. Suited for teams that prefer usage-based pricing or do not want to host the integration themselves.
About us
We are an independent technical service studio focused on App interface integration and authorized API delivery. Our engineers come from microfinance back-office, mobile reverse engineering, payment-gateway integration, and cloud platform backgrounds, and we have shipped integrations across Latin America, Southeast Asia, and EMEA.
- Microfinance, route-collection, digital banking, and cross-border payments
- Authorized protocol analysis, OpenAPI-spec design, and SDK delivery
- Python / Node.js / Go reference code with test harnesses
- Source code delivery from $300 — runnable code and full documentation, paid after acceptance
- Pay-per-call API billing — usage-based pricing on our hosted endpoints, no upfront fee
Contact
Tell us your target app and what data or scenario you need. We'll reply with a scoped proposal, sample payloads, and a delivery timeline.
Engagement workflow
- Scope confirmation: which PrestaCOP data domains and scenarios are in scope (portfolio, payments, collectors, webhooks).
- Protocol analysis & API design (2–5 business days, complexity-dependent).
- Build and internal validation against a sandbox tenant (3–8 business days).
- Documentation, sample clients, and test cases (1–2 business days).
- Typical first delivery: 5–15 business days; cloud-backup permission turnarounds may extend the timeline.
FAQ
What do you need from me to start?
How do you handle compliance with Colombia's Habeas Data?
Is the integration source code mine to keep?
📱 Original app overview (PrestaCOP — appendix)
PrestaCOP (package colombia.ancorp.prestacop) is a Colombia-built Android application for managing loans and field collections. It is aimed at small lenders, family-run finance shops, and route-collection operators who need to track customers, payment plans, and collector activity from a phone or tablet.
Highlights from the official Google Play description:
- Work with several collectors and an unlimited number of collectors per operator.
- Print receipt tickets and share them through social networks.
- Cloud backup of customer data; web version to manage clients and collectors from a browser.
- Smart search and easy-to-use interface; ad-free experience.
- Balance sheets to evaluate company profitability (paid feature).
- GPS tracking of collectors with the ability to disable tracking when the collector finishes the route (paid feature).
- Real-time visibility into amounts received, expenses, loans, and payments per collector; map view of the collector's location.
- Payment history, simple settings, summary of the day, and a cash box that does not require closure.
- Restrictions for collectors so they cannot edit or delete information.
- Validation of certificates and bad-customer reports so other companies can identify a defaulting customer; alerts when a reported ID is validated.
- Subscription pricing of approximately 1.66 USD per month or 16.99 USD per year, with Google Play in-app purchase support.
This page describes how the studio above can integrate with that operational data through authorized APIs; PrestaCOP and its publisher remain the property of their respective owners.