Account, POS and CoDi records inside BBVA Business Mexico — and the authorized way to reach them

Every B Negocios session sits on top of a Mexican business-banking backend that settles POS terminal sales, books transfers across MXN, USD and EUR, and clears CoDi QR charges in real time. The interesting part for an integrator is not the login screen. It is the reconciliation: the app totals operations and commissions per merchant affiliation, then posts a net amount to your checking account. That is exactly the figure a finance team re-types by hand today. This brief maps what the app holds, the authorized way to reach it for a third party, and what we hand over at the end.

What B Negocios actually holds for a business

The surfaces below come from the app's own published feature list and BBVA México's B Negocios page. Each row is something a connected system would read or sync.

Routes to the data

Three routes genuinely apply to B Negocios. They differ in how durable they are and how much we stand up to make them run.

Authorized interface integration against a consenting account

We read the app's own traffic under the account holder's authorization and rebuild the calls behind the movements, POS settlement and balance screens. This reaches everything the app shows. Effort is moderate; the one maintenance cost is re-confirming the captured flows when BBVA ships an app update. Access is arranged with you during onboarding, and the build runs against a consenting B Negocios account or a sandbox you nominate.

The CoDi and SPEI payment rails, taken directly

CoDi is operated by Banco de México as a QR layer over SPEI, so the collections slice does not need the private session at all. For a project that is only about taking money in, we integrate CoDi straight to Banxico's rail — static or dynamic QR, with settlement notifications fed back to your books.

The regulated transactional rail, when it arrives

Article 76 of the 2018 Ley Fintech obliges financial entities to share account and transaction data through standardized APIs. In principle that would replace much of the work above with a consented, schema-stable feed. In practice the secondary rules for datos transaccionales are not published, so this is a route we design toward, not one that is switched on today.

For most B Negocios work we build against a consenting account and read the app's own traffic, because the regulated feed that would otherwise carry this data is not live in Mexico yet. Where a job is purely collections, we skip that entirely and wire CoDi to Banxico. The choice is driven by what the project needs to read, not by a fixed ranking of the options.

A statement-and-settlement pull, sketched

Illustrative only — endpoint paths and field names are confirmed during the build against a consenting account, not asserted from the public listing. The shape mirrors how the app filters movements and how it reconciles POS settlement per affiliation.

# Runs against a consenting B Negocios account. Spanish field names
# follow the app's own vocabulary (movimientos, afiliacion, liquidacion).

session = bnegocios.login(
    contrato   = "MX-EMPRESA",            # business contract / codigo de cliente
    factor     = mobile_token.respond()   # B Negocios mobile token / Cronto challenge
)

# Account movements, filtered the way the app filters them
movs = session.get("/cuentas/{cta}/movimientos",
                   params={"tipo": "egreso", "desde": "2026-05-01"})

# POS settlement: daily summary per affiliation, to reconcile to the checking account
liq = session.get("/tpv/afiliaciones/{afil}/liquidacion",
                  params={"periodo": "2026-05", "detalle": "comisiones"})

for dia in liq["dias"]:
    book(fecha   = dia["fecha"],
         ventas  = dia["importe_bruto"],
         comision= dia["comision"],
         neto    = dia["abono_cuenta"])     # what hits the checking account

# CoDi charge — generated on Banxico's rail, not the private session
codi = banxico_codi.charge(monto="1450.00", concepto="Folio 8841", tipo="dinamico")

Transfers are read the same way, but we do not automate the money-moving call — a SPEI or own-account transfer carries a token step-up and stays behind explicit human approval.

What you receive

Each deliverable is tied to the surfaces above, not a generic checklist.

• An OpenAPI specification covering the movements, POS settlement, transfers and CoDi endpoints as captured.
• A protocol and auth-flow report: how the mobile-token and Cronto challenge-response builds and refreshes a session, written down step by step.
• Runnable source in Python or Node.js for the statement pull, the per-affiliation POS reconciliation, and CoDi charge creation.
• A normalized schema that maps B Negocios fields (importe_bruto, comision, abono_cuenta) to a clean model your systems consume.
• Automated tests that run against a consenting account or sandbox.
• Interface documentation plus consent-record and data-retention guidance for operating it.

Where Mexico's open-finance rules actually stand

Mexico legislated open finance early. The 2018 Ley Fintech, through Article 76, requires financial entities to share three tiers of data through APIs — datos abiertos (public product data), datos agregados, and datos transaccionales (individual account data with consent) — supervised by the CNBV alongside Banco de México and SHCP. Only the open-data tier is operative. The secondary rules that would make transactional sharing real have never been issued; reporting around the January 2026 amparo against CNBV, Banxico and SHCP put the delay past 2,000 days. So the page does not pretend a consented regulated feed exists for B Negocios right now.

