How TCPA Lawsuit Growth Reshapes MCA Lead Verification and Compliance for Funders

A 30% Litigation Surge That MCA Funders Cannot Ignore

Through the end of May 2026, TCPA lawsuits were on pace to grow by 30% over 2025 numbers, according to WebRecon's latest tracking data. CFPB complaints were climbing even faster, trending 34.8% higher year over year. The increase is not isolated to one sector. It cuts across industries. But for MCA funders who depend on broker-sourced leads and outbound contact workflows, the risk is acute.

The connection between TCPA exposure and bank verification software for funders is less obvious than it might seem at first glance, which is exactly why so many funders miss it. Most compliance teams treat lead consent and underwriting verification as separate workflows managed by separate people. That separation is a liability. When a merchant disputes that they ever requested funding, the funder's entire file comes under scrutiny: who contacted whom, when, and what evidence exists that the applicant voluntarily participated in the process. A robust, applicant-initiated bank verification recording can be the single strongest piece of evidence that the merchant was an active, willing participant.

This article breaks down how the TCPA litigation wave is reshaping lead-to-funding workflows for MCA funders, why traditional verification methods leave compliance gaps, and how asynchronous bank verification creates the kind of documented consent trail that protects funders on both sides of the equation.

Why TCPA Risk Reaches All the Way Into Underwriting

The Broker-Sourced Lead Liability Chain

Most MCA funders do not originate their own leads. They rely on a network of brokers and ISOs who generate applications through a mix of outbound calls, email campaigns, digital advertising, and referral networks. The funder's exposure begins the moment a broker contacts a merchant, even if the funder has no direct knowledge of how that contact was made.

Under the TCPA, consent requirements are strict. A single unsolicited call or text to a number on the Do Not Call registry, or made without prior express consent, can trigger statutory damages. Serial TCPA litigants have turned this into a business model, filing claims against any company in the contact chain. As we explored in our analysis of how serial TCPA litigants are reshaping MCA lead verification, these plaintiffs specifically target alternative lenders because the broker channel creates so many points of vulnerability.

When a TCPA claim lands, the funder's defense hinges on documentation. Can you prove the merchant consented to be contacted? Can you prove they actively participated in the application process? If your bank verification was a live phone call with no recording, or a PDF bank statement emailed by the broker, your evidence is thin.

The Consent Gap Between Lead Generation and Funding

The fundamental problem is temporal. Lead consent happens at one point in time, often captured by the broker through a web form checkbox or a verbal agreement on a recorded call. Bank verification happens later, during underwriting. Between those two moments, a merchant may change their mind, forget they expressed interest, or be contacted by multiple funders simultaneously. By the time a dispute arises, the original consent record may be ambiguous, missing, or challenged as fabricated.

Traditional bank verification methods do nothing to bridge this gap. A live verification call is synchronous, meaning it requires both parties on the line at the same time, creating scheduling friction that brokers sometimes resolve by cutting corners. A broker might submit bank statements on the merchant's behalf without the merchant's direct involvement. Or a verification call might happen with someone who is not the actual account holder. Each of these scenarios creates a TCPA-adjacent risk: the funder cannot definitively prove that the named applicant willingly participated in the verification process.

CFPB Complaint Amplification

The TCPA surge does not exist in isolation. CFPB complaints trending nearly 35% higher create a parallel pressure vector. The Consumer Financial Protection Bureau publishes complaint data that plaintiffs' attorneys mine for patterns. A funder who appears frequently in CFPB complaint records becomes a target, even if individual complaints are resolved. The combination of rising TCPA suits and rising CFPB complaints creates a compounding reputational and legal risk that demands a systematic response.

How Async Bank Verification Becomes a Compliance Shield

Applicant-Initiated Evidence

Asynchronous bank verification, as implemented by Exact Balance, flips the traditional model. Instead of the funder or broker initiating a call, the applicant receives a secure link and records their own banking session at their convenience. This is a critical distinction from a TCPA compliance perspective. The merchant opens the link voluntarily. They initiate the screen recording. They navigate their own banking portal. Every action is timestamped and stored.

This creates what attorneys call an "affirmative act of participation." The merchant did not merely check a box on a form. They did not passively answer a phone call. They actively logged into their bank account, navigated to the requested screens, and submitted a recording. That level of voluntary engagement is difficult to dispute in litigation.

Audit Trail Depth That Goes Beyond Consent Forms

Exact Balance's activity tracking captures the full lifecycle of each verification request: when the email was sent, when the link was opened, when the recording started, and when the submission was completed. This granular audit trail provides multiple independent data points that corroborate the merchant's willing participation.

