SynapseFI Review

SynapseFI, formally Synapse Financial Technologies, Inc., is no longer an operating company. It filed for Chapter 11 bankruptcy on April 22, 2024, and its collapse triggered one of the most consequential consumer financial harm events in modern fintech history. More than 100,000 end users lost access to over 265 million dollars in funds held across the platform’s banking partner network. Lets read more about SynapseFI Review.

A shortfall of between 46 and 96 million dollars existed between what Synapse’s records showed end users were owed and what the partner banks actually held. As of the CFPB’s September 2025 enforcement action and the agency’s December 2025 allocation of 46 million dollars toward restitution, many affected consumers had still not recovered their full balances more than a year after the bankruptcy.

Company Background and Market Position | SynapseFI Review

Synapse Financial Technologies was founded on April 14, 2014, by Sankaet Pathak, then in his mid-twenties, in San Francisco. Pathak had previously co-founded Zen Payroll, which later became Gusto, though he departed before the company achieved its most significant growth. His founding premise for Synapse was straightforward and, at the time, genuinely compelling: the infrastructure required to launch banking and financial products was prohibitively expensive and technically complex for the wave of fintech startups that wanted to offer deposit accounts, debit cards, and payment services to their customers. By building a centralized platform that handled the compliance, bank partnerships, and technical integrations, Synapse could allow fintech companies to launch banking products in weeks rather than years.

The company built a substantial operation on this premise. By the end of 2022, Synapse had reached 18 million end users, completed 91 million annualized transactions, processed 76 billion dollars in annualized transaction volume, and achieved cash-flow positive status. It was ranked among the top 100 financial services companies on the Inc. 5000 fastest-growing private companies list. It had contracts with approximately 20 banking partners and served roughly 100 fintech companies whose own customers ultimately relied on Synapse’s infrastructure for their banking services. Companies including Yotta, Juno, Copper, Dave, and Relay used Synapse’s platform to power their consumer and business banking products.

The company raised funding from investors including Trinity Ventures and Andreessen Horowitz. Its valuation reached unicorn status, above one billion dollars, at some point before the bankruptcy, reflecting the market’s significant confidence in both the BaaS model and Synapse’s execution of it.

The Banking as a Service Model Synapse Built

Understanding what Synapse actually did requires a clear explanation of the banking-as-a-service model it operated within, because the architecture of that model is both what made Synapse valuable as an infrastructure provider and what created the conditions for catastrophic failure.

A banking-as-a-service company like Synapse operates as a technology and ledger intermediary. Fintech companies, the companies actually facing consumers, do not hold banking licenses. They cannot legally hold deposits. To offer their customers what looked and functioned like a bank account, they partnered with FDIC-insured banks. But connecting directly with a bank requires significant compliance infrastructure, regulatory work, and technical integration that most small fintech companies could not afford or manage independently.

Synapse was at the heart of all of this. Fintech companies were connected with the technology of Synapse through its APIs that allowed for the creation and management of customer accounts, issuance of debit cards, payments processing, and Know Your Customer and compliance. On the other hand, Synapse was connected with partner banks including Evolve Bank & Trust, American Bank, Lineage Bank, and AMG National Trust Bank. Funds of customers were stored in FBO accounts, which referred to one bank account where the money of thousands of individuals could be stored. Synapse kept track of which individual owned how much from the total sum of the bank account balance.

All of this implied that the safety of customers’ funds was ensured by the following three factors; insurance of partner banks by the FDIC, solvency of partner banks, and accurate records on the ledger of Synapse. Both of the first two were true. Not so with the latter.

Core Products and Services During Operation

During its operational years, Synapse offered fintech companies a suite of products that covered the core infrastructure components of a banking product. Deposit account management through the FBO account structure allowed fintech companies to offer their customers accounts that held real money at real FDIC-insured banks, accessible through the fintech’s own app interface. End users deposited money into accounts that technically existed at the partner bank, with Synapse maintaining the per-user balance record in its own ledger system.

Debit card issuance was handled through Synapse’s card program management capability, connecting partner banks and card networks to allow fintech companies to issue branded debit cards to their customers without managing card network relationships independently. Card transaction processing ran through the Synapse infrastructure, with transaction records flowing into the ledger system alongside deposit balances.

