Sponsor Bank
A sponsor bank is a chartered bank that lets a non-bank company offer banking products under its charter. The fintech builds the app and owns the customer relationship; the bank holds the deposits, provides access to the payment rails, and carries the regulatory obligations. That last clause is the one that matters, because the bank remains accountable to its regulators for compliance failures no matter what the partnership agreement says.
| Also called | Partner bank, BaaS bank, bank sponsor |
| Model | Banking as a Service — a chartered bank rents regulated capability to a non-bank |
| The bank provides | The charter, deposit insurance, payment rail access, and regulatory standing |
| The fintech provides | The product, the interface, and the customer relationship |
| Who is examined | The bank — regulators supervise the charter holder, not the partner |
| Compliance obligations | BSA/AML, CIP, OFAC screening, fair lending, consumer protection |
| Delegation limit | Execution can be delegated; accountability cannot |
| Recent supervisory focus | Third-party risk management and oversight of fintech partners |
How the model works, and where it strains
The appeal is obvious on both sides. A chartered bank is expensive and slow to build; a fintech wanting to offer deposit accounts, cards or payments can reach market far faster by renting access to one. The bank, in turn, gains deposits and fee income it could not originate through its own branches.
The strain is structural rather than incidental. The bank carries the regulatory obligation, but the fintech operates nearly everything the obligation attaches to — it onboards the customer, runs the identity checks, sees the transactions, and holds the records. The bank is answerable for a Customer Identification Program it does not itself run.
That arrangement works when the bank has genuine visibility and fails when it has a contract instead. Supervisory attention has landed squarely on the difference.
What the enforcement record shows
The period from 2023 onward reset expectations for this model, and the specifics are worth stating rather than gesturing at.
Evolve Bank & Trust received a Federal Reserve cease-and-desist in June 2024 citing weak AML and BSA programs, OFAC-related deficiencies, and ineffective oversight of its fintech partnerships. It was not an isolated action — the FDIC, OCC and Federal Reserve issued consent orders against a substantial number of sponsor banks through 2024 and 2025, with BSA/AML program deficiencies the recurring theme.
The Synapse collapse in May 2024 demonstrated the consumer-facing version of the same weakness. When the middleware provider failed, roughly $265 million of end-user deposits held across several partner banks became inaccessible, because the records reconciling who owned what sat with the intermediary rather than with the banks.
The supervisory expectation that emerged is concrete: a sponsor bank should have current visibility into each partner’s compliance performance and be able to produce a complete, accurate customer file on request — not eventually, and not by asking the fintech.
Why this matters for identity verification
Every one of those expectations resolves to the quality of what was captured at onboarding, by the fintech, on the bank’s behalf.
A bank asked to evidence how a customer’s identity was established needs an answer better than “our partner ran a check.” It needs to know which document was presented, whether it was authenticated rather than merely read, whether the person was bound to it biometrically, and where that evidence is held. Where the partner accepted a photograph of a document and a database name match, the bank inherits that weakness and will answer for it.
This makes identity verification a third-party risk control in the BaaS model, not only a fraud control. The practical requirements are consistent standards applied across every partner program, evidence retained in a form the bank can retrieve, and oversight that does not depend on the partner self-reporting. Identity document verification that produces an auditable record is what makes that answerable, and Command Center visibility across programs is what turns a contractual obligation into an observable one. For the underlying obligations themselves, KYC and AML sits with the charter, wherever the work happens.
What a sponsor bank arrangement can’t do
It cannot transfer regulatory accountability. Contractual allocation of responsibility governs the commercial relationship between the parties. It does not move the supervisory obligation off the charter.
It does not make the fintech supervised. Regulators examine the bank. A partner’s weaknesses appear as the bank’s findings.
Indemnities are not a control. A contractual promise to cover losses does not prevent a consent order, and it is only worth what the counterparty is worth.
It does not guarantee customers can reach their money. Where reconciliation records sit with an intermediary rather than the bank, a failure upstream can strand deposits regardless of insurance.
Frequently asked questions
What does a sponsor bank do?
It lets a non-bank company offer banking products under its charter — holding the deposits, providing access to payment rails, and carrying the regulatory obligations — while the fintech builds the product and owns the customer relationship.
Who is responsible for compliance in a BaaS partnership?
The chartered bank, regardless of how the partnership agreement allocates the work. Execution of KYC, transaction monitoring and screening can be delegated to the fintech, but supervisory accountability stays with the charter holder, who is the party regulators examine.
Why have sponsor banks faced so many consent orders?
Because the model concentrates obligation and operation in different places. The bank is accountable for programs the fintech actually runs, and where oversight amounted to contractual assurance rather than genuine visibility, examiners found BSA/AML deficiencies. Third-party risk management has been the recurring theme.
What is the difference between a sponsor bank and Banking as a Service?
Banking as a Service is the model — a chartered institution making regulated capability available to non-banks. The sponsor bank is the institution playing that role in a specific partnership. The terms are often used interchangeably, but one is the arrangement and the other is a party to it.
Related reading
- Banking as a Service — the model this bank is one side of
- Customer Identification Program — the obligation the bank answers for and the fintech usually performs
- AML audit — the independent testing that examines whether the oversight is real
- Regulatory reporting — the filings the charter holder remains responsible for
