How to detect MCA stacking before you fund

Why stacking is the primary MCA default driver

Stacking — a merchant obtaining multiple simultaneous advances from different funders, often without each funder's knowledge — concentrates daily remittance obligations until they exceed the merchant's available cash flow. A merchant remitting to three or four funders simultaneously may be paying out a larger percentage of daily revenue than the business can sustain, creating a default cascade where the merchant stops paying all funders at once.

The detection challenge is that individual funders see their own position clearly but often have no visibility into how many other advances are outstanding. A merchant who appears to be a clean risk based on their bank statements from three months ago may have taken on two additional advances in the weeks between application and funding.

Detection signals and data sources

The most actionable pre-funding stacking signals are found in the merchant's bank statements from the most recent 30 to 60 days. Look for: regular daily or weekly ACH debits with descriptors matching known MCA funder names; multiple round-number daily debits of the same amount (a hallmark of simultaneous remittances to different funders); and a total daily outflow that, when added to the proposed new remittance, would exceed a prudent percentage of average daily deposits.

Beyond bank statements, UCC lien searches against the merchant's business name and EIN reveal existing secured interests — MCA funders typically file UCC-1 financing statements. Commercial credit bureaus (including some MCA-specific databases) aggregate lender-reported positions and can surface concurrent obligations not yet visible in bank statements. A robust pre-funding check pulls at least the bank statement analysis and a UCC search; adding a commercial bureau lookup materially reduces residual stacking exposure.

Building a repeatable stacking check into the underwriting workflow

Ad hoc stacking checks are inconsistently applied as volume scales. A repeatable process defines: which data sources are checked on every deal (not just large ones), at what point in the workflow the check occurs (as late as possible before funding — ideally within 24 hours of funding date), who is responsible for clearing each signal, and how the check result is documented in the case file.

The case file should record the stacking check as a distinct step with a timestamp, the sources consulted, the findings, and the underwriter's disposition. If stacking is identified and the funder elects to proceed (for example, because the total remittance burden is still within an acceptable threshold), the documented rationale is the evidence that the risk was understood and accepted — not missed.

FAQ

How to detect MCA stacking — common questions

Related