Non-Banks Are Winning Business Banking
Business banking is splitting in two, and the line runs through engineering, not regulation.
You incorporate a company. You need a business bank account. At your local bank, this takes two weeks of paperwork, three rounds of document requests, and a branch visit. At Mercury, it takes 10 minutes and a browser.
Same KYC requirements, same beneficial ownership rules, same regulatory framework. The difference is how the onboarding pipeline is built.
The easy explanation is that banks are slow and fintechs are fast. But J.D. Power's 2026 small business banking study shows satisfaction rising for the fifth consecutive year, up 54 points over the last four. Banks serve their existing customers well enough, but they're losing the ones who never walk through the door.
The onboarding gap
Opening a business account means Know Your Business verification, from entity documents and beneficial ownership identification to sanctions screening and risk assessment. The regulatory requirements are identical whether you're Chase or Mercury.
At most banks, KYB takes about 14 days. The bottleneck is the process, not the regulation. Manual document review and fragmented verification systems that force back-and-forth email chains requesting the same information in different formats. A compliance officer reviews each application individually, often pulling from multiple databases that don't talk to each other.
Mercury does the same checks in minutes because it automated the pipeline. Entity verification runs through API calls to state registries, beneficial ownership matching uses automated identity resolution, and sanctions screening hits real-time watchlist APIs. The regulatory bar is the same, but the engineering is different.
Onboarding speed is a funnel filter. A founder incorporating through Stripe Atlas can have a Mercury account open before the IRS issues their EIN. A founder walking into a bank branch starts a two-week process that competes for attention with everything else in their first month of operations. The 10-minute path captures the customer while the two-week path loses them before the account is active.
The API gap
Every Mercury account ships with read-and-write API access. You can pull transactions, check balances, initiate ACH payments, and build automations on top of your own banking data from day one. This is the default, not a premium tier.
Ramp built its entire product on this principle. It processed over $55 billion in payment volume in 2024, generates roughly $1.5 billion in annualized revenue, because it treats the corporate card as an integration surface, not a standalone product. Spend management, receipt matching, accounting sync, real-time budget controls, and approval workflows all ship as one product because the architecture was designed for it.
Banks add these features through vendor integrations bolted onto core banking systems that, in many cases, predate the internet. A typical community bank runs on a core from FIS, Fiserv, or Jack Henry. Adding a real-time expense management feature means integrating with that core's API layer, which was designed for batch processing and overnight reconciliation.
Banks can technically offer everything Ramp offers. The gap is velocity, not capability. A bank needs 12 to 18 months and a systems integrator to ship what Ramp builds in a quarter.
The data advantage
When Ramp issues you a corporate card, it sees the transaction amount, the merchant category code, your accounting GL code, the budget it was charged against, and which employee made the purchase. When your bank issues a debit card, it sees only the ISO 8583 authorization message, which carries the amount, merchant ID, and timestamp.
| Non-bank sees | Bank sees | |
|---|---|---|
| Amount | $847.30 | $847.30 |
| Merchant | AWS us-east-1 | AMAZON WEB SERVICES |
| Category | Cloud infrastructure | MCC 7372 |
| GL code | 6200 – SaaS | — |
| Budget | Engineering / Q4 | — |
| Purchaser | Jamie L., Eng Lead | — |
| Receipt | Auto-matched | — |
The non-bank owns the context around the transaction, while the bank owns the transaction itself. And context determines what products you can build on top.
This is why Ramp can auto-categorize expenses, flag duplicate subscriptions, and enforce spend policies in real time. The bank would need to integrate with your accounting software, HR system, approval workflow, and expense policies to see what Ramp sees natively. Most banks don't, because the integration cost exceeds the revenue from a small business account.
Mercury made the same bet from the deposit side. Over 300,000 clients use Mercury not because it offers higher interest rates or lower fees, but because the banking data connects to everything else. The account is a node in a financial operating system, not a destination you log into separately.
Where banks still win
Non-banks have captured the routine layer of business banking, from accounts and cards to payments and expense management. But the complex layer still belongs to banks.
Mercury can open your account in 10 minutes, but it can't underwrite a $2 million line of credit. Banks have capital reserves and lending licenses backed by decades of credit data that non-banks can't replicate. Small business loans have fallen from 24% to 12% of community banks' total loan portfolios over two decades, according to the Kansas City Fed, but the absolute volume is still enormous, and no non-bank has a comparable lending infrastructure.
Treasury management for mid-market and larger businesses is another moat. Cash concentration, zero-balance accounts, lockbox services, and foreign exchange all depend on a charter, capital reserves, and direct access to payment rails. Fintechs partner with banks to offer simplified versions, but the full suite still lives inside chartered institutions.
FDIC insurance is simpler through a bank. Non-banks provide it through pass-through arrangements with partner banks, but the coverage is indirect, and the Synapse collapse in 2024 showed what happens when the middleware layer between a fintech and its partner bank breaks down. Thousands of customers lost access to their funds for months.
The convergence signal
Capital One acquired Brex for $5.15 billion. That transaction is the clearest signal of where business banking is headed.
Capital One already ranked highest in J.D. Power's small business banking satisfaction study for three consecutive years. With service already strong, Capital One was buying the engineering layer it couldn't build fast enough internally, from automated onboarding and API-first card infrastructure to real-time spend management and a customer base of about 35,000 businesses that chose Brex over a bank.
The market is splitting. Routine business banking, accounts, cards, payments, expense management, is moving to non-bank platforms that compete on engineering speed. Complex financial services, lending, treasury, advisory, stay with banks that compete on capital and regulatory infrastructure. The interesting question is how fast the two sides converge, and Capital One just showed one way to answer it.
Sources
- J.D. Power 2026 U.S. Small Business Banking Satisfaction Study - overall satisfaction rose to 726 on a 1,000-point scale, fifth consecutive annual increase
- Capital One Completes Acquisition of Brex - $5.15 billion cash-and-stock acquisition of Brex corporate card and spend management platform
- Mercury Series D at $5.2 Billion Valuation - $200 million funding round, over 300,000 clients
- Ramp Revenue and Growth - approximately $1.5 billion in annualized revenue, $55 billion+ in annual payment volume
- Kansas City Fed: Community Bank Small Business Lending - community bank share of small business loans fell from 24% to 12% as of Q2 2024
Frequently Asked Questions
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.