Neobanks as Thin BaaS Wrappers
The future of interchange
The real weakness of many neobanks was that they owned the brand and app, but not enough of the product or economics underneath. A customer saw a polished mobile account, but behind the scenes the bank account, card program, compliance, and much of the payments stack were rented from a BaaS platform and sponsor bank. That made launch easy, but also made copycat products easy and left little room to support high customer acquisition costs.
-
The stack often had three layers. The neobank handled marketing, design, and support. The BaaS provider stitched together card issuing, ledgering, compliance workflows, and bank integrations. The sponsor bank held the charter and legally issued the accounts or cards. If the top layer changed, most of the core rails stayed the same.
-
This structure worked best when distribution was unique. Chime broke out by targeting paycheck to paycheck consumers with early wage access, but most neobanks still earned mainly from debit interchange, around 50 cents per $100 spent in Chime's case, which is a thin revenue stream unless usage and retention are unusually strong.
-
The survivors moved beyond a single debit card and checking account. The pattern was specialization, more products, or both. That meant lending, subscriptions, expense software, payroll links, or deeper workflow tools, which raised revenue per customer and gave people a reason to stay beyond a nicer app.
The market is moving away from standalone neobanks and toward embedded finance inside software products that already own distribution. The winners will control a real workflow, then add accounts, cards, lending, and money movement on top. In that world, BaaS becomes infrastructure, while the enduring value shifts to whoever owns the customer relationship and the daily use case.