Payment processing covered ACH transfers, which enabled direct deposit, bill payment, and peer-to-peer money movement through the accounts. This payment infrastructure was the functional backbone of the banking experience that fintech companies built on top of Synapse, and its reliability during the operating years was a genuine strength of the platform.

KYC and compliance services handled customer identity verification, Bank Secrecy Act compliance, and anti-money laundering screening on behalf of fintech companies and their partner banks. This compliance infrastructure was one of the most significant barriers to entry that Synapse removed for fintech operators, allowing companies to launch regulated financial products without building their own compliance teams from scratch.

The Modular Banking product, launched in 2022, and the Global Cash product introduced in the same year reflected Synapse’s ambition to extend beyond its core US deposit and card infrastructure toward a more comprehensive global financial services platform. These products were still developing when the company’s financial and operational difficulties escalated.

The Relationship with Evolve Bank and the Growing Dispute

The relationship between Synapse and Evolve Bank and Trust is the central operational context for understanding the collapse, and it deserves careful examination because the dispute between the two companies directly produced the conditions that froze customer funds.

Evolve Bank and Trust was Synapse’s largest banking partner and the bank that held the most significant portion of Synapse’s end-user funds. The relationship was commercially central to Synapse’s business model: Evolve provided the FDIC-insured banking infrastructure behind a substantial share of the fintech products Synapse enabled.

In late 2023, the relationship began deteriorating. Evolve demanded that Synapse maintain a reserve of approximately 50 million dollars as a condition of continuing the partnership. Synapse, whose financial position was weakening following Mercury’s departure from the platform, could not satisfy this demand. The dispute over reserve requirements and the settlement of end-user balances between the two organizations created a growing discrepancy between Synapse’s internal ledger records and Evolve’s records of what the bank held on behalf of Synapse’s end users.

Mercury, one of Synapse’s largest and highest-profile fintech clients, migrated off the Synapse platform in late 2023. The loss of Mercury’s transaction volume, and the settlement of Mercury’s customer balances as part of that migration, is a disputed but significant element in the balance sheet of what went wrong. Pathak has alleged that Mercury’s migration created approximately 92 million dollars in shortfall in funds held at Evolve. Evolve and others dispute this characterization.

As the dispute escalated and Synapse’s financial position deteriorated, the company began discussions with TabaPay about an acquisition that would have used TabaPay’s resources to resolve the balance discrepancy and continue operations. Synapse filed for Chapter 11 bankruptcy on April 22, 2024, with the TabaPay acquisition intended to proceed through the bankruptcy process.

The Bankruptcy, the TabaPay Failure, and the Account Freeze

The sequence of events following the bankruptcy filing moved quickly and disastrously. The TabaPay acquisition was the last viable path to a resolution that would have preserved customer access to their funds, and its collapse destroyed that path.

TabaPay’s acquisition of Synapse required a closing condition: Evolve Bank needed to fully fund the FBO accounts to cover the balance discrepancy before the deal could close. Evolve refused to do so, disputing both the existence of its obligation and the accuracy of Synapse’s records about the shortfall amount. TabaPay withdrew from the acquisition on May 8, 2024, citing the failure to meet the closing conditions.

Three days after TabaPay’s withdrawal, on May 11, 2024, a crisis point was reached. Synapse cut Evolve’s access to the dashboard system that Evolve used to maintain customer accounts, an action that Synapse characterized as a response to non-payment but that Evolve characterized as a sudden system shutdown without notice. Evolve froze the funds it held in response, citing inability to verify transactions and confirm end-user balances without access to Synapse’s systems.

The impact on users was instant and drastic, as those who were storing their money using Synapse’s technology stack, from Yotta to Juno to Copper, and other platforms, logged into their applications in the morning only to see their accounts frozen. Direct deposits could not be made. Scheduled payments did not go through. Funds to cover rental payments, emergencies, and business operations were held within an account that neither the company nor anyone else was able to access because the ledger system that showed who had ownership of which portion of the aggregated funds was down or wrong.

These were people describing actual difficulties in life on public forums and bankruptcy filings. One user stated how they had been forced to borrow money to pay for rent and relocation services while they could not access their own money. Another mentioned having over twenty thousand dollars in a Yotta account, and unable to access those funds.

The Ledger Discrepancy: What Went Wrong Technically

The specific technical failure at the heart of the Synapse collapse was the inaccuracy of its ledger records, which the CFPB’s August 2025 enforcement action specifically cited as a violation of consumer protection laws.

