BaaS Roadmaps Captured by Giants
Banking-as-a-Service: The $1T Market to Build the Twilio of Embedded Finance
This is the core tradeoff in BaaS, landing a giant fintech can create the business, but it can also turn the platform into a custom engineering shop for one customer. The biggest fintechs need unusual controls across KYC, card logic, ledgers, disputes, and compliance, and as volume scales they win more pricing power too. That leaves less product attention for smaller fintechs and for non fintech companies that just want a simpler embedded finance layer.
-
Marqeta had about 160 customers, roughly $488M in yearly revenue, and 73% of revenue from Square in 2021. That is a very high ACV, high concentration model. It works financially, but it naturally pulls roadmap decisions toward the needs of the largest account.
-
The reason is product complexity. Large fintechs do not just want a generic card API. They want custom authorization rules, faster onboarding, tighter fraud controls, dispute workflows, sponsor bank coordination, and room to bend the program around their exact business model.
-
That creates an opening for long tail BaaS players. Embedded finance customers like retailers, SaaS platforms, and marketplaces usually want finance to support the main product, not to be the product itself. They are less likely to demand a bespoke stack, and they produce a broader customer base with less concentration risk.
The market is moving toward a split structure. One group will keep serving a small number of very large fintechs with deep customization and heavy services. Another group will win by standardizing common workflows for thousands of embedded finance customers. The companies that build the cleanest default product for that long tail should capture the next wave of BaaS growth.