BaaS Requires Full-Stack Compliance
Roy Ng, EVP, Chief Business Officer at FIS, on the future of BaaS
This is why BaaS has consolidated around full stack operators instead of pure self serve APIs. To launch a bank account or card program, a platform has to coordinate sponsor bank approval, KYC and KYB checks, ledgering, processor connectivity, disclosures, transaction monitoring, and the exact money movement path. Bond built itself around that program manager role, and after joining FIS it leaned even harder into compliance tooling, bank workflows, and standardized enterprise launches.
-
Going straight to an issuer processor is only one ingredient. A company still needs a bank partner, KYC vendors, a ledger, compliance operations, and reporting, which is why all in one BaaS platforms emerged above processors like Marqeta and Lithic.
-
The hard part is not just moving money, it is proving to the bank and regulators that every step is controlled. Bond describes the needed pieces as accounts, cards, and money movement, wrapped in data systems that show pass and fail rates, reviews, issued cards, spend, and transaction details.
-
That complexity changes the customer mix. Early BaaS sold to startups that wanted speed, but tighter oversight has pushed the market toward larger enterprises and banks that prefer standardized workflows, dedicated teams, and broad platforms over assembling many point solutions themselves.
The next phase of embedded finance belongs to platforms that make regulated workflows feel repeatable, not infinitely customizable. That favors incumbents and scaled intermediaries that can package bank relationships, compliance operations, and modular infrastructure into a product that large software companies and banks can launch quickly and extend over time.