Deuna Negocios API integration services (Ecuador OpenFinance)

Why Deuna Negocios data matters

Since its 2026 launch, Deuna Negocios has positioned itself as a one-stop merchant tool for Ecuador's micro and small businesses, centralizing collection, cash close and team permissions in a single Android and iOS app. Each transaction generated in the app is structured: it carries an amount, a reason, a cashier identity, a timestamp and a settlement target (a Deuna or Banco Pichincha account, or a Deuna phone number).

For a third-party platform — an ERP, an accounting SaaS, a delivery marketplace or a tax filing tool — that structured payment stream is exactly what an OpenFinance integration can unlock: real-time visibility of revenue, automated reconciliation against invoices, and audit-grade evidence for the Servicio de Rentas Internas (SRI) and the Superintendencia de Bancos del Ecuador.

We connect to Deuna Negocios via its documented merchant APIs and through authorized protocol analysis where additional data is required, so your product can read sales, raise charges, listen to webhooks, and trigger refunds without forcing the merchant to leave their existing app.

Recent change worth noting

In 2025–2026, Deuna shipped a major upgrade for the merchant side: businesses can now accept debit and credit card payments directly from their cell phone, without any additional reader or POS terminal. This expands the addressable data model from QR-only flows to full card acceptance, which means our integrations can also surface card-brand, authorization status and acquirer settlement metadata.

In parallel, Deuna has interconnected with the blu network and with more than twenty cooperatives in Ecuador, which means a single Deuna Negocios merchant now receives QR payments originated from Banco Pichincha's Banca Móvil, BGR Digital, Alianza del Valle, Tulcán and many cooperative apps — all unified into one transaction feed that we can export.

QR collection API

Generate static QR with a pre-loaded amount or dynamic QR per checkout, both bound to your internal order ID. Use case: a restaurant POS issues a QR per table; the kitchen system marks the order paid only when our webhook confirms the Deuna sale.

Payment status & cashier query

Look up a transaction by reference, retrieve the operating cashier (role and permission scope), the concept text and the timestamp. Use case: end-of-day reconciliation in an accounting tool, where each Deuna sale is matched against the cashier shift and invoice line.

Webhook for sales notifications

Subscribe to instant POST callbacks when a customer pays. Use case: an inventory system decrements stock the moment Deuna confirms the QR or payment-link transaction, eliminating the polling loop and reducing oversells.

Refund & cancellation API

Programmatically request a refund or cancel a pending charge. Use case: a marketplace's customer-care console issues a refund directly into the buyer's Deuna account without manual approval steps inside the merchant app.

Transfer & settlement bridge

Read transfers between Deuna accounts, Banco Pichincha accounts and Deuna phone numbers. Use case: a treasury dashboard rolls up daily inflows by store and pushes consolidated settlement data into the corporate ERP.

Reports & cash-close export

Pull cash management entries, daily cash reports and close reminders into your tooling. Use case: a multi-branch retailer feeds Deuna cash-close events into a BI cube to compare in-app sales against POS receipts.

Scenario 1 — ERP sales reconciliation for SMEs

An Ecuadorian retail chain runs an ERP with multi-branch reporting. We attach a Deuna Negocios webhook for every QR or card sale, push the event to a queue, and post a journal entry in the ERP that ties the Deuna transaction reference to an invoice line. The mapping uses cashier_id, store_code and concept from the Deuna payload, aligning with OpenFinance principles of consented, granular merchant-payment data sharing.

Scenario 2 — Online checkout with payment link

A marketplace generates a Deuna payment link via the merchant API, embeds it in the checkout page and listens for the success webhook. On confirmation, the order moves to "paid" and the warehouse module dispatches the package. This avoids redirecting the customer to a separate gateway and reuses the merchant's existing Deuna Negocios account, keeping the OpenBanking flow inside one regulated provider.

Scenario 3 — Tax compliance & SRI filing

A tax-tech SaaS pulls a daily statement export of all Deuna Negocios transactions for a given RUC, classifies them by VAT category and emits the filing payload to the SRI portal. The Deuna data carries the merchant RUC, transaction concept and amount — exactly the fields needed for VAT-aware reporting in Ecuador.