That makes the dependable basis the account holder's own authorization. We work from explicit, written consent for the specific data in scope, keep consent and access records, minimize what is pulled to what the integration needs, and sign an NDA where the engagement calls for one. CoDi sits apart from all of this: it is a Banxico-run rail anyone with the right banking relationship can collect through.

What we account for on a B Negocios build

Three things on this app shape how we design the integration.

• Settlement is keyed per affiliation. A merchant with several terminals holds several afiliaciones, each with its own daily and monthly commission summary. We model the sync per affiliation and roll up to the checking account the way the app's reconciliation view does, so a multi-terminal business does not lose the per-terminal breakdown.
• The session is token-gated and short-lived. The mobile token and Cronto device step up sensitive operations with a challenge-response. We design the sync around that session model and the consent-refresh window so reads do not silently expire mid-day, and we keep transfers behind human approval rather than scripting them.
• Currency and value date travel together. Balances and own-account transfers span MXN, USD and EUR. We normalize currency and value-date handling so a cross-currency movement reconciles to the right posting date and amount instead of double-counting.

The app describes itself as constantly changing, so we keep a maintenance check that re-confirms the captured flows whenever BBVA updates the app.

Where teams put this to work

• An accounting platform that auto-books each day's POS gross, commission and net abono per affiliation, ready for a Mexican tax close.
• A merchant checkout that raises a dynamic CoDi QR at the till and marks the order paid on Banxico settlement, with no terminal.
• A treasury dashboard that pulls MXN, USD and EUR balances and movements nightly across a group's B Negocios contracts.

Screens we worked from

Published B Negocios screenshots. Select one to enlarge.

Other Mexican business-finance apps in the same picture

If you are unifying more than one provider, these sit alongside B Negocios. Named for context only.

• Banorte — business accounts, SPEI transfers and payroll for Mexican companies.
• Santander Empresas México — corporate accounts, cash management and transfers.
• Citibanamex (BancaNet Empresarial) — business accounts and card data.
• HSBC México — business banking and transfers for a large international book.
• Clip — merchant POS payments and daily settlement for small businesses.
• Konfío — SME lending with a business card and payment terminal.
• Clara — corporate cards and spend management across LatAm.
• Albo — commission-free accounts and card management.
• Mercado Pago — merchant wallet with QR collections and settlement.

Sources and review

Compiled in June 2026 by the OpenBanking Studio integration desk. We read the app's published feature list and BBVA México's own B Negocios page for the data surfaces, Banxico's CoDi documentation for the QR rail, and current Mexican coverage for where the open-finance rules stand. Primary sources:

• BBVA Business Mexico — Google Play listing
• BBVA México — App BBVA Empresas / B Negocios
• Banco de México — CoDi, Cobro Digital
• Holland & Knight — Open Banking Has Arrived in Mexico
• El Financiero — Open Finance lleva a la CNBV ante el juez (Jan 2026)

Questions integrators ask about B Negocios

Can you reproduce the POS settlement and commission summary the way B Negocios reconciles it?

Yes. The app totals operations and commissions per affiliation on a daily and monthly basis and posts the net to your checking account; we map the same per-affiliation rollup so a finance system sees the gross, the commission and the net abono without a person re-keying the statement.

Is there a live regulated rail in Mexico that hands over this transactional data?

Not at the moment. Article 76 of the 2018 Ley Fintech obliges financial entities to share data through APIs, but the secondary rules for datos transaccionales have not been published, and a constitutional amparo was filed against CNBV, Banxico and SHCP in January 2026 over that omission. Until those rules are switched on, the dependable basis is the account holder's own authorization, so we build against a consenting account.

How do you deal with the B Negocios mobile token and Cronto step-up during an automated read?

Sessions are short and sensitive operations trigger a challenge-response from the mobile token or Cronto device. We design the sync around that session model and the consent-refresh window so balance and movement reads keep working, and we keep money-moving actions like SPEI transfers behind explicit human approval rather than automating them.

Can CoDi collections be generated outside the app?

Yes. CoDi is operated by Banxico as a QR layer over SPEI, so the charge-and-settle slice can be wired straight to that rail with static or dynamic QR, separate from the private B Negocios session, and the settlement notifications fed back into your books.

Working with us

A finished B Negocios integration usually lands inside one to two weeks of focused work. Source-code delivery starts at $300: we hand over the runnable API source, the auth-flow report, tests and the interface docs, and you pay after delivery once you have looked it over and you are satisfied. Prefer not to host it yourself? Run it as a pay-per-call hosted API instead — you call our endpoints and pay only for the calls you make, with no upfront fee. Either way you give us the app name — BBVA Business Mexico — and what you need from its data; access and the compliance paperwork are arranged with you as part of the work. Tell us what you need on the contact page and we will scope it.

Mapping last checked 2026-06-15.