Bi en Línea API integration services (Banco Industrial Guatemala)

1. Accounting & ERP sync for Guatemalan SMEs

Many small businesses run on Bi en Línea retail accounts before graduating to Bi Banking. We expose a daily transaction-history endpoint that normalizes movements into ISO-8601 timestamps, GTQ/USD amounts, and counterparty references, then pipes them into QuickBooks, Odoo, or in-house ERPs. Reconciliation jobs match QR receipts and bill payments to invoices using merchant code and reference number.

2. Remittance trigger pipelines

With the December 2025 Zigi/Intermex/SukuPay launch, US-to-Guatemala remittances now arrive in seconds. Aid programmes, payroll providers, and household-finance apps want to react to those arrivals. We deliver a webhook stream that fires on remittance settlement with corridor, FX rate, fee, and beneficiary masking — letting customer apps top up wallets, trigger SMS, or kick off downstream payouts.

3. Credit underwriting via consented statement export

Lenders need 3–12 months of bank statements to underwrite a loan. We offer a consented "statement-pull" API that authenticates with the user's Bi en Línea credentials, retrieves the official PDF estado de cuenta, parses it into structured JSON (balances, recurring deposits, salary patterns), and ships it to the lender's underwriting model — fully aligned with Superintendencia de Bancos secrecy expectations.

4. Merchant QR & settlement reporting

Retailers accepting Bi / Cuik / Zigi QR payments want a single feed showing daily settlement, refund events, and dispute states. Our merchant-side API aggregates QR confirmations, matches them to POS line items by reference, and emits T+1 settlement files for finance teams. The same feed powers Soundbox-style audible merchant alerts for low-tech storefronts in Guatemala City and Quetzaltenango.

5. Personal-finance & budgeting apps

Bi en Línea's in-app spending tracker shows the appetite for PFM tooling. We provide a consented category-tagged transaction stream so independent PFM apps (Bilt-style coaches, expense splitters, savings nudges) can offer Guatemalan users a unified view across Bi en Línea, BAC, GTCApp, and BANRURAL accounts — without forcing each user to maintain spreadsheets.

Authorization & session bootstrap

// Step 1: bootstrap a consented Bi en Línea session
POST /api/v1/bienlinea/auth/login
Content-Type: application/json
X-Consent-Id: cs_8f1d...

{
  "user_dpi": "<Guatemalan DPI hash>",
  "device_fingerprint": "android-13-pixel-7",
  "biometric_token": "<FaceID|Fingerprint attestation>"
}

200 OK
{
  "access_token": "ey...",
  "refresh_token": "rt_...",
  "expires_in": 900,
  "scopes": ["accounts.read","statements.read","payments.qr.read"]
}

Statement export (multi-currency)

// Step 2: pull a normalized statement
POST /api/v1/bienlinea/statement
Authorization: Bearer <ACCESS_TOKEN>

{
  "account_id": "gt-bi-001-1234",
  "currency": "GTQ",
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "format":    "json"
}

200 OK
{
  "account_id": "gt-bi-001-1234",
  "opening_balance": 4321.55,
  "closing_balance": 5102.18,
  "movements": [
    {"ts":"2026-04-03T14:22Z","amount":-180.00,
     "type":"qr_payment","merchant":"FARM_GLOBAL_GT",
     "category":"health"},
    {"ts":"2026-04-15T09:01Z","amount":+5800.00,
     "type":"remittance","corridor":"US-GT","fx":7.78}
  ]
}

Webhook: remittance & QR payment events

// Step 3: subscribe to real-time events
POST /api/v1/bienlinea/webhooks
Authorization: Bearer <ACCESS_TOKEN>

{
  "url": "https://your-app.com/hooks/bi",
  "events": ["payment.qr.confirmed",
             "remittance.received",
             "card.limit.changed"],
  "secret": "whsec_..."
}

// Sample webhook delivery
POST /hooks/bi  (signed with HMAC-SHA256)
{
  "event":"remittance.received",
  "ts":"2026-05-08T18:45:11Z",
  "amount":250.00,"currency":"USD",
  "fee":0.99,"network":"zigi/sukupay",
  "beneficiary_masked":"****1234"
}

Regulatory framing

Guatemala has not yet enacted a comprehensive open-banking framework. Banking secrecy is enforced under the Banks and Financial Groups Law, which requires institutions to keep client information confidential except where the client consents or a legal exception applies. Every Bi en Línea integration we deliver therefore stands on documented consent (account-holder authorization or merchant agreement) and aligns with guidance from the Superintendencia de Bancos de Guatemala (SIB).

Where the integration touches payments, we follow the Monetary Board's technological-risk regulations, register as an Obligated Person before the Special Verification Intendancy (IVE) when payment-flow volume requires it, and apply the new Credit Card Law (Decree 2-2024) for any card-related data. Cross-border remittance flows additionally honour US BSA/AML obligations on the originating leg.

Privacy & data minimization

We only request the scopes a use case actually needs — for example, a budgeting app gets statements.read but not payments.write. PII is hashed at the edge (DPI numbers are never persisted in clear), tokens rotate every 15 minutes, and we keep a 12-month consent log so account holders can revoke access at any time. For comparative reference, see the open banking framing on Wikipedia and the broader Latin-American adoption picture documented by industry trackers.

Deliverables checklist

• API specification (OpenAPI / Swagger) tailored to Bi en Línea scopes
• Protocol & auth flow report (DPI/biometric login, token refresh, session pinning)
• Runnable source for login, statement, QR-event, and remittance APIs (Python / Node.js)
• Webhook signing & retry harness with HMAC-SHA256 verification samples
• Automated tests (sandbox + replay) and Postman collections
• Compliance pack: SIB framing, IVE/AML notes, consent and retention guidance

About OpenFinance Lab

We are an independent studio focused on fintech and open-data API integration. Our team includes engineers from regional banks, payment gateways, and protocol-analysis backgrounds. We know the Guatemalan banking stack, SIB and IVE expectations, and Latin-American privacy practice, and we ship end-to-end financial APIs under security and compliance constraints.

• Payments, digital banking, insurtech, and cross-border clearing
• Enterprise API gateways, security reviews, and SOC-2-friendly logging
• Custom Python / Node.js / Go SDKs and replay test harnesses
• Source code delivery from $300 — runnable API code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost

Engagement workflow

1. Scope confirmation: target scenarios (login, statements, QR, remittance) and data scopes.
2. Protocol analysis & API design — 2–5 business days, complexity-dependent.
3. Build & internal validation against the Bi en Línea sandbox or replay traces — 3–8 business days.
4. Documentation, sample clients, and signed test cases — 1–2 business days.
5. Typical first delivery: 5–15 business days; third-party approvals or merchant onboarding may extend timelines.

Contact

For quotes, sandbox access, or to submit your target Bi en Línea scenario:

Contact page