BaaS Feeder Channel for Lithic
Bo Jiang, co-founder and CEO of Lithic, on the key primitives in card issuing
The key point is that BaaS expands Lithic’s market more than it shrinks it. All in one BaaS platforms are best when a company wants one vendor to handle the bank relationship, compliance stack, and launch work. Lithic fits later, when the product gets more complex and the customer wants tighter control over card rules, KYC flows, transaction monitoring, or program design. That makes BaaS a feeder channel for higher complexity issuing.
-
BaaS providers often sit on top of issuer processors rather than replacing them. In practice, many all in one platforms bundle sponsor banks, compliance, accounts, and payments, then use specialists underneath for card issuing. That creates a natural partnership path where BaaS wins the simple launch and Lithic powers the card layer.
-
The dividing line is usually clear. Early neobanks and software companies that want to avoid direct bank work tend to prefer BaaS. More mature fintechs with unusual funds flows, multiple card programs, or custom controls tend to outgrow the all in one model and want modular infrastructure they can swap and tune.
-
This is the same unbundling pattern that happened in payments. Marqeta opened card issuing as an API layer, then newer providers like Lithic pushed deeper into developer friendly primitives, while BaaS platforms assembled broader packages around them. The result is a larger ecosystem, not one winner taking all.
Going forward, the market is likely to separate even more cleanly into broad platforms and deep specialists. As compliance and bank oversight get more demanding, BaaS platforms will keep owning fast, managed launches, while point providers like Lithic gain leverage where customers need precision, flexibility, and infrastructure that can plug into a larger stack.