WaaS vs. Neobanking vs. BaaS: Untangling the Confusion

A founder who understands that a Wallet-as-a-Service API is not a bank account usually runs into a second, closely related question almost immediately: is it a neobank, then? And where does Banking-as-a-Service fit into all of this? The three terms get used interchangeably in vendor marketing constantly, which is exactly why the confusion persists.

They are not the same thing. This piece untangles them, because picking the wrong mental model here tends to shape a company's entire go-to-market strategy, often before anyone realises the assumption was wrong.

WaaS vs Neobanking: What's the Real Difference?

A neobank is a consumer or business-facing brand offering banking-like services, usually built on top of a Banking-as-a-Service or Wallet-as-a-Service provider underneath. A Wallet-as-a-Service API is the infrastructure a neobank, or any other company, can use to build that offering. One is a product. The other is plumbing.

This is where the confusion usually starts. Neobanks such as Chime or Revolut present themselves as banks in every visible way: a debit card, an app, a routing number. Most do not hold a banking licence themselves. They partner with a licensed bank behind the scenes, often through a Banking-as-a-Service arrangement, and build their entire consumer experience on top of that partner's rails.

A company using a Wallet-as-a-Service API is not necessarily trying to become a neobank at all. A gig-economy platform that wants to let drivers hold and spend their earnings is not building a bank. It is adding a wallet feature to an existing product. A cross-border marketplace that wants sellers to hold multi-currency balances is not launching a banking brand either. It is using wallet infrastructure to solve a specific payments problem inside a product that was never meant to look like a bank in the first place.

The confusion between the two comes from the fact that neobanks often use WaaS or BaaS infrastructure to exist. But using wallet infrastructure does not automatically make a company a neobank, any more than using cloud servers makes a company a cloud provider. The infrastructure and the brand built on top of it are two separate decisions, and a founder can use one without building the other.

What Is the Difference Between BaaS and WaaS?

Banking-as-a-Service typically gives a company access to full banking primitives, including individually numbered bank accounts, debit cards, and sometimes lending products, usually through a licensed bank partner. Wallet-as-a-Service is narrower in scope. It focuses specifically on stored-value wallets: balances that move money without necessarily issuing a full bank account tied to each user.

The most practical difference shows up in what each is best suited for. BaaS tends to fit companies that want to offer something functionally identical to a bank account, complete with account numbers and routing details a user could give to their employer for direct deposit. WaaS tends to fit companies that want a lighter-weight balance system, often for internal marketplace transactions, gig worker payouts, or holding funds temporarily before a payout event.

Many providers blur this line deliberately, offering wallet functionality alongside card issuing and BaaS-style account features under one roof. That is a business decision on the provider's part, not a rule about what wallets are allowed to be. A founder evaluating providers should ask directly which model a given feature actually falls under, since "wallet" and "account" get used interchangeably in vendor marketing far more often than the underlying architecture would justify.

Do I Need a Banking Licence to Launch a Wallet?

No, not if you are working with the right infrastructure provider. This is arguably the single most attractive thing about the Wallet-as-a-Service model, and the reason it exists at all.

Banking licences take years to obtain in most jurisdictions, cost enormous sums, and come with ongoing regulatory obligations that a young fintech is rarely equipped to carry alone. A WaaS provider that already holds the relevant licences, or partners with an institution that does, absorbs that regulatory burden. The client company builds its product on top of an already-compliant foundation instead of becoming a licensed entity itself. This is the same custody relationship described in Part 1: the fintech handles the product experience, while a licensed partner sits underneath, safeguarding the actual funds.

One might then ask, can a fintech startup offer wallets without becoming a bank? Yes, and this is precisely the arrangement most fintech startups choose. The startup focuses on the product experience, the customer relationship, and the specific problem it is solving, while the WaaS provider handles custody, compliance, and the regulatory relationships underneath. This is also why a purpose-built infrastructure provider, rather than a generic payments API, tends to serve fintech founders better: the compliance layer needs to be embedded from day one, not added as an afterthought once regulators start asking questions.

Where This Leaves a Founder

Three labels, three different jobs. A neobank is the brand a customer sees. Banking-as-a-Service and Wallet-as-a-Service are two different flavours of infrastructure sitting underneath that brand, or underneath a wallet feature bolted onto a completely different kind of product. Knowing which one you actually need, rather than which one sounds more impressive in a pitch deck, saves months of rebuilding later.

Part 3 of this series, How to Actually Launch a Wallet, picks up from here: what the compliance layer behind a wallet actually needs to do, where wallets show up in real products, and how to evaluate a provider before signing anything.

This is Part 2 of a three-part series on Wallet-as-a-Service infrastructure. Part 1, What Is a Wallet-as-a-Service API?, covers the basic definition and mechanics.