Flex's Dependence on Banking Rails

This risk is really about Flex renting critical banking rails instead of owning them. Flex can design the app, underwrite the customer, and market the card, but deposits and card issuance still depend on outside banks and middleware style coordination. Synapse showed that when the infrastructure layer breaks, customers can lose access to funds for months, and the fintech above it can keep the brand damage while losing product uptime and margin control.

• Flex runs business banking through Thread Bank and cards through Lead Bank, which means two core products depend on partner institutions whose economics, compliance standards, and service continuity Flex does not fully control.
  1 sacra 2 sacra
• The Synapse collapse is the concrete template for this risk. In 2024, tens of thousands of users were locked out, roughly $200M was frozen, and the trustee reported a large gap between customer balances and funds held at partner banks.
  3 cnbc 4 bloomberglaw 5 apnews
• Mercury shows the strategic response. After disruptions tied to Evolve and the post Synapse BaaS crackdown, it moved customers toward Column and Choice and applied for a national bank charter, aiming to remove a layer of dependency that still sits inside Flex's model.
  6 sacra 7 bankingdive 8 sacra

The next phase of fintech infrastructure will favor companies that either own more of the regulated stack or concentrate on a smaller set of deeply integrated bank partners. For Flex, that means product expansion will increasingly depend not just on customer demand, but on how much control it can gain over banking rails, compliance processes, and unit economics.