DaviPlata API integration services (Bre-B / OpenFinance)

1 · Microenterprise sales reconciliation

Context: a shop that collects with DaviPlata QR and the payment button wants its accounting tool to see net settled revenue.
Data/API: Transaction history API + merchant-collection records (order reference, gross, fee, settlement batch).
OpenFinance mapping: a consented, machine-readable account-information feed — the same idea as PSD2/UK Open Banking AIS, applied to a Colombian wallet, normalised into ledger entries for the ERP.

2 · Bre-B instant payout & refund engine

Context: a marketplace or insurer pays sellers and claimants in seconds rather than next-day batches.
Data/API: Bre-B transfer module — resolve a llave, submit the payment, subscribe to the status webhook (accepted / settled / rejected).
OpenFinance mapping: payment-initiation over an interoperable national rail (Bre-B / SPBVI), with reference tracking comparable to a PIS flow.

3 · Personal-finance dashboard for the underbanked

Context: a budgeting app serving users whose only product is DaviPlata, including PPT and cédula de extranjería holders.
Data/API: Account link API + Balance & sync API + Transaction history API; categorise transfers, top-ups and bill payments.
OpenFinance mapping: consumer-permissioned data sharing under Colombia's voluntary open-finance model, surfacing balances and categorised spend.

4 · Statement-based loan underwriting

Context: a lender wants verified cash-flow evidence instead of uploaded screenshots.
Data/API: Statement export module — date-ranged structured rows plus the rendered PDF, opening/closing balance, category totals.
OpenFinance mapping: account-information sharing for affordability assessment, with consent records retained for audit.

5 · Remittance "last mile" confirmation

Context: a cross-border money-transfer operator credits recipients in Colombia to DaviPlata and needs delivery confirmation.
Data/API: inbound-credit events from the Transaction history API / Bre-B ingestion, matched to the remittance reference.
OpenFinance mapping: webhook-driven settlement notification, closing the loop between an international payout and the local wallet ledger.

1 · Obtain an access token (OAuth client credentials)

POST /oauth2/token HTTP/1.1
Host: api.partner-gateway.example
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials
&client_id=<CLIENT_ID>
&client_secret=<CLIENT_SECRET>
&scope=daviplata.read daviplata.payments

200 OK
{
  "access_token": "eyJhbGciOi...",
  "token_type": "Bearer",
  "expires_in": 1800,
  "scope": "daviplata.read daviplata.payments"
}
# Timeout note: DaviPlata APIs use a 60s server timeout — set client read timeout accordingly.

2 · Fetch transaction history (paged, date-ranged)

GET /v1/daviplata/accounts/{account_ref}/transactions
  ?from=2026-04-01&to=2026-04-30&type=ALL&page=1&page_size=100
Authorization: Bearer <ACCESS_TOKEN>
X-Consent-Id: cns_8f21a4

200 OK
{
  "account_ref": "DP-****-2391",
  "currency": "COP",
  "page": 1, "page_size": 100, "has_more": true,
  "items": [
    {"id":"txn_001","ts":"2026-04-03T14:21:09-05:00","type":"BRE_B_IN",
     "counterparty_key":"@maria.r","amount":85000,"fee":0,"balance_after":211400,"status":"SETTLED"},
    {"id":"txn_002","ts":"2026-04-03T18:02:55-05:00","type":"QR_PURCHASE",
     "merchant":"Tienda La 14","amount":-23990,"fee":0,"balance_after":187410,"status":"SETTLED"}
  ]
}
# Errors: 401 invalid_token · 403 scope_missing · 409 consent_expired · 429 rate_limited (retry-after)

3 · Initiate a Bre-B payment by llave

POST /v1/daviplata/payments/bre-b
Authorization: Bearer <ACCESS_TOKEN>
Idempotency-Key: 1f9c2a7e-...
Content-Type: application/json

{
  "debtor_account_ref": "DP-****-2391",
  "creditor_key": {"type": "PHONE", "value": "+57 3001234567"},
  "amount": 120000, "currency": "COP",
  "reference": "ORDER-7741"
}

202 Accepted
{ "payment_id": "pay_5571", "status": "ACCEPTED", "expected_clearing": "PT20S" }

4 · Settlement webhook (your endpoint)

POST /webhooks/daviplata  (signed: X-Signature: sha256=...)
Content-Type: application/json

{
  "event": "payment.settled",
  "payment_id": "pay_5571",
  "reference": "ORDER-7741",
  "amount": 120000, "currency": "COP",
  "settled_at": "2026-04-29T09:15:02-05:00"
}
# Verify HMAC over the raw body before trusting the event; respond 2xx within 5s or it is retried.

Nequi

