Reference architectures.

How to build with the blocks: each case shows the problem, the build and what you get.

Full digital bank

Who it is forIPs and SCDs — Brazil's payment-institution and direct-credit-company licenses — and digital banks (S2–S4) launching their own accounts, Pix and card issuing.

Launching accounts, transfers and Pix from scratch takes a correct ledger, real-time risk control and a connection to the central bank — usually months of wiring separate systems together.

The build

  • Midazthe double-entry ledger where everything settles
  • Tracervalidates every transaction in real time, before the ledger
  • Flowkerorchestrates onboarding, approvals and payment routing
  • SPI · Pix / SPB · TEDsettlement direct at BACEN, Brazil's central bank
  • Reporterregulatory reports straight from the ledger

What you get

  • A ledger that is correct by construction, in double entry and with an immutable trail.
  • Pix and TED settling directly, with no third-party gateway.
  • Risk and compliance in the same stack, not bolted on afterwards.

Embedded finance / BaaS

Who it is forBaaS providers and platforms serving several brands or subsidiaries.

Serving several brands or subsidiaries from one base takes full tenant isolation, events each client's systems can consume, and a connection to payments — without duplicating infrastructure.

The build

What you get

  • Full tenant isolation from the foundation up.
  • Domain events published by the platform on every movement — each client's systems react from there.
  • One infrastructure base, many brands.

Marketplace

Who it is forCommerce platforms that sit in the middle of the payment between sellers and buyers.

One payment from the buyer turns into several destinations at once — the seller, the platform's commission, shipping, withholdings — and either they all settle atomically or none of them settle. Then come per-seller balances, payout calendars and reconciliation with the PSP, across millions of accounts.

The build

  • Midazone account per seller and the multi-party split settled atomically in a single transaction
  • Flowkerseller onboarding and KYC, and the order → payment → balance release cycle
  • Tracerapplies rules and limits before a payout leaves
  • SPI · Pixseller inflows and payouts settling direct at BACEN
  • Matcherreconciles what the PSP settled against what the ledger recorded
  • Reporterseller statements and tax reports

What you get

  • Seller, commission, shipping and withholdings in a single transaction: everything settles, or nothing does.
  • Per-seller balances in the ledger itself — no side spreadsheet to know how much each one can withdraw.
  • What the PSP settled checked against what the ledger recorded, with the differences isolated as exceptions.

Acquiring and sub-acquiring

Who it is forAcquirers, sub-acquirers and payment facilitators.

Every transaction captured splits four ways: MDR (the merchant discount rate), network fee, acquirer fee and the merchant's net — components that settle on different schedules, from D+1 to D+30. Checking the network's or the acquirer's settlement file against what was actually captured is the bottleneck, and the merchant still has to be paid on time.

The build

  • Midazan account per merchant, settlement and withheld-MDR accounts, every fee component with its own entry
  • Matcherreconciles the settlement files with tolerance for fees and timing, and 1:N split matching
  • Flowkerorchestrates capture → settlement → payout, and merchant onboarding
  • Tracerapplies the business rules before authorizing
  • SPI · Pix / SPB · TEDmerchant payouts settling direct at BACEN
  • Lenderadvances on the merchant's receivables, booked as a credit operation
  • Reportersettlement and accounting reports

What you get

  • MDR, network, acquirer and merchant net each with their own ledger entry — not one net figure with no arithmetic behind it.
  • Settlement files checked against what was captured, with tolerance for fees and timing and 1:N relationships.
  • Merchant payouts leaving by Pix or TED direct at BACEN, with no intermediary in the money path.

Payroll-deducted lending (Consignado)

Who it is forConsumer finance companies, SCDs and credit fintechs running Consignado in Brazil.

Running Consignado in Brazil goes from origination and signing the CCB (the Brazilian loan contract) to registering the loan with Dataprev so the installments are deducted at source, and booking every financial event along the way — usually spread across systems that do not talk to each other.

The build

  • Lenderthe end-to-end credit journey: origination, CCB, servicing
  • Consignado · Dataprevpayroll registration and the operations exchanged with Dataprev
  • Midazbooks every credit event in the ledger
  • Reporteraccounting and regulatory reports on the portfolio

What you get

  • From proposal to payroll registration in a single engine, with one consistent history.
  • Every financial event booked in the double-entry ledger.
  • End-to-end Consignado coverage, in one stack.

Enterprise reconciliation and treasury

Who it is forEnterprise treasuries and back-office teams that close the month without replacing their core.

Closing the month by checking statements from banks, processors and ERPs against internal records eats days in spreadsheets — and you want that solved without replacing the core you already run.

The build

  • Matcherconnects to the sources you already have and reconciles across them, with scores and exceptions
  • Flowkerorchestrates the reconciliation cycle, from ingestion to close
  • Reporterreconciliation and variance reports

What you get

  • Automatic reconciliation across banks, processors, ERPs and ledgers.
  • Runs standalone on top of the systems you already have — no core migration, Midaz optional.
  • Exceptions routed to the tools the team already uses — JIRA or ServiceNow, through webhooks.

Which architecture is yours?

Bring us your case — we assemble it from the blocks.