Compare this to a traditional verification call where the only evidence might be a notation in the underwriter's CRM: "Called merchant, verified balances." If the merchant later claims they never authorized the funding, that notation carries minimal evidentiary weight. A timestamped video recording of the merchant navigating their own bank portal tells a fundamentally different story.

The importance of robust documentation was a theme we explored in depth in our piece on how MCA audit season exposes bank verification documentation gaps. The same documentation that satisfies auditors also satisfies litigation discovery requests.

Removing Broker Intermediation Risk

One of the most significant TCPA risk factors for funders is the broker acting as an intermediary during verification. When a broker handles bank statements or facilitates verification calls, the funder loses direct visibility into whether the merchant actually participated. Async verification removes this intermediation entirely. The merchant interacts directly with the verification platform. The broker cannot fabricate participation because the recording captures the merchant's live banking session in real time.

This also addresses a growing concern in the industry about trusted data channels in broker-to-funder workflows. When the verification recording comes directly from the merchant through a secured platform rather than passing through broker hands, the integrity of the evidence is materially stronger.

Practical Steps for Funders Facing the TCPA Wave

The 30% TCPA lawsuit increase is not a blip. It reflects a structural shift in how aggressively merchants and their attorneys are challenging contact practices in alternative lending. Funders who wait for a lawsuit to land before addressing their verification workflows are playing a losing game. Here is what proactive compliance looks like in practice.

First, separate your lead consent documentation from your bank verification documentation, and ensure both are independently defensible. A web form checkbox does not protect you if your verification process cannot independently confirm the merchant's voluntary participation. Second, move to applicant-initiated verification wherever possible. Every touchpoint where the merchant takes an affirmative action, opening a link, starting a recording, navigating their bank portal, creates an additional layer of documented consent. Third, ensure your verification records are stored with tamper-evident timestamps. In 2026, courts are increasingly sophisticated about digital evidence. A recording with a clear chain of custody and immutable timestamps carries more weight than a broker's verbal assurance.

Finally, review your broker agreements. If your brokers are generating leads through outbound calls, you need contractual representations about TCPA compliance and evidence of proper consent collection. Your bank verification platform should provide a secondary, independent confirmation that the merchant is a real person who actively chose to participate in the process.

Frequently Asked Questions

How does the TCPA affect MCA funders who don't make outbound calls themselves?

MCA funders can face TCPA liability even when brokers handle all outbound contact. Courts have held that companies benefiting from unauthorized calls can be treated as vicarious participants. If a broker generates a lead through a TCPA-violating call and the funder funds the deal, the funder may be named in the lawsuit. Independent bank verification that documents the merchant's voluntary participation provides a separate evidentiary layer that the funder acted on a willing applicant's request.

What is async bank verification for MCA lending?

Async bank verification is a process where the merchant records their banking portal on their own time, without a live call. The funder sends a secure link with instructions specifying what to show, such as account summaries, transaction history, and specific date ranges. The merchant opens the link, records their screen as they navigate their live banking session, and submits the recording. The underwriter reviews it later. Platforms like Exact Balance provide AI-guided coaching during the recording and full activity tracking for compliance purposes.

Can bank verification recordings be used as evidence in TCPA disputes?

Yes. A timestamped screen recording showing the merchant voluntarily navigating their bank portal serves as strong evidence of affirmative participation in the funding process. This is materially different from a broker-submitted bank statement or an underwriter's CRM note. The recording captures the merchant's active engagement, making it difficult for them to later claim they had no knowledge of or consent to the transaction.

How can MCA funders reduce TCPA exposure in their underwriting workflow?

Funders should implement verification processes that create independent proof of merchant participation beyond the initial lead consent form. Applicant-initiated async verification, robust activity logging, and tamper-evident storage all contribute to a defensible compliance posture. Additionally, funders should audit their broker networks for TCPA compliance practices and include specific contractual protections in their ISO agreements.

Conclusion

The 30% surge in TCPA lawsuits is not an abstract legal trend. It is a direct operational threat to MCA funders who cannot independently prove that their merchants voluntarily participated in the funding process. Traditional verification methods, whether live calls or broker-submitted documents, leave gaps that plaintiffs' attorneys are increasingly skilled at exploiting.

Asynchronous bank verification closes those gaps by putting the merchant in control of the process and creating a timestamped, tamper-evident record of their participation. Every link opened, every recording submitted, every banking screen navigated becomes part of a compliance trail that protects the funder long after the deal is funded.

Visit exactbalance.ca to see how async bank verification fits into your compliance and underwriting workflow, and start building the kind of documentation that holds up when it matters most.