In a move that redraws the architectural boundaries of financial infrastructure, San Francisco-based Increase has completed its acquisition of Washington State-chartered Twin City Bank, officially transitioning from a pure infrastructure provider into a fully regulated, chartered banking entity. The deal, which followed an initial voting share acquisition the prior year, represents one of the more structurally consequential consolidations in recent fintech memory — and a direct challenge to the middleware-dependent model that has quietly underpinned American financial technology for the better part of a decade.
Founded in 2020 by Darragh Buckley, an early alumnus of Stripe, Increase was built from the outset with a single purpose: to give developers native, programmatic access to banking rails without the friction of legacy intermediary systems. The company has already demonstrated it can operate at genuine financial scale — its infrastructure has moved, stored, and lent hundreds of billions of dollars across client platforms including Ramp and Stripe itself. The Twin City acquisition is the logical endpoint of that trajectory, collapsing the distance between the software layer and the regulated banking layer into a single, unified entity.
The Middleware Problem Buckley Was Born to Solve
Buckley's conviction about vertical integration traces directly to his Stripe years, where he encountered firsthand the growing mismatch between the velocity of software development and the rigidity of legacy banking cores. The conventional fintech architecture — a modern application programming interface (API) wrapper draped over an antiquated core banking system, connected to a partner bank through yet another layer of middleware — introduces compounding vulnerabilities at every junction. Asynchronous processing between API layers and legacy cores creates balance discrepancies and reconciliation lags. Every additional third-party intermediary widens the attack surface for data breaches and API abuse. And fragmented compliance responsibilities across multiple vendors complicate audit trails, anti-money laundering (AML) monitoring, and real-time fraud detection under frameworks such as those administered by the Office of the Comptroller of the Currency (OCC), the Federal Deposit Insurance Corporation (FDIC), and the Financial Conduct Authority (FCA) in the United Kingdom.
By owning both the banking charter and the underlying infrastructure software, Increase eliminates the need for middleware translation entirely. Developer teams gain direct access to primary payment rails — including real-time gross settlement (RTGS) networks, the FedNow instant payments service, Automated Clearing House (ACH), and wire transfers — through low-latency, native APIs. The ledger becomes a single source of truth, updated in real time rather than through batch processing cycles that introduce windows of systemic uncertainty.
Why Vertical Integration Changes the Risk Calculus
From a third-party risk management (TPRM) perspective, the implications are substantial. Financial firms operating under conventional middleware architectures must conduct layered vendor risk assessments covering every banking partner, middleware provider, and API intermediary in their transaction flow. Each assessment carries compliance overhead, audit complexity, and potential for gaps between what one vendor certifies and what the next actually delivers. Collapsing the entire stack — charter, core infrastructure, and API layer — under a single legal and regulatory entity consolidates that risk surface dramatically. A single audit boundary replaces a fragmented chain of shared responsibility.
The security architecture benefits are equally meaningful. Legacy core banking systems were designed for batch-processed fraud detection, which means suspicious transactions may only be flagged after a settlement cycle has completed. An infrastructure-first chartered bank, by contrast, can deploy inline threat monitoring directly at the API layer — catching anomalies such as automated payload tampering, credential stuffing, and unusual transaction patterns before they ever reach settlement. For platforms processing payments at the scale that Ramp and Stripe operate, even fractional improvements in detection speed translate into material reductions in fraud exposure.
A Precedent With Ecosystem-Wide Consequences
Increase is not the first fintech to recognise that charter ownership confers structural advantages, but its execution is notable for the deliberateness of its approach. Rather than acquiring a large regional bank and inheriting its legacy technology debt, Buckley targeted a Washington State institution — Twin City Bank — whose modest scale allowed for a clean architectural integration. The initial voting share acquisition completed the prior year indicates that regulatory approvals and operational due diligence were conducted with unusual patience and precision, rather than the sprint-to-close urgency that has characterized some earlier fintech-bank deals.
The broader industry signal is difficult to ignore. As fintech platforms mature and transaction volumes grow, the operational and regulatory costs of middleware dependency accumulate. Increase's move sets a clear precedent for infrastructure providers willing to absorb the regulatory burden of charter ownership in exchange for full-stack control. Competitors and partners alike will now have to evaluate their own architectural positions in light of a company that has effectively become its own bank — and built the software to prove it can run one at scale.
What This Means for the Market
For compliance officers, infrastructure architects, and engineering leads at scaling financial firms — whether operating under US federal frameworks or adapting to UK FCA expectations — the Increase model presents both a benchmark and a competitive pressure point. The days of accepting latency, reconciliation risk, and fragmented audit responsibility as unavoidable features of fintech architecture are increasingly difficult to justify when a direct competitor has structurally eliminated them. Bringing banking charters under the same organizational roof as high-throughput engineering infrastructure is no longer a theoretical aspiration; Increase has made it operational reality. The next wave of financial infrastructure consolidation may well be shaped by who follows.
Written by the editorial team — independent journalism powered by Codego Press.
