Pulling BIZ's business-banking data into your own systems

One BIZ login can sit over several companies at once. The bank lets an administrator link every company they manage to a single profile, and each one carries its own checking accounts, corporate credit cards, deposit certificates and loans — plus a queue of transactions waiting on someone to approve them. That shape, one profile over many empresas with mixed products, is what governs any integration against it.

There is no live open-banking mandate in the Dominican Republic yet, so the dependable basis for reaching this data is the company's own authorization. We work from a consenting BIZ session, study how the app talks to the bank, and rebuild those calls as a client you can run. The practical shape is a scheduled delta pull: read each company's accounts, then page new movements forward from a saved reference, on whatever cadence the treasury team needs.

What sits behind a BIZ login

The data worth integrating is exactly what the app shows a finance manager. Mapped to its own naming where the listing and the bank's page use Spanish labels:

Getting to the data: the routes that fit

Three routes apply to BIZ, plus a direction worth naming for the long run.

1. Protocol analysis of a consenting session

We capture how the app authenticates and queries the bank from a session the company authorizes, then rebuild those calls. This reaches everything the app surfaces — accounts, cards, certificates, loans, approvals. Effort is moderate; durability is good as long as we re-validate when the bank ships an app update. For BIZ this is the route we'd build on, because it tracks the real surfaces a finance team already uses.

2. User-consented credential operation

The company's own authorized operators stand up a managed session with their corporate credentials and step-up factor. Same surfaces, lighter setup, and it keeps the access trail squarely with people the company already trusts.

3. In-session statement download as a fallback

Where a statement or movement export is available inside the session, we can wire that in for bulk history. It is narrower than a live pull and tends to lag, so we treat it as a backfill aid, not the spine.

Where the regime is heading

Regulated open-finance access is the forward option here. The Superintendencia de Bancos has been building a framework with the IFC and ran a technical sandbox, so a consent-based API path may exist later; we design today's client so a move onto that path is a swap of the transport, not a rewrite.

A delta pull against the movements feed

The core loop is small. Authenticate once with the corporate credentials and step-up factor, list the companies on the profile, then page movements per account from a saved cursor. Shapes below are illustrative and were confirmed against captured traffic during the build.

# Delta pull of account movements for one empresa on a BIZ profile.
# Auth mirrors the app: company + user + password, then a step-up
# (biometric / device factor), replayed through the client we build.

POST /seguridad/sesion            # establish session
  body: { empresa, usuario, secreto, factor }
  -> { session_token, profile_id, empresas: [ {empresa_id, nombre} ] }

GET  /empresas/{empresa_id}/cuentas
  Authorization: Bearer <session_token>
  -> [ { cuenta_id, tipo, moneda, balance_disponible, balance_actual } ]

# Cursor-based delta: only movements after the last reference we stored.
GET  /cuentas/{cuenta_id}/movimientos?desde_ref={cursor}&limite=200
  -> { movimientos: [ {ref, fecha, descripcion, monto, signo, balance} ],
       next_ref, has_more }

# Loop pages while has_more; persist next_ref per cuenta for the next run.
# On 401 -> re-establish the session and resume from the same cursor.

A normalized shape to land it in

We flatten the per-company, multi-currency structure into one record an integrator can store and join. Currency rides on every amount; nothing is summed across currencies.

{
  "entity":   { "empresa_id": "...", "name": "..." },
  "account":  { "id": "...", "type": "checking",
                "currency": "DOP", "available": 0.0, "ledger": 0.0 },
  "movement": { "ref": "...", "posted_at": "2026-01-31",
                "amount": -12500.00, "currency": "DOP",
                "description": "...", "running_balance": 0.0 }
}

What you get back

The headline deliverable is code that runs, not a folder of paper. For BIZ that means:

• A runnable client in Python and Node.js covering session setup, the per-empresa account list, the movements delta endpoint, and card and loan reads.
• A delta-sync runner: a cursor store per account, paging, resume-from-last, and a separate backfill mode for the first load.
• An automated test suite running against recorded response fixtures, so a changed or renamed field shows up as a failed assertion rather than a quiet gap in your ledger.
• An OpenAPI description of the reconstructed endpoints and a short auth-flow report covering the session token, the step-up factor and how the session is renewed.
• Interface documentation and data-retention guidance written against Ley 172-13.

Consent and the Dominican rulebook

Two things govern the data side. Personal data is covered by Ley No. 172-13, the Dominican data-protection law (promulgated 2013, per the Superintendencia de Bancos), which sets informational self-determination, written consent for sensitive data, habeas data rights and limits on cross-border transfer. The banks themselves are supervised by the Superintendencia de Bancos, whose Resolution SB 003-2023 set early ground rules for digital-service interoperability and security.

