Back to the journal
Engineering

The case for one ledger per brand

Multi-brand operators always ask: shared liquidity, isolated reporting, or both? Here's how we draw the line.

MTMaya Tran· Engineering Lead8 min read

Multi-brand operators always ask: shared liquidity, isolated reporting, or both? Here's how we draw the line.

The story

This article is the seeded version of "The case for one ledger per brand". Replace this body in the Studio with the full deep-dive — bold, lists, blockquotes and inline links are all supported.

  • Open this post in /studio under Blog → Blog posts
  • Replace this body with the actual article
  • Add a cover image and author photo
Filed underEngineering
Related reading

More from the journal

Engineering

Inside Flex-Pay's smart routing engine

How we score 400+ acquirers per market and risk profile, and the failure modes we tuned for in the last two quarters.

Read article
Engineering

Why we chose Postgres for the ledger

We benchmarked four data stores against the workload. Postgres won — but not for the reason we expected.

Read article
Engineering

Risk routing across BNPL lenders

A practical look at how 220+ BNPL providers are sequenced through a single application form — without stacking hard inquiries.

Read article
Keep reading

More notes from the engine room.

Browse every article in the Flex-Pay Journal — product deep-dives, engineering write-ups, customer stories and the trade-offs behind every shipped surface.

All articlesBrowse the library