Your Bank Isn’t a Bank Anymore. It’s a Software License. Here’s the $74 Billion Secret Hiding in Your Banking App
I opened my Uber app last week to check a ride receipt, and there it was: a little banner offering me a debit card with 3% cashback on gas.
Uber. A ride-hailing company. Offering me a bank card.
That’s not a glitch. That’s Banking as a Service, and it’s quietly rewiring who gets to call themselves a “bank.”
If you’ve used Chime, Cash App, Shopify Balance, or even booked a flight and been offered a “travel card” mid-checkout you’ve already touched BaaS. You just didn’t know the invisible plumbing behind it used to belong exclusively to century-old banks with marble lobbies and armed guards.
Now it belongs to an API.
So What Actually Is This Thing?
Strip away the jargon and it’s simple: Banking as a Service lets any company a gym app, a payroll platform, a trucking startup plug into a licensed bank’s infrastructure and offer real financial products under their own brand. Debit cards. Checking accounts. Loans. Even crypto wallets.
The tech company builds the app people see. A regulated bank sits quietly behind the curtain, holding the actual license, the actual deposits, the actual compliance headache. The customer never sees the bank’s name. They just see “Uber Card” or “Shopify Balance.”
Think of it like Airbnb for banking licenses. You don’t need to own the building. You just need the keys.
Why Every Startup Suddenly Wants to Be a Bank
Here’s the part that should make founders sit up: fintech companies used to spend 12 to 18 months and millions of dollars chasing their own banking charter before they could touch a single dollar of customer money.
BaaS collapsed that timeline into weeks.
A company like Synapse, Unit, or Treasury Prime hands a startup pre-built rails account creation, card issuing, ACH transfers, fraud checks through an API. The startup writes some code, signs a partnership agreement with a sponsor bank, and suddenly it’s issuing debit cards from a garage office in Austin.
That’s why your dentist’s office app now offers a savings account. Why your rewards app for coffee shops suddenly has a “cash back” wallet. Why airlines are becoming quasi-banks. It’s not that these companies love banking. It’s that banking became cheap enough to bolt onto anything.
The Number Nobody’s Talking About
Get Kiara’s stories in your inbox
Join Medium for free to get updates from this writer.
Analysts are projecting the global Banking as a Service market could balloon past $74 billion within the next few years, and some estimates push even higher once embedded lending and insurance get folded into the mix. That’s not a niche. That’s an entire shadow banking layer growing underneath the one you grew up with.
And the banks providing the actual licenses? Smaller, regional players are cashing in hard. A community bank in the Midwest with $2 billion in assets can suddenly touch millions of customers nationwide — not by opening branches, but by quietly powering the backend of ten fintech apps at once.
It’s a strange trade. The community bank loses the customer relationship. It gains fee income and deposit volume it could never have reached alone.
But Here’s Where It Gets Messy
Remember Synapse? If you don’t, you should.
In 2024, the BaaS middleman Synapse collapsed into bankruptcy, and the fallout froze the accounts of hundreds of thousands of people who thought they had money sitting safely in a “bank account” through apps like Yotta and Juno. Turns out the money was tangled in a ledger dispute between Synapse and its partner banks, and regular people — teachers, gig workers, people saving for rent — couldn’t touch their own cash for months.
That’s the ugly underside of this whole model. When you tap “sign up” on a slick fintech app, you’re often trusting a chain of three or four companies you’ve never heard of, none of whom you can walk into and yell at when something breaks.
Regulators noticed. The FDIC and OCC have been tightening scrutiny on sponsor banks throughout 2025 and into 2026, pushing for clearer reconciliation of who actually holds whose money. Some smaller sponsor banks have started pulling back from BaaS partnerships entirely because the compliance risk outweighed the fee income.
So the gold rush is real, but so are the sinkholes.
Who Wins and Who Gets Left Holding the Bag
The winners right now: infrastructure players like Stripe, Marqeta, and Galileo, who provide the actual card-issuing and payment rails without ever touching regulatory risk directly. They’re the picks-and-shovels sellers of this gold rush, and they’re profiting whether the fintech apps built on top of them succeed or implode.
The people taking the real risk: everyday users who assume “bank account” means the same protections everywhere, when in reality the FDIC insurance chain in a BaaS stack can be genuinely confusing, layered through multiple intermediary accounts.
The quiet losers, potentially: the sponsor banks themselves, if they’ve underpriced the risk of powering ten fintech apps they don’t fully control.
Where This Is Actually Headed
Embedded finance is graduating from a buzzword into default infrastructure. Expect BaaS to expand deeper into lending, insurance, and even embedded investing your grocery delivery app offering you a micro-loan at checkout isn’t far off, and in some markets it already exists.
The next fight isn’t over whether Banking as a Service works. It clearly does — the market size proves that. The fight is over who takes responsibility when the invisible plumbing leaks.
Next time an app you didn’t expect offers you a debit card, you’re not looking at a gimmick. You’re looking at the new architecture of banking itself — decentralized not in the crypto sense, but in the sense that the bank you’re using might not even know your name.
