BaaS Operational Visibility Gap
Peter Hazlehurst and Kris Hansen, co-founders of Synctera, on BaaS in 2023
The core issue was that many banks in early BaaS setups were operating with legal responsibility but not operational sight. In an FBO structure, the bank often saw one pooled account balance and a few settlement entries, not the thousands of end customer accounts and card swipes underneath. That left compliance teams relying on delayed files instead of live monitoring, which is exactly the gap newer BaaS stacks tried to close by giving banks direct ledger level visibility and shared case workflows.
-
This was not just a reporting inconvenience. It broke the normal bank workflow. In a standard core, a bank can watch new accounts, transaction counts, suspicious patterns, and limit breaches as they happen. In pooled FBO accounts, those controls stop working unless the tech layer reconstructs the underlying customer ledger for the bank.
-
The first workaround was usually batch exports, weekly customer lists and transaction files sent from fintech or middleware to the bank. But a file only helps if the bank has tooling to ingest it, run AML and KYC checks on it, and escalate cases. Many community banks did not have that downstream analytics stack built for fintech programs.
-
This visibility gap became a real competitive fault line in BaaS. Middleware platforms won early on by making launch easy for fintechs, but later the market shifted toward models that kept bank oversight much tighter, including platforms built around shared ledgers and vertically integrated banks like Column and Lead Bank that keep charter, ledger, payments, and compliance closer together.
Going forward, BaaS infrastructure is moving toward fewer black boxes. The winning model is likely to be the one where the bank, fintech, and infrastructure provider are all looking at the same live operating data, so compliance becomes part of the product workflow instead of an after the fact audit exercise.