A mandated open-finance regime is not in force yet. The SB, Adofintech and the Hub de Innovación Financiera have been promoting finanzas abiertas, the SB signed a commitment with the IFC to design open banking, and a Fintech sandbox was stood up to test it. Until that lands, the consent we rely on is the company's own: authorized, logged, and minimized to the accounts in scope, with an NDA where the engagement needs one.

Details we plan around for BIZ

A few traits of this app shape the build, and we handle each on our side.

One profile, many companies and roles

A single login can be linked to every company an administrator manages, and administrators define each user's limits and which entities they can act on. We mirror that role model in the client, scope every read and any submission to one empresa at a time, and make sure a pull for one company never bleeds into another.

Pesos and dollars side by side

BIZ carries DOP and USD accounts on the same profile. We keep the currency code on every balance and movement, normalize amounts with sign intact, and never roll a consolidated figure across currencies without an explicit FX step you control.

Read first, write only when asked

The app submits tax, card and loan payments and loan disbursements, and clears its approval queue in batches. We default the integration to read-only. If you want the write path, it stays behind the same dual control and per-user limits the bank enforces, scoped to the role you authorize during onboarding.

Screens we worked from

Store screenshots of BIZ, used to confirm the surfaces above. Tap to enlarge.

Other Dominican business-banking apps in scope

Most groups run more than one bank, so a unified pull usually spans several of these. Listed for ecosystem context, not ranking.

• Banreservas — the state bank and among the largest in the country by assets; its app holds accounts, transfers and payments for individuals and businesses.
• BHD — a full-suite private bank with a dedicated business app covering accounts, cards and payments.
• Scotiabank República Dominicana — part of the Canadian group; its Caribbean mobile and Scotia en Línea channels hold account and card data.
• Banco Santa Cruz — App BSC serves SMEs and corporates with accounts, credit and payment functions.
• Banesco RD — BanescoMóvil handles DOP and USD transfers, plus loan and card payments.
• Qik Banco Digital — a fully digital bank, among the most-used finance apps in the country, holding wallet and account balances.
• Banco Promerica — regional bank with accounts, cards and business products on its app.
• APAP — a savings-and-loan association operating like a bank, with accounts and credit for SMEs and corporates.

What we checked, and where

This brief was built from the app's own materials and the Dominican regulatory record, last checked 2026-06-08. We read the bank's App BIZ page for features, multi-company linking and the batch-approval limit; the Google Play and App Store listings for platform and package details; and the Superintendencia de Bancos and presidential records for the data-protection law and the open-finance work. Primary sources:

• Banco Popular Dominicano — App BIZ feature page
• Diario Libre — Banco Popular's new apps
• Superintendencia de Bancos — Ley No. 172-13
• Presidencia RD — SB, Adofintech and the open-finance push

Assessment written by an OpenFinance Lab integration engineer, 2026-06-08.

Questions integrators ask about BIZ

How current can the synced data be, and how does the pull stay up to date?

We run scheduled delta pulls: each cycle reads the account list, then pages new movements forward from the last saved reference per account. Cadence is yours to set, a few minutes apart for live treasury or hourly to end-of-day for reconciliation. The first run backfills history; later runs only fetch what changed.

Can a single run cover every company linked under one BIZ profile?

Yes. One login fans out to the empresas tied to the profile, and the client iterates them, scoping each pull to one entity so accounts, cards and movements never cross between companies. Group treasury can be consolidated downstream from there.

Does the integration only read, or can it also submit payments and approvals?

By default it reads. BIZ handles tax, card and loan payments plus loan disbursements, and a pending-approval queue that processes in batches; if you want the write path we keep it behind the same dual control and per-user limits the app enforces, scoped to the role you authorize.

Which regulator covers this in the Dominican Republic, and is open banking available yet?

The Superintendencia de Bancos supervises the banks, and personal data falls under Ley 172-13. A regulated open-finance framework is still being built with the IFC and tested in a sandbox, so today the work rests on the company's own authorization rather than a mandated consent API.

Starting a BIZ build

A typical BIZ build runs one to two weeks. You bring the app name and the companies and surfaces you care about; we arrange access and compliance with you and do the rest. Source-code delivery starts at $300 — you receive the runnable client, the delta-sync runner, tests and docs, and pay only after delivery once you are satisfied. If you would rather not run it yourself, the same surfaces are available as a pay-per-call hosted API, billed per call with no upfront fee. Talk to us about a BIZ integration