Subscribe to get high-signal insights on how modern fintech is built.

analysis

Fintechs Are Done Renting Banks

Chime bought Stride Bank for $590 million. Revolut got its US charter. Block applied for one. Three in three months.

By Alex Kugell ·

Chime announced this week that it's acquiring Stride Bank, a nationally chartered bank based in Oklahoma, for $590 million. Chime has been a Stride client for years, using Stride's charter to hold deposits and issue debit cards. Now Chime is buying the bank it used to rent from.

Chime is the third major fintech to make this move in 2026. Revolut secured a conditional US banking license in September. Block applied to establish Builders Bank, a national trust bank, the same month. Each took a different path to the same destination: own the charter.

Why fintechs rented in the first place

Starting a bank from scratch requires a charter, which takes years and costs tens of millions in legal and regulatory work before you process a single transaction. The BaaS model (Banking-as-a-Service) offered a shortcut. A fintech partners with a chartered bank, the bank provides the regulatory umbrella, and the fintech builds the customer experience on top.

This model launched an entire generation of neobanks. Chime used Stride and Bancorp. Mercury used Choice Financial and Evolve. Brex used Emigrant Bank. The fintech got to market in months instead of years, and the sponsor bank earned revenue on deposits it never had to acquire.

The arrangement worked until it didn't.

What breaks at scale

A BaaS relationship is a dependency. The sponsor bank controls the charter, the compliance program, the BSA/AML obligations, and ultimately the relationship with regulators. The fintech controls the product and the customer. When both sides are small, the partnership is manageable. When the fintech scales to millions of accounts, the dependency becomes a constraint.

Chime has roughly 22 million accounts. Every compliance decision, every product change that touches the banking layer, every new feature that requires regulatory approval flows through the sponsor bank.

At that scale, the fintech is the largest client of a bank that wasn't built to serve that kind of volume. The sponsor bank's compliance team becomes the bottleneck for the fintech's product roadmap.

Regulators have also tightened scrutiny on BaaS relationships. The FDIC and OCC have issued guidance on third-party risk management that puts more responsibility on the sponsor bank for oversight of its fintech partners.

Synapse's collapse in 2024, which left thousands of customer accounts in limbo, accelerated that scrutiny. Sponsor banks are now more cautious about onboarding large fintech clients, and more expensive when they do.

The $590 million math

Chime paid $590 million. Run the numbers the other way.

Chime reportedly generates over $1.5 billion in annual revenue, primarily from interchange on debit card transactions. A meaningful cut of that revenue goes to the sponsor bank as part of the BaaS arrangement.

Interchange splits, compliance fees, deposit revenue sharing, and minimum balance requirements all add up.

Owning the charter eliminates the split. Chime keeps the full interchange, earns interest on its own deposits, and controls its own compliance program.

If the BaaS fees run even 5% to 10% of revenue, the acquisition pays for itself within a few years from fee elimination alone. That's before accounting for the product velocity gained by removing the sponsor bank as a dependency.

Revolut's math is similar. At 80 million global customers and a $115 billion valuation, Revolut can't build its US operation on someone else's charter. The conditional license lets Revolut hold deposits directly, offer lending products, and control its own regulatory relationships in the market that matters most for its IPO narrative.

What this means for BaaS

The BaaS model isn't dead. For fintechs that need deposit accounts or card programs, it's still the fastest way to launch.

For fintechs processing under a million accounts, BaaS still makes sense. The regulatory overhead of owning a charter, the capital requirements, the examination cycle, the compliance staffing, these are fixed costs that only pencil out at scale.

A startup burning $3 million a month can't absorb the cost of maintaining a charter.

For fintechs that have scaled past that threshold, the BaaS model becomes the thing they need to outgrow. Chime, Revolut, and Block all reached the point where the cost of renting exceeded the cost of owning.

The $590 million Chime paid for Stride is a large number. It's a smaller number than the cumulative cost of remaining dependent on a sponsor bank for the next decade.

The sponsor banks that built their business on BaaS revenue are watching their largest clients either leave or get acquired. Stride, Bancorp, Evolve, Choice.

Stride's outcome, bought by its biggest client for $590 million, may be the best exit a BaaS bank can hope for.

Sources

Alex Kugell
Alex KugellAI/ML Engineer, Fintech Infrastructure

Writes Ledger Drift. Engineer building AI systems and financial infrastructure. Open source contributor to x402, ACK, and MPP.

Frequently Asked Questions

Why did Chime buy Stride Bank instead of continuing to use it as a partner?
Chime has roughly 22 million accounts, making it Stride's largest client by a wide margin. At that scale, every compliance decision and product change has to flow through a sponsor bank that wasn't built for that volume. Owning the charter eliminates the revenue split on interchange, gives Chime interest income on its own deposits, and removes the regulatory dependency that slows its product roadmap.
How quickly does a $590 million bank acquisition pay for itself?
If BaaS fees, including interchange splits, compliance charges, and deposit revenue sharing, run even 5-10% of Chime's reported $1.5 billion in annual revenue, the acquisition breaks even within a few years from fee elimination alone. Product velocity improvements from removing the sponsor bank dependency are harder to quantify but structurally more valuable over a decade.
Is the Banking-as-a-Service model dying?
Not for smaller fintechs. Companies processing under a million accounts still benefit from partnering with a chartered bank because the fixed costs of owning a charter, capital requirements, examination cycles, compliance teams, don't make financial sense at that scale. What's changing is that the largest BaaS clients are outgrowing the model, and sponsor banks are watching their biggest revenue sources either leave or acquire them.
Why did three major fintechs pursue bank charters in the same quarter?
Chime, Revolut, and Block all hit the same inflection point from different directions. Chime bought its sponsor bank outright. Revolut secured a conditional US license to support its IPO narrative and US expansion. Block applied for a national trust bank charter for bitcoin and stablecoin custody. Each took a different path, but the driver is the same: at scale, the cost of renting a charter exceeds the cost of owning one.
What happened to Synapse that accelerated fintechs moving away from BaaS?
Synapse's 2024 collapse left thousands of customer accounts frozen and exposed an $85 million gap between what customers were owed and what the partner banks held. Regulators tightened scrutiny on BaaS relationships afterward, and sponsor banks became more cautious and expensive when onboarding large fintech clients. The incident made the dependency risk of the BaaS model visible in a way that theory couldn't.

Built by Trio, a fintech-native engineering partner helping teams build the next generation of financial technology and infrastructure.

Subscribe to Ledger Drift for high-signal insights into how modern fintech is built, from systems to code to teams.

Keep reading

fintechCash Flow Infrastructure Is a Platform DecisionCash flow starts as a product feature and becomes infrastructure the moment two systems need the same balance.
ai & mlAML's Real Bottleneck Is the NarrativeTransaction monitoring generates the alerts, but the four-hour SAR narrative is where compliance teams actually lose their week.
anatomySpade and the Payments Data LayerCard authorization messages give issuers 40 bytes to identify a merchant, so Spade built the side channel that carries the rest.
View more ›