Why Stripe’s 1st Employee Bought a Bank | Darragh Buckley, Increase
Darragh Buckley argues banking fintech should stop stacking abstraction layers and instead go down a level, owning the bank and exposing raw Federal Reserve capabilities by API, built simply, safely and with an empowered team.
Watch on YouTube ↗Charlie's summary
- ▶ 1:29
Building on someone else's bank is the princess-and-the-pea problem: you always feel the stone in your shoe
Darragh says Stripe's partner banks made it feel “out of place.” Stripe never paid merchants by bank transfer because a failed transfer meant a manual email from the bank. Dozens dealt with ACH returns because the trace ID was not passed on correctly. Products are built for their intended users, and Stripe wasn't the target. Companies must then build large manual teams or skip the product.
- ▶ 7:59
Modern banking APIs look like payments in 2010, so Increase verticalizes: replace the core and the API together
Before Stripe, you needed a merchant account plus a gateway like authorize.net. Stripe's insight was that they are one thing. Darragh sees today's fintech layers on top of bank cores, essentially ledgers of balances and transactions, as the same pattern. He thinks the answer is to go down a level, not keep adding layers.
- ▶ 16:32
Buying a bank is its own culture: banks can't announce a sale, and Darragh was told to join a board first
Banks can't say they're for sale because their loan staff would leave, so the industry holds a conference called “Buy or Be Bought” where everyone claims to be buying. Control thresholds of about 10% and 25% require regulatory permission. After a 2023 attempt on Washington Business Bank, Darragh was asked to sit on its board, then bought Twin City Bank, now Increase Bank.
- ▶ 25:10
You can't just screw an API onto a bank: build compliance as code and run audits on yourself constantly
Darragh wants compliance rules, like the travel rule at $3,000, built into transfer processing from the start. He wants the audit “sigh of relief” close to zero. Just as engineers write tests and deploy dozens of times a day, run your compliance checks several times a day. That needs engineers reading regulations and compliance staff reading engineering details.
Give your email to unlock the rest of the key points — for every episode.
Do more with Charlie
Free — sign in with your email, no password.