In the FBO account structure, all end-user funds at a given bank are held in a single pooled account. The only way to determine how much of that pooled balance belongs to any specific end user is through the intermediary’s internal ledger. Synapse’s ledger was the definitive record of individual balances across its network of partner banks. When the ledger was accurate and the pooled bank balances matched the sum of individual ledger entries, the system worked. When they diverged, there was no simple way to determine which end users were owed what, because the bank’s records only showed the aggregate pooled balance, not individual ownership.

The complaint made by the CFPB, filed on August 21, 2025, and entered by the court on September 12, 2025, stated that Synapse violated the Consumer Financial Protection Act of 2010 by failing to keep proper record-keeping of the location of the consumers’ funds. This enforcement action showed that the issue of poor record-keeping was not due to the final dispute with Evolve; instead, it was Synapse’s ongoing inability to manage its ledger infrastructures according to the true locations of its funds in the partner banks.

According to the bankruptcy trustee who used to be the FDIC chair, Jelena McWilliams, there was an estimated gap between Synapse’s record-keeping and what was being kept by the partner banks of 65 to 96 million dollars during different times of the process. It was documented in court files that the total amount the end-users needed for reimbursement was around 265 million dollars, and the partners were holding about 219 million dollars. Hence, the gap was around 46 million dollars, which was allocated to restitution in December 2025.

The Regulatory and Legal Aftermath

The Synapse collapse generated regulatory and legal activity across multiple fronts that continued through 2025 and into 2026, and understanding this aftermath is essential context for evaluating the broader BaaS risk landscape.

The CFPB’s enforcement action against Synapse was filed on August 21, 2025, and entered by the bankruptcy court on September 12, 2025. The action alleged that Synapse violated the Consumer Financial Protection Act by failing to maintain adequate records of consumer fund locations and failing to adequately oversee the banking partners and fintech companies in its network. The consent order required the allocation of available funds toward restitution for affected consumers.

Yotta, whose customers had initially lost access to over 100 million dollars in funds, filed a lawsuit against Evolve Bank in September 2024, alleging grotesque misconduct, fraud, and negligence. Yotta’s lawyers described Evolve as having a rotten core, reflecting the deep attribution of blame that the fintech directed at the bank partner rather than accepting shared responsibility for the infrastructure failures.

The Federal Reserve, which supervises Evolve as a state-chartered member bank, issued enforcement actions against Evolve related to its BaaS activities. These enforcement actions addressed Evolve’s oversight of its fintech partners and its internal controls around the FBO account structure, confirming that the bank’s conduct in managing its Synapse relationship was not consistent with sound banking practices.

Evolve maintained throughout the proceedings that Synapse’s own recordkeeping failures, not Evolve’s conduct, were the primary cause of the consumer harm. The assignment of blame between Synapse and Evolve remained contested as of early 2026, with active litigation between various parties including Yotta’s lawsuit against Evolve continuing in the courts.

The Industry Impact and Regulatory Response

The Synapse collapse had consequences that extended well beyond the specific companies and end users directly affected, reshaping how regulators, banks, and fintech operators think about the BaaS infrastructure model.

Federal banking regulators issued joint guidance on BaaS arrangements in mid-2024, clarifying supervisory expectations for banks that partner with fintech companies. The guidance emphasized that banks retain full responsibility for compliance with banking laws and regulations regardless of what technology intermediaries do on their behalf, and that the delegation of compliance functions to BaaS providers does not reduce the bank’s regulatory accountability. This guidance effectively raised the bar for bank oversight of BaaS relationships, with direct implications for how BaaS providers structure their operations.

As per the analysis in the Yale Journal of International Affairs published in January 2026, the Synapse collapse proved that there is a requirement for mandatory disclosures during account opening that explain clearly the custodial structure, scope of deposit insurance, involvement of middleware firms, and degree of regulation. According to this analysis, any financial product marketing itself with the promise of safety provided by the bank must be providing safety in the same way as that provided by a bank.

In the case of the BaaS industry specifically, the Synapse collapse led to the phase of consolidation. Many BaaS players had grown rapidly due to their business models being solid as the deposits with their partners were FDIC insured. After the Synapse collapse incident, there were doubts regarding the assumption of FDIC insurance covering the failure of the intermediary firm. It became evident that FDIC insurance covers failure of banks but not of intermediaries who maintain record of shares of pooled bank accounts.