Bancolombia's mobile wallet and the largest Colombian neobank by users; holds wallet balances, transfers, "bolsillos" savings pockets, card transactions and Bre-B activity. Teams that integrate DaviPlata frequently need the same transaction-export shape for Nequi so dashboards can merge both ledgers.

MOVii

An independent Colombian fintech wallet identified mainly by phone number; holds prepaid-card movements, top-ups, transfers and merchant payments. Relevant when a payout engine must reach recipients regardless of which wallet they use.

Nu Colombia (Nubank)

Digital account and credit card with a daily-yield savings product; holds card statements, account movements and interest accruals. Often paired with DaviPlata in personal-finance apps that aggregate spending across accounts.

Lulo Bank

A fully digital Colombian bank (Grupo Gilinski) offering accounts, savings goals and cards; holds account statements, goal balances and card transactions — another candidate for the same statement-export and balance-sync integration patterns.

RappiPay

Wallet and prepaid Visa inside the Rappi ecosystem; holds wallet balance, card spend, cashback and order-linked payments. Useful when reconciling delivery-platform spend alongside a standalone wallet like DaviPlata.

Ualá

Argentine fintech operating in Colombia, Mexico and Argentina with a wallet, Mastercard debit and the Ualá Bis acquiring terminal; holds transactions, card movements and merchant collections — relevant for cross-border and multi-country reporting.

Dale!

A low-amount deposit wallet (EFECTY/Grupo Éxito lineage) used for transfers, bill pay and top-ups; holds the same family of wallet movement and receipt data, often integrated for inclusion-focused budgeting tools.

Tpaga

A Colombian wallet aimed at gig workers and small merchants; holds wallet transactions, QR collections and payout records — frequently grouped with DaviPlata QR data when building merchant-side reconciliation.

Mercado Pago

Mercado Libre's wallet and acquiring platform across Latin America; holds payments, settlements, QR collections and account movements. A common partner ledger to merge with DaviPlata for sellers operating on both rails.

Bancolombia App

The flagship mobile-banking app of Colombia's largest bank; holds account balances, transfers, card statements and Bre-B keys. Personal-finance and accounting integrations often need DaviPlata and Bancolombia data side by side.

Deliverables checklist

• API specification (OpenAPI / Swagger) for each implemented endpoint
• Protocol & auth-flow report (token exchange, refresh, consent lifecycle, webhook signing)
• Runnable source for the modules you order — login, transactions, balance, Bre-B, statements, payment button (Python / Node.js; Go on request)
• Automated tests, Postman collection, and example payloads against sandbox
• Compliance guidance: consent text, retention windows, Ley 1581 data-subject handling, logging plan
• Handover session + 30 days of fixes for the delivered scope

Engagement workflow

1. Scope call: which DaviPlata data/flows, which authorization route, sandbox access.
2. Protocol analysis & API design (2–5 business days, complexity-dependent).
3. Build & internal validation against sandbox (3–8 business days).
4. Docs, samples, tests (1–2 business days).
5. Typical first delivery: 5–15 business days; Davivienda portal approvals, Bre-B key registration or merchant onboarding can extend timelines.

About us

We are an independent studio focused on fintech and open-data API integration. Our engineers come from banks, payment gateways, protocol-analysis and cloud backgrounds, and we have shipped wallet, statement and instant-payments integrations across Latin America and beyond. We work to security and compliance constraints, document everything we build, and prefer sandbox-first delivery so you can verify before going live.

• Wallets, digital banking, remittances, merchant acquiring and cross-border settlement
• Enterprise API gateways, webhook security reviews and idempotency design
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance handover
• Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — call our hosted endpoints and pay only per request, no upfront cost; good for teams that prefer usage-based pricing

Contact

For a quote, send your target app and concrete requirements (the data types, the flows, your authorization route). We'll reply with scope, timeline and price.

Contact page

We only build against authorized access or documented public/authorized APIs — share what authorization you hold (e.g. Davivienda developer-portal credentials) and we'll scope around it.

What do you need from me to start a DaviPlata integration?

The target app name (DaviPlata, provided), the concrete data or flows you need (transaction history, balance, statement export, Bre-B key transfers, the DaviPlata payment button), and any sandbox or merchant credentials you already hold on the Davivienda developer portal.

How long does delivery take?

Usually 5 to 15 business days for a first API drop with documentation; flows that depend on Davivienda sandbox approval, Bre-B key registration or merchant onboarding may take longer.

How do you handle compliance and user consent?

We work only with customer authorization or documented, authorized APIs, keep request and consent logs, apply data minimization, and align with Colombia's Ley 1581 de 2012 data-protection rules and Superintendencia Financiera expectations; NDAs on request.

Do you support pay-per-call billing instead of source code delivery?

Yes. You can take the runnable source code from 300 USD and run it yourself, or call our hosted endpoints and pay only per request with no upfront fee.