777 Partners' $500 Million Fraud Plea: The Collateral Control Failure Lenders Cannot Excuse

TL;DR

• Joshua Wander, co-founder and former CEO of 777 Partners, pleaded guilty to wire fraud and securities fraud in a scheme the Justice Department says took more than $500 million from lenders and investors.
• The control failure was brutally concrete: assets were pledged that 777 Partners did not own or had already pledged elsewhere, restricted lender funds were diverted, and bank statements were digitally altered.
• A borrowing-base certificate is not collateral evidence. Private-credit lenders need asset-level uniqueness checks, controlled cash, independent confirmation, lien verification, and exception escalation.
• Start with the facilities where collateral reporting is borrower-generated, substitutions are frequent, and the same management team controls cash, records, and lender reporting.

A lender challenged 777 Partners about double-pledged assets. Joshua Wander blamed an “antiquated computer system.”

That explanation should now sit in every credit-risk training deck under stop the draw and investigate.

On October 15, 2026, Wander, the co-founder and former CEO of Miami investment firm 777 Partners, pleaded guilty to wire fraud and securities fraud. The Justice Department says he orchestrated a multi-year scheme that defrauded lenders and investors of more than $500 million. As part of the plea, Wander agreed to forfeit at least $500 million in proceeds. Sentencing is scheduled for March 1, 2027.

The 777 Partners fraud plea matters beyond one private investment firm or its headline-grabbing soccer portfolio. It exposes a basic weakness in asset-based and private-credit lending: the lender can have covenants, certificates, and polished financial packages while still lacking reliable proof that the collateral exists, belongs to the borrower, remains unencumbered, and supports the reported borrowing base.

What Happened in the 777 Partners Fraud Scheme?

777 Partners originally financed purchases of structured settlements. Those arrangements provide personal-injury victims or other beneficiaries with periodic payments rather than one lump sum. The firm bought rights to future payments, financed those purchases through private credit facilities, and pledged the payment rights and cash as collateral.

According to the FBI’s October 2025 charging summary, the business grew into one of the largest buyers in the secondary structured-settlement market. The trouble came when 777 Partners expanded into businesses with less predictable cash flows, including airlines, streaming platforms, and professional soccer clubs.

Prosecutors said Wander directed restricted lender funds into acquisitions and expenses despite warnings from employees and restrictions in the credit agreements. That created cash and collateral shortfalls. The firm then maintained access to financing through false collateral and false financial information.

The mechanics were not sophisticated:

The October 2025 indictment alleged that more than $350 million in assets were pledged even though 777 Partners did not own them or had pledged them elsewhere. That figure was an allegation at charging. The current procedural fact is stronger and narrower: Wander has now admitted guilt to wire and securities fraud, and DOJ says the overall scheme exceeded $500 million.

The distinction matters. Compliance teams should not repeat every indictment allegation as an admitted fact. They can, however, use the government’s account to test whether their controls would detect the same mechanics.

The SEC Case Shows a Second Reporting Perimeter

The criminal case focused heavily on lenders, collateral, and restricted funds. A parallel SEC action shows how the same liquidity problem reached equity investors.

In Litigation Release No. 26419, the SEC alleged that Wander, co-founder Steven Pasko, former CFO Damien Alfalla, 777 Partners LLC, and 600 Partners LLC defrauded investors in an approximately $237 million preferred-equity offering. The SEC complaint says investors were told the companies had or would generate enough net income to support a 10% annual dividend while the businesses were in a severe liquidity crisis.

The SEC also alleged a $300 million credit-facility overdraw and approximately $33 million in investor funds diverted to Wander and Pasko personally. Those civil claims remain allegations unless resolved or proven in court. They are still relevant to control design because they show two audiences receiving information from the same impaired financial-reporting environment:

1. Lenders needed accurate collateral, cash, covenant, and use-of-proceeds data.
2. Preferred-equity investors needed accurate earnings, liquidity, dividend-coverage, and proceeds-use information.

A firm should not run those reporting streams as separate compliance exercises. The CFO, Controller, Treasurer, General Counsel, and Chief Risk Officer need one reconciled view of unrestricted cash, restricted cash, pledged assets, liens, facility availability, investor obligations, and related-party payments.

That is the same concentration-risk problem addressed in the site’s guide to bank exposure to private credit and nonbank financial institutions: opaque nonbank reporting becomes the regulated lender’s credit and operational risk.

Why Borrowing-Base Certificates Fail

A borrowing-base certificate is a management representation. It is useful, but it is not independent evidence.

The weak operating model looks like this: the borrower exports an asset list, applies eligibility rules, signs a certificate, and sends it to the lender. The lender verifies the arithmetic and approves the draw. If the source list contains an asset that was never purchased, was sold, was paid off, or was pledged to another lender, perfect spreadsheet math only produces a precisely wrong answer.

For structured-settlement receivables, the lender should be able to connect each pledged asset through the full evidence chain:

beneficiary and obligor → purchase agreement → court approval where required → payment right → unique asset identifier → custody or control record → lien status → expected payment schedule → actual cash receipt → facility allocation

Break one link and the collateral needs an exception status—not a quiet manual adjustment.

This is where ownership gets messy. Credit says Operations owns the collateral tape. Operations says Legal owns perfection. Legal says the borrower certified the schedule. Internal Audit tests whether the certificate was received on time. Everyone completed a task; nobody proved the asset was uniquely and validly pledged.

The control owner should be the Credit Risk function, because collateral eligibility is a credit decision. Loan Operations should execute reconciliations and custody checks. Legal should validate liens, perfection, and contractual rights. Internal Audit should independently test whether those controls work. The relationship manager cannot be the final exception approver when a draw or fee depends on keeping the facility moving.

