The specification and the contract

Everything an integration needs to know about the contract, and the sources every rule in the catalogue is checked against. The contract is published by the platform itself, so this page cannot describe an API that is no longer there.

Technical specifications

The simulation is live in its own cloud project. What a team gets today, what is still being built, and how to start.

Live now · a console with a world switcher, a REST API, a persisted world per team, and a public simulation anybody can run without a key.

Endpoints

Console: ecosystem.financial — sign-in with Google or email, restricted to an allow-list.
OpenAPI contract: /openapi.json — the REST API publishes its contract.
Health: GET /v1/health
Runs and scenarios: /v1/**
Machine lane: /v1/atm/** — for real ATM and ITM integrations.
Message shapes: Transfers as ISO 20022-shaped JSON; card responses carry the ISO 8583 projection.
Webhooks: A team’s application is told what happened, instead of polling for it.
Try it live: financialecosystem.io/simulate/ — a public simulation in the browser, no key and nothing to install: a transfer, a cash withdrawal or a card purchase, run live with every rule cited.

Authentication and isolation

Team key: One key per team, sent in the header x-lab-api-key.
Isolated world: Each key is its own world, with its own seed, clock, ledgers and reports — persisted in Firestore, so it survives a restart. The console’s world switcher says which world is on screen.
Determinism: A run is deterministic from its seed, and a world can be reset.
Reports: Stored per team: trace, ledgers, reconciliation and findings citing articles.

Starter population, per world

Institutions: Three banks with different personalities, one electronic-payment entity, the direct-debit administrator and an ATM network.
People and businesses: 200 synthetic people and 40 businesses, with unmistakably synthetic identifiers.
What they hold: Accounts with the regional standardized number, balances, cards, SGPI aliases — and flagged adversaries.

Live across the whole ecosystem

Cards: Acquirer and sub-acquirer, two card schemes with their own BIN tables, authorization routed to the issuer that owns the BIN, tokenization and 3-D Secure, clearing accumulated per cycle and settled net in the LBTR, and the dispute lifecycle.
Providers: Wallet, payment-initiation and payment-gateway providers, a QR profile, and the consent register a bank and an electronic-payment entity keep alike.
Supervision and compliance: The simulated supervisors, the financial-intelligence unit, the oversight feed, and CEMI Cumplimiento plugged in as a live participant.
Cheques and resilience: Cheque clearing at stateful fidelity — digitization, image exchange, returns and net settlement in the LBTR — and chaos mode, a deterministic failure injector shipped with its negative controls.
Sponsored nodes: A sponsor gets its own institution, a private lane for its vendors, certification runs, and an Art. 83 dossier shaped as the evidence a no-objection request needs.

Scope today

Endpoints: 340+ REST endpoints, all in the published OpenAPI contract.
Rule catalogue: Version 2026.09.08, every rule citing its article.
Availability: Invited outside teams from 8 September 2026.

In progress — being built now

The Central Bank’s QR standard and the SGPI operating rules, as each instructivo is published
Sponsored nodes and community scenarios with the first partner institutions

Start in five minutes

Ask for a keyWrite to partners@cemi.ai. You get a team key and a seat on the console allow-list.

Read the contractFetch the OpenAPI document, open the technical manual, and check GET /v1/health.

RunSend x-lab-api-key on every call, pick a seed, run a scenario, and read the report.

What a run here is, and is not

Everything in the ecosystem is simulated and carries a Lab name. It is not an «ambiente de prueba» under Art. 83, and a report serves as evidence only — it grants nothing.

Today this is a simulation, not a digital twin in the strict sense: there is not yet a finished system to be a twin of, since the instant-payments system is being built now. Our aim is to become the true digital twin of the Dominican financial ecosystem as it takes shape, following the work and guidelines of the Central Bank, the Superintendencia and the industry.

Technical manual · The manual is public and generated from the deployed contract and rule catalogue. Questions: partners@cemi.ai.

Sources

Everything on this page comes from the Central Bank’s own published material. Where a figure appears, its article or its page is named.

Also read: Ley 183-02 (Monetary and Financial Law), Art. 27; Ley 155-17 on money laundering and terrorist financing; the Novena Resolución of 18 November 2010 adopting the regional standardized account number; and the tables of contents of the three instructivos — administrators of payment systems and acquirers, electronic-payment entities and electronic payment accounts, and the LBTR — read in full for their operational parameters.