Stripe's First Employee Built a Bank to Fix Payments' Messy Last Mile

Stripe's First Employee Built a Bank to Fix Payments' Messy Last Mile

Darragh Buckley went from Stripe’s first employee to bank owner with a contrarian bet: The biggest opportunity in payments sits inside regulated banking, not outside it. Increase Bank isn’t trying to rip out America’s payment rails. It’s built to fix the stubborn last mile between modern software companies and the bank infrastructure moving trillions of dollars. Buckley said richer data, continuous visibility and compliance designed into the software can reshape payroll, embedded finance and the meaning of community banking.

An engineer sits across the table from a bank examiner. How does that conversation go? Better than you might think, Darragh Buckley would argue. The engineer wants to know what the system is doing at every step. The examiner wants to know it’ll do the right thing every time. Those aren’t competing demands. They’re the blueprint for a better bank. That idea runs against one of FinTech ’s founding stories: Banking ’s future depends on replacing legacy infrastructure. But after helping build Stripe’s earliest banking integrations, Buckley reached a different conclusion. The rails weren’t broken. The trouble was the distance between those rails and the software companies trying to build on top of them. That conviction eventually carried Buckley beyond banking-as-a-service partnerships and all the way into bank ownership. Increase ’s launch of Increase Bank is where that journey landed.

Founder and CEO Buckley told PYMNTS CEO Karen Webster that his time as the first employee of Stripe revealed capabilities banks possessed but rarely exposed in ways modern software companies could actually use. “The systems are good and reliable,” Buckley said. “And they serve very much the use cases that they were built for.” But, he added, “many of our current use cases, especially around ambitious technology companies, run into edge cases that perhaps weren’t contemplated. If you’re rebuilding the technology stack anyway, contemplating those compliance regimes from the start makes it easier to build a safe and sound system.”

Plenty of FinTech executives would happily send ACH and Fedwire to the museum. Buckley won’t. He credited the Federal Reserve with operating dependable systems. “The Federal Reserve is fantastically reliable,” Buckley said. “They changed the messaging format for Fedwire… across 3,500 institutions… and everything succeeded. Everyone got paid. Lights stayed on. Traffic still moved.” His analogy isn’t a blockchain or a rocket ship. It’s public transportation. The tunnels don’t change often. What riders feel are better schedules, easier payments and clearer explanations when something goes wrong. The infrastructure can stay put while the experience gets better. That mindset helps explain why Increase didn’t start by pursuing a banking charter. It first built its own technology stack, connected directly to payment networks, and developed the operations developers need to build financial products. Only after years of working with partner banks, serving on a community bank board, and learning how regulated banking really works did Buckley conclude that the final piece required owning a bank. The strategy grew out of the kind of operational frustration Buckley knew firsthand from Stripe. Take wire transfers. Sending the money usually wasn’t the hard part. ...