Have you noticed how many apps now offer a debit card or an account? Ride-hailing, retail, payroll and creator platforms all seem to have joined in. Most of them are not banks. They are using banking as a service, or BaaS, a model in which regulated banks and specialist technology firms provide the plumbing so other companies can offer financial products. Infrastructure startups in this space, and the larger payment companies that buy them, are shaping how it develops.
Banking as a service in one definition
Banking as a service is a way for a non-bank company to offer financial features by plugging into a licensed bank through software. Instead of obtaining a banking licence, building core systems and negotiating card networks, the company connects to APIs, which are standard interfaces for sending requests and receiving responses.
Need to open an account for a customer? Call the API. Issue a card? Call another. Move money? Another.
The layers of the stack
It helps to picture layers.
The bank holds the licence, the deposits and the regulatory obligations; the infrastructure provider builds the software that connects to the bank and offers developer-friendly tools; the brand, sometimes called the fintech or program manager, owns the customer relationship and the app experience; and card networks and payment rails carry the transactions.
Money may be held at the bank even though the brand’s name is on the card. That is why disclosures often say that banking services are provided by a partner bank.
Why brands want banking as a service
For a company with an existing audience, financial products can deepen engagement and create new revenue. A delivery app might offer a card with rewards. A payroll provider might offer instant access to wages. A small business platform might give merchants a business account.
Before banking as a service, this meant years and heavy investment. With it, a modest team can launch in months.
Where the money comes from
For a closer look at one popular product built this way, see our explainer on card issuing for businesses, which covers virtual and physical cards.
Revenue comes from several sources: fees charged to the brand, a share of interchange (the fee merchants pay on card transactions), and sometimes interest on balances. These economics shape what products are viable. A banking as a service card programme with low spending may not cover its costs.
Responsibility and risk in banking as a service
The part people often overlook is compliance. Banks are responsible for knowing their customers, monitoring suspicious activity and meeting regulations, even when a third party handles customer interactions. If the intermediaries are sloppy, problems follow.
Regulators have shown increasing interest in these arrangements, and some programmes have faced scrutiny over oversight and record-keeping. One recurring issue is clarity about where customer funds sit and who is responsible if a middle company fails. In some cases, tracing which customer owns which dollars has been difficult.
This is why serious players invest heavily in reconciliation, the process of matching internal records with the bank’s records, and in audits.
What customers should know
The wider story of why established banks sometimes lag behind these newcomers is told in why corporate banking lags consumer fintech.
Banking as a service also changes who you call when something goes wrong. A frozen card might be a problem with the brand app, the infrastructure provider or the bank, and each will point to the next. Keep screenshots and reference numbers so you can escalate cleanly.
If you use a card from a non-bank brand: check which bank holds your money; understand whether deposits are insured, and under what conditions; keep your own transaction records; know how to contact both the brand and the bank; and read how disputes and fraud claims are handled.
Deposit insurance rules are specific and do not automatically protect against every failure in the chain, so read the fine print where you live.
Why banking as a service attracts consolidation
Infrastructure is a scale business. Large payment and banking technology companies often acquire smaller infrastructure providers to add capabilities, customers and engineering talent. For the smaller firm, joining a larger one can bring stability, licences and distribution. For the buyer, it shortens the path to new products.
For clients of an acquired company, the outcome varies. Services can improve with more resources, or priorities can shift. If you depend on such a provider, plan for continuity and review contracts.
Questions for a company thinking about banking as a service
Which banks and partners are involved, and how stable are they? Who handles compliance, and how are responsibilities divided? How are funds segregated and reconciled? What happens if a partner fails or ends the relationship? Can we move to another provider without rebuilding everything?
That last question, portability, tends to be underestimated until it is needed.
The takeaway
Banking as a service lets almost any brand offer financial products by renting regulated infrastructure. It lowers barriers and has spawned many useful products. It also stretches responsibility across several firms, which demands careful oversight. If you are building or using one of these products, know who holds the money, who answers the phone and what happens when something breaks.
