Giant Clients vs Scalable BaaS
Senior BaaS platform executive on the rise of banking-as-a-service 2.0
Landing a giant fintech can make a BaaS provider bigger, but less platform like. A customer like Square needs custom controls, custom compliance flows, and contract terms that improve as volume rises, so the provider spends product time serving one program instead of building reusable features for many customers. That is why Marqeta grew huge with a small customer base and still ended up with revenue heavily concentrated in Square.
-
Marqeta shows the tradeoff clearly. It helped power Cash App and reached about $60B in transaction volume by 2020, but Square drove about 70% of revenue in 2020 and 73% in early 2021, which meant one breakout customer shaped both economics and priorities.
-
The practical reason is that large fintechs treat infrastructure as core product. They want exact controls over card logic, disputes, KYC, settlement, and support workflows. If a platform cannot match that, the fintech often goes straight to a bank and assembles more of the stack itself.
-
This splits the market in two. Upmarket providers become high touch vendors with a few very large accounts, while platforms like Unit, Productfy, and others aim at the long tail of smaller fintechs and embedded finance customers, hoping a handful mature into major revenue contributors.
The market is moving toward a clearer divide between enterprise infrastructure built around a few demanding fintechs and broader API platforms built for many smaller programs. The winners in BaaS 2.0 will be the companies that choose one lane early, either serving giant customers with deep customization or serving the long tail with standardized products that can scale without being captured by one roadmap.