Scenario 4 — Lending / credit scoring for micro-merchants

A digital lender requests, with explicit merchant consent, a 90-day window of Deuna Negocios sales. The platform turns these into a cash-flow score, including average ticket, number of paying customers and seasonality, and offers a working-capital line. This is a textbook OpenFinance use case for the LATAM micro-merchant segment.

Scenario 5 — BI dashboards for franchise networks

A franchise headquarters consolidates Deuna Negocios sales across dozens of franchisees into a BI tool (Looker, Metabase or Power BI). Our pipeline normalizes store_code, cashier_id and payment_method, exposing daily and intraday sales KPIs alongside Banco Pichincha settlement events.

1) Generate a QR / payment link

POST /api/v1/deuna-negocios/charges
Content-Type: application/json
Authorization: Bearer <MERCHANT_ACCESS_TOKEN>

{
  "ruc": "1790012345001",
  "store_code": "QUITO-NORTE-01",
  "amount": 18.75,
  "currency": "USD",
  "reason": "Order #A-9821",
  "method": "QR_DYNAMIC",
  "external_id": "ord_A9821"
}

200 OK
{
  "charge_id": "chg_01HXYZ...",
  "qr_payload": "00020101021226...",
  "payment_link": "https://pay.deuna.app/c/abc123",
  "expires_at": "2026-04-29T18:30:00-05:00",
  "status": "PENDING"
}

2) Query transaction status

GET /api/v1/deuna-negocios/charges/chg_01HXYZ
Authorization: Bearer <MERCHANT_ACCESS_TOKEN>

200 OK
{
  "charge_id": "chg_01HXYZ",
  "status": "PAID",
  "paid_at": "2026-04-29T17:42:11-05:00",
  "amount": 18.75,
  "cashier": { "id": "csh_22", "role": "CAJERO" },
  "payer": { "channel": "DEUNA_APP", "alias": "ana***@deuna" },
  "concept": "Order #A-9821",
  "settlement_target": "PICHINCHA_2200xxxx"
}

3) Webhook callback & refund

POST https://your-api.example/webhooks/deuna
X-Deuna-Signature: t=1714421000,v1=...
{
  "event": "charge.paid",
  "charge_id": "chg_01HXYZ",
  "external_id": "ord_A9821",
  "amount": 18.75,
  "cashier_id": "csh_22"
}

# Verify signature, then optionally refund:
POST /api/v1/deuna-negocios/charges/chg_01HXYZ/refund
Authorization: Bearer <MERCHANT_ACCESS_TOKEN>
{ "reason": "customer_request", "amount": 18.75 }

# Standard error envelope
4xx { "error": { "code": "CHARGE_ALREADY_REFUNDED", "message": "..." } }

Regulatory framing

Deuna Negocios operates in Ecuador under the supervision of the Superintendencia de Bancos del Ecuador and works in close partnership with Banco Pichincha. Any integration we deliver respects Ecuador's Ley Orgánica de Protección de Datos Personales (LOPDP) and aligns with regional OpenFinance practices and the principles popularized by PSD2/PSD3 in Europe and Open Finance Brasil. We document the legal basis (merchant consent, contractual necessity), the data categories accessed and the retention policy applied.

Operational safeguards

We minimize data, encrypt tokens at rest, rotate keys, sign webhooks with HMAC and isolate environments per tenant. PII is segregated from transactional fields, refunds are audited end-to-end and access logs are retained for the periods required by SRI and the Superintendencia. NDAs and DPAs are available on request.

Deliverables checklist

• OpenAPI 3.1 / Swagger specification for the Deuna Negocios connector
• Protocol and authentication report (token lifecycle, webhook signing, error map)
• Runnable source code (Python, Node.js or Go) for charges, status, refund and webhook flows
• Automated tests, Postman collection and sandbox fixtures
• Compliance pack: data inventory, LOPDP notes, retention plan

Engagement workflow

1. Scope confirmation: integration scenarios, RUC list, expected volume.
2. Protocol analysis and API design (2–5 business days).
3. Build and internal validation (3–8 business days).
4. Docs, samples and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days, depending on complexity.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?