Open your point-of-sale app, your invoicing tool, or your e-commerce dashboard and there's a good chance a "business account" or "instant payout" button is staring back at you. It probably isn't a bank that put it there. It's the software company you already use every day — and it's quietly become one of the fastest-growing ways small businesses hold, move, and borrow money.
This is embedded finance: banking-like products — accounts, debit cards, payments, lending — built directly into the software platforms business owners already use, rather than bolted on by a separate bank. The global embedded finance market grew from roughly $148 billion in 2025 to about $197 billion in 2026, and analysts expect it to reach nearly $588 billion by 2030. In the US alone, embedded fintech products are projected to carry more than $7 trillion in transactions by the end of 2026 — up from $2.6 trillion in 2021. Non-bank card issuance is a big piece of that shift: platforms and software companies now account for a rapidly growing share of small-business card volume that used to belong entirely to banks, and revenue for the platforms and "enablers" powering it is projected to climb from roughly $2 billion to $11 billion.
Translation: the decision small business owners used to make once — "which bank do I use?" — is now a decision they make repeatedly, often without fully realizing it, every time they pick a piece of software.
Why Software Companies Became Banks
None of this happened because Shopify or Square woke up one day wanting to be a bank. It happened because owning the financial relationship is extremely good business — and because the infrastructure to do it got cheap and fast to plug in.
A handful of "banking-as-a-service" infrastructure providers now do the regulated, compliance-heavy plumbing so software companies don't have to become banks themselves:
- Stripe (Treasury, Issuing, Capital) powers financial features for platforms including Shopify.
- Marqeta is a dominant card-issuing processor behind many embedded card programs.
- Unit and Cross River Bank let software companies embed accounts and lending with a sponsor bank in the background.
- Parafin powers merchant financing for platforms like Square and DoorDash.
The result is real product, not vaporware. Square built business banking — accounts, savings, and short-term credit — directly into the same dashboard merchants already use to run sales. Shopify Balance gives merchants a business account and debit card tied directly to their store's revenue, with faster access to funds than waiting on a traditional bank transfer; Shopify Capital alone financed $4.2 billion in merchant funding in 2025. Toast does something similar for restaurants, and ServiceTitan for home-services contractors. The pattern repeats across nearly every vertical SaaS category: the software already sees your revenue in real time, so it can underwrite, issue a card, or advance cash faster than a bank that only sees a monthly statement.
Why Owners Are Taking the Deal
The appeal isn't abstract. Two-thirds of small businesses in the US are actively shopping for new banking relationships, and roughly 80% of financial institutions themselves expect to expand small-business offerings over the next two years — a tacit admission that they're losing ground. Meanwhile, credit cards have quietly become the default financing tool for small business: about half of US small businesses use a business credit card, and another quarter run business expenses through a personal one, largely because approval is instant, documentation is minimal, and there's no collateral requirement.
Embedded finance leans directly into that preference. When your point-of-sale system already knows your daily revenue, it can offer same-day underwriting a bank branch simply can't match. When your invoicing software already holds unpaid receivables, it can advance against them without a loan committee. For a business owner who has spent years watching separate tools — payments, payroll, banking, bookkeeping — awkwardly not talk to each other, "it's all just in the app I already use" is a genuinely compelling pitch.
The Trade-Off Nobody Puts in the Onboarding Flow
Convenience comes with a structural catch: when your bank account lives inside a software platform, you're not actually banking with a bank — you're banking with a bank through a software company, and that middle layer matters.
The clearest cautionary tale is the 2024 collapse of Synapse, a fintech middleware provider that routed pooled customer funds from dozens of apps into omnibus "for benefit of" accounts at partner banks. When Synapse failed, upward of 100,000 customers with a combined $265 million in deposits were locked out of their money. The problem wasn't that the underlying bank was uninsured — it was FDIC-insured — it's that FDIC insurance protects against the bank failing, not against the middleman failing to keep accurate records of whose money was whose. Synapse's own subledgers, the records that were supposed to say exactly how much of the pooled account belonged to each individual customer, didn't reconcile, and some customers are still waiting on funds more than a year later. In response, the FDIC has moved to tighten recordkeeping rules for exactly this kind of third-party arrangement.
None of that means embedded banking products are unsafe by default — the large, well-capitalized platforms named above have strong bank-partner relationships and have operated without incident. But it does mean the due-diligence questions are different from "is this a real bank?" A better checklist before you move real operating cash into a platform's banking feature:
- Who is the actual FDIC-insured bank partner, and is it named clearly, not just implied by a badge in the footer?
- Are funds held in individually titled accounts (FBO with per-customer ledgering) rather than one large pooled account with only the platform's own internal records tracking your share?
- What happens to your money if the software company itself goes out of business — not the bank, the software company sitting between you and the bank?
- Can you export your transaction history in an open format if you ever need to leave, or is it locked inside the platform's proprietary dashboard?
That last question matters for reasons beyond switching costs. The more financial activity gets embedded inside a platform, the more your bookkeeping ends up scattered across tools that each hold a partial view of your business — a Shopify Balance transaction here, a Square loan repayment there, a Toast payout somewhere else — none of which necessarily reconciles cleanly against your general ledger unless you deliberately build that habit in.
Bank, Platform, or Both? A Practical Framework
Most owners don't actually face an all-or-nothing choice between "traditional bank" and "embedded finance platform" — in practice, the winning setup is usually both, split by job:
Use the embedded product for speed-sensitive, revenue-tied needs. If your point-of-sale or e-commerce platform already sees every sale in real time, its instant payout, working-capital advance, or revenue-based card is genuinely hard to beat for short-term cash flow smoothing — covering payroll during a slow week, restocking inventory ahead of a busy one, or bridging the gap between a big invoice going out and getting paid. These products are underwritten on data no traditional bank has visibility into, which is exactly why they can say yes in minutes instead of weeks.
Keep a traditional (or at least standalone) bank account for the money you can't afford to lose access to. Reserves, tax withholdings, payroll funding, and anything earmarked for an obligation with a hard deadline belong somewhere you're not exposed to a software vendor's uptime, pricing changes, or — in the Synapse scenario — solvency. A bank account is boring by design, and boring is a feature when the money in it absolutely has to be there when you need it.
Match the tool to the time horizon, not the hype. A good rule of thumb: money you'll touch within days can reasonably live in an embedded product optimized for speed; money you're holding for weeks or months, or that's already spoken for, belongs in an account with the fewest moving parts between you and it. Plenty of owners end up running both simultaneously — a Shopify Balance or Square account for day-to-day sales velocity, and a conventional business checking account as the actual reserve.
The businesses that get burned aren't usually the ones using embedded finance products — they're the ones treating an embedded product as their only financial relationship, with no visibility into where the underlying bank partnership sits or what happens if the software company between them stumbles.
Keeping Your Books Straight When Your Bank Is a Bundle of Apps
Whether your money sits at a traditional bank or inside three different embedded finance products, the accounting fundamentals don't change: every dollar in and out needs to land in the right account, on the right date, categorized correctly. What does change is the discipline required to pull it all together, since embedded finance means your "bank statements" are no longer one PDF a month — they're exports (or, if you're lucky, API feeds) from every platform holding a piece of your cash.
This is where plain-text, version-controlled accounting earns its keep. Beancount.io lets you pull transactions from multiple sources — a Shopify Balance account, a Square loan, a traditional business checking account — into one auditable ledger you fully own, instead of trusting your financial picture to whichever app happens to be showing you a dashboard that day. Every entry is transparent, diffable, and portable, so switching platforms (or just wanting a single source of truth across five of them) never means starting your records over. Get started for free and keep one clear ledger no matter how many places your business banking actually lives.