Vana - Préstamos confiables: API integration & OpenFinance data services
Authorized protocol analysis, alternative-data scoring exports, and runnable lending APIs for Honduras and the wider Central American micro-credit ecosystem.
Bring Vana loan, KYC, and repayment data into your back-office, in a compliant way
Vana is a non-bank lender registered with Honduras' SAR and URMOPRELAFT, a member of the Honduran Fintech Association (AFINH), and one of the top finance apps on Google Play in Honduras. Its platform handles loan offers up to L 7,000 with 90-day to 12-month terms, electronic-transfer disbursement, and receipt-based repayment. We connect that workflow to your stack with authorized OpenData adapters.
Feature modules
Each module is shipped as documented endpoints, runnable Python or Node.js source code, and a test harness. You pick only what you need; modules can be combined to cover a full origination-to-recovery cycle.
Loan application API
Programmatic mirror of the in-app credit application: applicant profile, requested amount (L 700–L 7,000), term selection (90–360 days), product code, decision response, approval timestamp.
Use case: replicating Vana's "response in minutes" flow into a partner channel (e.g. agent-assisted onboarding) while keeping a unified loan record.
Repayment & receipt API
Captures cash-deposit and electronic-transfer events plus receipt-photo references so the lender ledger reconciles with bank-side movements. Returns settled, pending, and reversed states.
Use case: feeding accounting (SAR filings) and triggering the next-loan eligibility logic Vana exposes after on-time repayment.
KYC & profile sync
Exports the verified identity profile and AML/PEP screening status used during onboarding (consistent with URMOPRELAFT obligations) so it can populate downstream KYC vaults without re-asking the customer.
Use case: a credit bureau or a partner lender that wants to reuse Vana's verified KYC for product cross-sell.
Credit-limit & product-history API
Tracks how a borrower's limit moves toward L 7,000 across cycles, including disbursement fees (L 65–L 2,106 + VAT) and effective APR up to 32.4%, so analytics teams can compute lifetime value and risk-adjusted yield.
Use case: monthly cohort dashboards, LTV models, and refi-offer triggering.
Alternative-data signals
Vana publicly states it uses non-traditional data and ML to underwrite users with no formal banking relationship. This module exposes an authorized, consented copy of the device, behavioral, and channel-source signals fed into scoring — never raw PII without consent.
Use case: cross-portfolio risk uplift, fraud rings detection, and reusable underwriting features.
Webhook & event bus
Real-time push for application_submitted, decision_returned, disbursement_completed, repayment_received, limit_increased, account_blocked. Configurable retries, signed payloads, idempotency keys, and dead-letter handling.
Use case: pushing fresh events into a streaming pipeline (Kafka / PubSub) or a Slack/Teams ops channel.
Data available for integration
The table below catalogs structured data the Vana app holds and how an OpenData adapter typically surfaces it. Granularity reflects fields and refresh rates we have implemented for similar Honduran and LatAm lenders.
| Data type | Source (screen / feature) | Granularity | Typical use |
|---|---|---|---|
| Loan applications | "Apply" / credit application screen | Per-application: amount, term, product, applied_at, decision | Funnel analytics, conversion uplift, credit-policy backtesting |
| Credit decisions & limit moves | Decision response & "Mi crédito" panel | Per-decision: score band, approved amount, max limit, expiry | Risk monitoring, cohort drift detection, regulatory MI |
| Disbursement events | Bank-account credit confirmation | Per-event: net amount, fees (L 65–L 2,106), VAT, channel | Treasury reconciliation, settlement timing analytics |
| Repayment & receipts | "Pay" screen + receipt-photo upload | Per-event: due date, paid amount, channel, receipt URL hash | Collections, on-time-payment scoring, accounting feeds |
| KYC / AML profile | Onboarding identity flow | Per-customer: ID type, screening result, risk tier, last_review | URMOPRELAFT reporting, partner KYC reuse |
| Customer support events | "Soporte" ticketing & chat | Per-ticket: topic, status, sentiment, agent_id | Voice-of-customer dashboards, churn-risk signals |
| Device & behavior signals | Background SDK telemetry (consented) | Per-session: device fingerprint, install age, in-app journey | Anti-fraud rules, alternative-data scoring features |
Typical integration scenarios
1. Lender-to-CRM full loop
Business context: a partner credit union wants to track Vana borrowers who are also their customers, without duplicating onboarding.
Data & APIs: KYC sync + loan applications + repayment ledger, joined on national ID hash.
OpenFinance mapping: aligns with the LatAm "data portability with consent" pattern advanced in Brazil's Open Finance and Colombia's June 2025 mandatory framework — applied conservatively for Honduras pending local rules.
2. Accounting and SAR-aligned reporting
Business context: finance team needs a clean ledger of disbursements, fees (L 65–L 2,106), VAT, and reversals for monthly closing and SAR submissions.
Data & APIs: disbursement_events + repayment + receipt metadata pushed into the ERP (Odoo, SAP B1, NetSuite) via signed webhooks.
OpenFinance mapping: matches the "transactions / statements" data category used in OpenBanking specs (Brazil OpenFinance §IV, UK CMA9), adapted to Honduran non-bank lender posture.
3. Alternative-data scoring exchange
Business context: a regional fintech consortium wants to share consented underwriting features (device age, repayment cadence, channel mix) to reduce default in thin-file segments.
Data & APIs: alternative-data signals export + credit-limit history, surfaced as feature vectors over a versioned API.
OpenFinance mapping: an Open Finance "credit / risk data" adjacency, consistent with how Latin American open-finance roadmaps treat lending data once payment data is in place.
4. Embedded credit in partner apps
Business context: a retail or remittance app wants to offer "pay later" credit using Vana's underwriting in the background.
Data & APIs: loan_application_create + decision_returned webhook + disbursement_status, wrapped behind the partner's UI.
OpenFinance mapping: equivalent to BaaS / embedded finance flows, with Vana acting as the regulated lender of record under SAR / URMOPRELAFT.
5. Cross-border portfolio analytics
Business context: a holding company runs lenders in Honduras, Guatemala, Peru, and the Dominican Republic and wants a unified portfolio view.
Data & APIs: country-tagged exports of applications, repayments, and credit-limit moves, normalized into a single schema.
OpenFinance mapping: not regulated cross-border, but uses the same OpenData abstractions so the team can later plug into formal Open Finance APIs as those markets mature.
Technical implementation
Auth: token exchange (pseudocode)
POST /api/v1/vana/auth/token
Content-Type: application/json
{
"client_id": "studio-partner-01",
"client_secret": "<OPAQUE>",
"scope": "loans.read repayments.read kyc.read",
"country": "HN"
}
200 OK
{
"access_token": "eyJhbGciOi...",
"expires_in": 1800,
"token_type": "Bearer",
"consent_id": "csnt_2025_HN_4a91"
}
Loan application export (pseudocode)
GET /api/v1/vana/loans?country=HN&from=2026-01-01&to=2026-04-28&status=approved
Authorization: Bearer <ACCESS_TOKEN>
X-Consent-Id: csnt_2025_HN_4a91
200 OK
{
"page": 1, "page_size": 50, "total": 712,
"items": [
{
"loan_id": "ln_HN_8821",
"applied_at": "2026-04-12T14:33:11Z",
"amount_requested": 7000.00,
"amount_approved": 5000.00,
"currency": "HNL",
"term_days": 90,
"product_code": "VN-HN-90D",
"fees_total": 749.00,
"vat": 112.35,
"apr_max_pct": 32.4,
"decision": "APPROVED",
"limit_max_hnl": 7000.00
}
]
}
Repayment webhook (pseudocode)
POST <partner_url>/webhooks/vana
X-Vana-Signature: t=1714291800,v1=8c1a...
Idempotency-Key: evt_rp_91a4b2
{
"event": "repayment_received",
"loan_id": "ln_HN_8821",
"paid_at": "2026-04-27T18:02:55-06:00",
"amount_paid_hnl": 7938.00,
"channel": "ELECTRONIC_TRANSFER",
"receipt_ref": "rcpt_2026_HN_18f3",
"status": "SETTLED",
"next_loan_eligible": true
}
// Verify HMAC: signature == HMAC_SHA256(secret, "<timestamp>.<raw_body>")
// On 5xx the platform retries with exponential backoff up to 24h.
Error handling & idempotency
All endpoints surface a stable error envelope: {"code":"RATE_LIMITED","message":"...","retry_after":12}. Retries on 429 / 5xx use jittered exponential backoff. Every mutating call accepts an Idempotency-Key so partners can safely replay disbursement and repayment events without double-counting.
For long-running exports we provide both pagination (cursor + total) and an async job mode (job_id, polling endpoint) so large historical pulls do not block the integration.
Compliance & privacy
Vana is registered with Honduras' Servicio de Administración de Rentas (SAR) as a non-bank lender, with the Unit Responsible for the Registration, Monitoring, and Prevention of Money Laundering and Terrorism Financing (URMOPRELAFT), and is a member of the Honduran Fintech Association (AFINH), which works alongside the National Banking and Insurance Commission (CNBS). Any integration we deliver respects these obligations.
- AML / CTF (URMOPRELAFT): KYC fields, sanction-list outcomes, and transaction monitoring evidence are preserved with audit trails.
- SAR tax reporting: disbursement, fee, and VAT events are exported in formats friendly to Honduran tax submissions.
- Privacy: aligned with Vana's published privacy policy (cdn.vana.hn/privacy-policy/index.html) — consent IDs, scoped tokens, and data-minimization defaults; PII is redacted unless the partner has lawful basis.
- Open Finance benchmarks: where local rules are still in development, we follow Brazilian Open Finance and Colombia's June 2025 mandatory framework as design references, so integrations age gracefully when Honduran rules formalize.
- GDPR-style hygiene: deletion endpoints, consent revocation, and data-subject access requests are first-class, even when not strictly required locally.
Data flow / architecture
A production deployment for a partner usually looks like this:
- 1. Vana mobile client & backend — origin of loan, repayment, and KYC events (com.vana.hn on Android).
- 2. Authorized adapter / API gateway — token exchange, scope enforcement, consent-id stamping, request logging.
- 3. Streaming bus / queue — Kafka, PubSub, or SQS; carries decision_returned, disbursement_completed, repayment_received events with retries and DLQ.
- 4. Storage & analytics — partitioned warehouse (BigQuery, Snowflake, or Postgres) for reconciliation, BI dashboards, and risk feature stores.
- 5. Outbound APIs / webhooks — partner CRM, ERP, or Slack/Teams ops channels consume normalized data.
We deliver the adapter, schemas, IaC for the queue and warehouse landing, and a runnable reference partner consumer.
Market positioning & user profile
Vana is one of the leading finance Android apps in Honduras and a notable LatAm micro-credit player, with parallel operations in Guatemala, Peru, and the Dominican Republic. Honduras itself has roughly 3.2 million digital-payment users and a growing personal-finance management segment, but bank-account penetration is among the lowest in Central America — exactly the underserved profile Vana targets with non-traditional data and ML-based scoring.
End users skew toward Android-first, mobile-only borrowers seeking small, short-term loans (L 700 to L 7,000) for working capital, household needs, or bridging income gaps. The app's "pay on time → bigger limit" mechanic creates a long-tail engagement loop, and partners typically integrate to reuse this verified borrower base for cross-sell (insurance, BNPL, remittances) or to feed data into broader regional risk consortia.
Screenshots
Click any thumbnail to enlarge.
Similar apps & integration landscape
Vana sits inside a wider Latin American micro-credit and digital-banking ecosystem. The apps below come up in the same searches as Vana when users compare Honduran or LatAm lending options, and they are common neighbors in partner stacks. Our team can apply the same OpenData approach to most of them, so portfolios that mix several brands can be unified under one schema.
About our studio
We are an independent technical studio specializing in App interface integration, authorized API integration, and OpenData / OpenFinance / OpenBanking adapters. Our team has hands-on experience in mobile applications and fintech across LatAm, EU, and APAC.
- Protocol analysis of Android and iOS apps, with a strong record on Spanish-language LatAm fintech stacks.
- Authorized API integrations for lending, payments, e-commerce, hospitality, and OTT clients.
- Compliance-first delivery: we map every integration to local rules (SAR / URMOPRELAFT for Honduras, plus Open Finance references from Brazil and Colombia).
- Two engagement models — source code from $300, paid after satisfaction, or pay-per-call hosted API with no upfront fee.
- Deliverables: OpenAPI/Swagger spec, runnable Python/Node.js source, automated tests, deployment guide, and a compliance memo.
Contact
Send us your target app (Vana - Préstamos confiables in this case), the data scope you need, and any existing credentials or sandbox access. We will respond with a fixed-price quote or a pay-per-call plan.
For Vana itself, end users can reach the operator at soporte@vana.hn or vana.hn — the studio is independent and only provides integration services on top of authorized data.
Engagement workflow
- Scope confirmation: which Vana data (loans, repayments, KYC, alt-data), which markets (HN, GT, PE, DO), and which destination systems.
- Authorization & legal review: consent flows, scopes, retention windows, and SAR/URMOPRELAFT alignment.
- Protocol analysis & adapter design (typically 3–6 business days).
- Build, internal validation, and load testing (4–9 business days).
- Documentation, sample partner consumer, automated tests (1–2 business days).
- Handover, support window, and optional pay-per-call hosting.
FAQ
What do you need from me to start?
Is this a "scraper"?
How fast is delivery?
Do you cover Vana's Guatemala, Peru, and Dominican Republic operations?
What happens if Honduras formalizes Open Finance?
📱 Original app overview — Vana - Préstamos confiables (appendix)
Vana - Préstamos confiables (package: com.vana.hn) is a Honduran mobile lending app operated by Vana, a fintech originally founded in Guatemala that now also serves Peru and the Dominican Republic. The app lets users apply for cash loans up to L 7,000 directly from their phone, receive a credit decision in minutes, and have the money disbursed into their bank account.
How it works (per the app description):
- Complete the credit application from the app and receive a response in minutes.
- Receive the credit directly into your bank account.
- Pay on time to gradually unlock a larger credit limit, up to L 7,000.
Repayment options: deposit cash or send an electronic transfer to one of Vana's bank accounts, then upload a photo or screenshot of the receipt inside the app. Once payment is confirmed, the next loan can be requested.
Loan structure: repayment terms range from 90 days to 12 months depending on the customer and approved product. The maximum annual interest rate is 32.4%. Administrative fees (profile evaluation and validation, disbursement, transaction) range from L 65 to L 2,106 plus VAT. Early repayment is allowed without additional fees.
Representative example (per the app): a L 7,000 loan over 90 days totals L 7,938 plus VAT — equivalent to L 189 in interest plus L 749 in processing fees plus VAT.
Regulatory standing: Vana is registered as a Non-Bank Lender with the Servicio de Administración de Rentas (SAR) and with URMOPRELAFT (the Honduran AML/CTF unit), and is a member of the Honduran Fintech Association (AFINH).
Privacy & contact: privacy policy at https://cdn.vana.hn/privacy-policy/index.html. Support: soporte@vana.hn · website vana.hn · address: Torre Nova 2, 9th Floor, Novacentro, Los Próceres Corporate Center, Tegucigalpa.
Recent context (last 2 years): Vana has continued to expand across LatAm with localized apps in Guatemala (vana.gt), Peru (vana.pe), and the Dominican Republic (vana.do); industry coverage of the company in 2024–2025 (including an EDC podcast with co-founder/CFO Luis Marinelli) emphasizes its ML-driven, alternative-data approach to financial inclusion in markets with low formal banking penetration.