Banking as a service puts bank capabilities inside other products

Banking as a service, or BaaS, is a partnership model that lets a nonbank offer financial features inside its own app or service by connecting to banking infrastructure through application programming interfaces, known as APIs. The customer sees the nonbank’s brand and interface; a licensed bank supplies the underlying banking capabilities, while a technology layer may connect the two. PwC and Stripe describe the model as a route to accounts, cards, payments and lending without the customer-facing business building banking infrastructure itself.

An API is a defined software connection that lets one system request an action or exchange data with another. In BaaS, APIs can support functions such as account opening, card applications and money movement. The arrangement can shorten a product launch and reduce infrastructure work, according to the providers and advisers that describe the model, but it also creates dependencies around security, reliability, integration and customer support.

How banking as a service works

A typical BaaS arrangement has three roles. They can sit in separate companies, or some functions can be combined depending on the provider and market.

1. Licensed bank: The bank supplies banking infrastructure and products. PwC says BaaS providers handle back-end functions including regulatory compliance, security and risk management.
2. BaaS platform or technology intermediary: This optional middle layer supplies APIs and middleware, software that translates between the bank’s systems and the partner’s product. Stripe characterises BaaS platforms as intermediaries between banks and companies embedding financial functions.
3. Distribution partner: The nonbank, such as a software, commerce or gig-economy business, designs the customer-facing service and presents the feature under its own brand. It is commonly the business through which end users encounter the product.

The flow is therefore: bank capability, API or platform connection, branded customer experience. A customer may open an account or receive a payment within the partner’s application, while the underlying banking function is supplied through the partnership.

What a business can offer through BaaS

The available products depend on the bank, platform and arrangement. Sources describing BaaS commonly include deposit accounts, card issuance, payment processing and money movement, and lending. FIS cites account opening, credit-card applications, and transfers through ACH and wire as examples of API-enabled functions.

Illustrative sequence: A marketplace wants sellers to receive proceeds in its own dashboard. It can use APIs to support an account feature, show a balance in its branded interface and initiate a payout. The bank and technical partners provide the underlying banking and connection capabilities; the marketplace builds the customer journey around them. The parties need to establish the allocation of operations and support rather than assume it from the label “BaaS.”

BaaS and embedded finance are related

Embedded finance describes a financial service appearing inside a nonfinancial product at the point of use. BaaS can be one means of enabling that outcome. FIS describes its BaaS technology as facilitating embedded finance, while PwC describes BaaS as a back-end model through which a partner can place banking products in its own offering.

The distinction helps frame an implementation. “Embedded finance” describes what a customer experiences, such as paying, holding funds or applying for a card without leaving a software product. “BaaS” describes the partnership and technical route used to deliver a banking capability.

Why banks and nonbanks use the model

For a nonbank, the attraction is access to financial functions without building extensive banking infrastructure. PwC says this can reduce time to market and entry barriers for financial innovators. Stripe similarly presents quicker integration and less in-house development as potential benefits, not automatic results.

For a bank, the model can turn existing infrastructure, licences and risk-management expertise into services for partners. PwC says banks may use such arrangements to seek additional fee income, new customer segments and more diversified revenue. The commercial result will depend on product economics, partner fit and the cost of operating the relationship.

Questions to answer before adopting BaaS

• Which product is being embedded? Specify whether the goal is an account, card, payment flow, payout or lending function, then establish what the bank and platform actually support.
• Can existing systems connect cleanly? Stripe warns that integration can be difficult where internal systems were not designed for external services, potentially extending development and raising costs.
• How will sensitive data be protected? Financial features handle bank and identity information. Stripe identifies security and fraud exposure as a central consideration.
• What happens during an outage or failed transaction? Provider downtime can delay or interrupt transactions, Stripe says. Teams should examine reliability information and plans for technical failures.
• Who helps the end customer? The branded business, bank and platform should establish how customer queries and exceptions will be handled, particularly because the user encounters the product through the distribution partner.

Frequently asked questions

Does banking as a service give a nonbank a bank charter?

In a BaaS arrangement, the licensed bank supplies the underlying banking infrastructure and capabilities, while the nonbank integrates financial features into its customer-facing product. PwC and Stripe describe the model as a way for nonbanks to offer those features through partnerships and APIs.

What products can banking as a service support?

Common examples include deposit accounts, debit or credit cards, payments and money movement, and lending. The particular products available depend on the bank, platform and commercial arrangement.

What are the main risks of banking as a service?

Stripe identifies sensitive-data security, provider reliability and uptime, technical integration complexity, and customer support as key considerations. A provider outage can delay or interrupt transactions, making technical-failure planning part of assessing an arrangement.

Sources

• What does Banking as a Service (BaaS) mean for business? — www.pwc.com
• What is banking-as-a-service (BaaS)? — stripe.com
• Banking as a Service - Embedded Finance — www.fisglobal.com