For more than a decade, the fintech sector has operated on a structural contradiction: API-first companies delivering seamless digital experiences to millions of users, while quietly depending on aging core banking systems stitched together through layers of middleware that were never designed for the demands of modern financial engineering. That compromise, tolerated for years, is now being directly challenged. San Francisco-based Increase has officially completed the acquisition of Washington State-based Twin City Bank, securing a full commercial banking charter and becoming one of the rare financial technology infrastructure providers in the United States to own its entire stack — from the API layer down to the regulated bank itself.
The move follows an initial voting share acquisition that Increase had executed the prior year, with founder and chief executive Darragh Buckley formally completing the takeover of Twin City Bank in the latest transaction. Buckley, an early alumnus of Stripe, established Increase in 2020 with an explicit mandate to rebuild financial infrastructure from the ground up — not merely wrap legacy systems in modern interfaces. The company has since grown into the backbone of some of the most prominent platforms in fintech, including Ramp and Stripe itself, collectively facilitating the movement, storage, and lending of hundreds of billions of dollars across the financial system.
Why the Charter Changes Everything
The significance of holding a banking charter cannot be overstated for a company operating at Increase's scale and architectural depth. Traditional fintech infrastructure providers operate through what the industry calls a partner bank model: a fintech firm connects its technology to a licensed bank's core system via middleware or application programming interface wrappers, enabling it to offer banking-like services without a charter of its own. This arrangement is functional, but structurally fragile. Asynchronous processing between API layers and legacy core banking software generates balance discrepancies, reconciliation errors, and delayed ledger clearing. More critically, the multi-vendor architecture widens the attack surface for data breaches, application programming interface abuse, and credential stuffing. And when compliance reporting is required, the chain of regulatory responsibility is fragmented across each layer of the stack.
By absorbing Twin City Bank entirely, Increase eliminates that chain. Developer teams using Increase's infrastructure now interact directly with primary payment rails — including the FedNow instant payment network, Automated Clearing House transfers, real-time gross settlement systems, and wire transfer networks — through low-latency native application programming interfaces, without any intermediary translation layer in between. The ledger becomes a single source of truth, updated in real time rather than reconciled in batch cycles. Third-party risk management, a laborious process that typically requires separate vendor assessments for every banking partner and middleware provider in a payment flow, collapses into a single audit boundary under consolidated regulatory oversight of the Office of the Comptroller of the Currency and the Federal Deposit Insurance Corporation.
The Security and Compliance Architecture Shift
From a security architecture standpoint, the implications of Increase's model are equally substantial. Legacy core banking software typically relies on batch processing for fraud detection and Anti-Money Laundering compliance monitoring, meaning suspicious activity may only be flagged after a transaction has settled. An infrastructure-first chartered bank can deploy real-time threat mitigation directly at the application programming interface layer, intercepting automated payload tampering, anomalous transaction patterns, or identity abuse before settlement is finalised. For security officers and compliance leads at scaling financial firms, this represents a fundamental upgrade in operational resilience — one that reactive, batch-oriented middleware architectures structurally cannot match.
Buckley's decision to pursue this path traces directly to his time at Stripe, where the gap between the speed of software development and the rigidity of the banking systems underneath it was a persistent operational constraint. The insight that the only true resolution was vertical integration — owning the charter alongside the code — underpins everything Increase has built since its founding. In that sense, the Twin City Bank acquisition is less a pivot than the logical culmination of a six-year engineering thesis playing out at institutional scale.
A Precedent for the Infrastructure Layer
Increase is not the first fintech to seek a banking charter, but the context of this acquisition is distinct. Most charter-seeking fintechs have been consumer-facing companies seeking to eliminate their dependency on sponsor banks and capture greater margin. Increase is an infrastructure provider — a company whose customers are themselves sophisticated financial technology platforms. Its charter acquisition therefore sets a precedent at a deeper layer of the ecosystem, one that could reshape how developer-facing banking infrastructure is built, regulated, and audited across the United States and, by extension, how comparable models are evaluated under Financial Conduct Authority frameworks in the United Kingdom.
As financial regulators on both sides of the Atlantic continue to scrutinise the concentration of systemic risk in middleware-dependent fintech architectures, the vertically integrated chartered model that Increase now embodies offers a structurally cleaner answer to questions of accountability. When a single entity owns the infrastructure, the charter, and the compliance perimeter, there is no ambiguity about where regulatory responsibility begins and ends. That clarity, in an era of increasingly aggressive supervisory expectations, may prove to be the most durable competitive advantage Increase has built.
For infrastructure architects, security professionals, and compliance leads at financial firms building on partner bank rails, the message from San Francisco is unambiguous: the middleware era of fintech infrastructure is entering its final chapter, and the institutions that control their full stack will set the standards for the next generation of financial architecture.
Written by the editorial team — independent journalism powered by Codego Press.