Six Controls That Would Challenge Double-Pledged Assets

1. Build an asset-level collateral registry

Assign or capture a persistent identifier for every receivable, settlement stream, security, or contract right. Include originator, obligor, acquisition date, purchase price, expected cash flow, ownership entity, custodian, facility assignment, lien status, and disposition date.

Then test for duplicate identifiers across every facility and affiliate. Fuzzy matching is necessary when borrowers change punctuation, abbreviate names, or reformat contract numbers. An exact-match spreadsheet check is too easy to defeat accidentally or deliberately.

2. Confirm ownership outside the borrower package

Select a risk-based sample and obtain evidence from the obligor, custodian, settlement administrator, bank, or other independent party. Trace acquisition consideration from the controlled bank account to the seller. A purchase agreement without proof of funding does not establish that the borrower completed the acquisition.

This is the collateral equivalent of the independent-custody controls discussed in the Astor stock-loan fraud breakdown. Branding, contracts, and management attestations do not replace control over the asset.

3. Verify liens and competing claims

Run UCC and other applicable lien searches at onboarding, before material increases, and on a defined refresh cycle. Require disclosure of every financing arrangement that could touch the collateral pool. Reconcile the disclosure to debt footnotes, cash movements, board materials, and external legal invoices.

A clean UCC search alone is not enough. Contractual assignments, offshore entities, custodial arrangements, or recently created liens may not be visible through one search method. Legal should document the search perimeter and residual risk.

4. Control restricted cash at the bank

Use lender-controlled collection accounts where the structure permits. Configure payments so collateral cash enters an account the borrower cannot freely redirect. Reconcile expected payments to bank transactions and the asset ledger, with unresolved shortages aging visibly.

Most importantly, obtain balances and transactions through direct bank access or bank-delivered data. A PDF uploaded by management is not a cash control. The 777 Partners case includes digitally altered bank statements precisely because static documents were capable of carrying the lie.

5. Treat collateral substitutions as new underwriting events

A substitution should require evidence of ownership, eligibility, value, lien status, and release of the outgoing asset. Log who requested it, who approved it, and why. High substitution volume, repeated last-day requests, and assets moving among affiliates should trigger enhanced review.

Starter trigger: review a facility when monthly substitutions exceed its trailing six-month internal range or when the same asset identifier appears in more than one submitted schedule. Calibrate the threshold to the portfolio; preserve the duplicate test as a zero-tolerance exception.

6. Link exceptions to draw authority

Define which exceptions stop funding. Missing independent confirmation, duplicate collateral, unexplained restricted-cash transfers, or unverifiable bank balances should prevent a draw unless a named senior credit officer approves a documented, time-limited exception.

Track the exception as an issue with root cause, owner, due date, interim control, and independent closure evidence. An email saying “system issue—will fix next month” is not remediation.

A 30/60/90-Day Review for Credit and Compliance Teams

First 30 days: find the blind spots

Owners: Chief Credit Officer, Head of Loan Operations, General Counsel.

• Inventory facilities dependent on borrower-generated collateral schedules.
• Identify which accounts are lender-controlled and which balances arrive only by statement or screenshot.
• Map collateral identifiers across affiliates and facilities.
• Pull all unresolved borrowing-base, covenant, cash, and collateral exceptions.
• Freeze automatic increases where ownership or lien evidence is incomplete.

Evidence for the Credit Committee: facility inventory, control-perimeter map, exception register, and a list of draws approved despite unresolved exceptions.

By day 60: test the assets and cash

Owners: Credit Risk Testing, Loan Operations, Finance.

• Select higher-risk facilities using leverage, reporting delays, substitution frequency, exceptions, and management concentration.
• Reperform borrowing-base calculations from source records.
• Independently confirm a sample of assets and bank balances.
• Search for duplicate asset identifiers and competing liens.
• Reconcile expected collateral cash to receipts and investigate breaks.

Do not report only a pass rate. Classify failures: nonexistent asset, duplicate pledge, stale valuation, missing ownership evidence, cash diversion, unperfected lien, or reporting error. Those causes require different remediation.

By day 90: harden the operating model

Owners: Chief Risk Officer, Chief Credit Officer, Internal Audit.

• Move material collection accounts toward lender control where contracts allow.
• Add funding-stop rules to the credit policy.
• Require independent evidence for collateral substitutions and material draws.
• Establish dashboard reporting for duplicate assets, unmatched cash, stale confirmations, overdue exceptions, and reopened issues.
• Have Internal Audit validate the fixes without relying on the team that designed them.

The first committee question should be simple: Can we prove that every material pledged asset exists, belongs to the borrower, remains eligible, and is pledged to us only as represented? If the answer is “the borrower certifies it,” the review is not done.

The Practitioner Takeaway

The 777 Partners fraud plea is not a story about a clever model defeating a lender. It is a story about basic evidence being weaker than the confidence placed in it.

Assets lacked reliable uniqueness. Restricted money left its intended perimeter. Static bank statements stood in for direct cash verification. Management controlled the records used to reassure the same lenders whose funds kept the business alive.

Credit Risk should take the collateral register to the next committee meeting—not another policy rewrite. Pick the five facilities with the most borrower-generated data, the most substitutions, or the most unresolved exceptions. Verify assets and cash outside the borrower package. Anything that does not reconcile becomes a tracked issue with a funding consequence.

If that review surfaces exceptions that need owners, deadlines, interim controls, and independent closure evidence, the Issues Management Tracker & Template is built for exactly that remediation work.