MCA Stacking Detection: How Funders Catch It Before It Costs Them
The Problem with Stacking Isn't That It Happens — It's That You Find Out Too Late
A merchant takes a $50,000 advance from you in January. By February, they've stacked three more positions on top of it from other funders. Their daily remittances are now split six ways. By March, they're defaulting — and you're fourth in line.
This is not a hypothetical. It's the default failure mode for MCA funders who don't have stacking detection built into their underwriting workflow.
The industry loses hundreds of millions annually to stacking-related defaults. The funders who avoid the worst of it aren't smarter — they're faster. They catch stacking before funding, not after.
What MCA Stacking Actually Is
Stacking occurs when a merchant takes multiple merchant cash advances simultaneously from different funders, without disclosing existing positions. Each funder believes they have a clean deal. In reality, the merchant's daily revenue is already committed to multiple remittance streams.
There are two forms:
Disclosed stacking — the merchant tells you about existing positions. Some funders allow this with adjusted terms. Most don't.
Undisclosed stacking — the merchant hides existing positions. This is the one that kills portfolios.
The challenge is that undisclosed stacking is designed to be invisible at the point of underwriting. The merchant submits clean bank statements, a fresh application, and a plausible story. The stacked positions don't show up in a standard credit pull.
Why Manual Detection Fails at Scale
The traditional approach to stacking detection involves pulling a UCC lien search, reviewing bank statements for evidence of existing remittances, calling references, and manually cross-referencing against known MCA funders.
This works when you're doing 10 deals a week. It breaks down at 100. At 500+ deals per month — where competitive MCA funders operate — manual detection becomes a bottleneck that either slows your pipeline or gets skipped entirely.
| Method | Time per Deal | Scalable? | |---|---|---| | UCC lien search | 20–30 min | No | | Bank statement review | 45–90 min | No | | Industry database check | 10–15 min | Partially | | Manual cross-reference | 30–60 min | No |
At 300 deals per month, thorough manual stacking detection requires 3–5 full-time underwriters doing nothing else. Most operations don't have that. So they cut corners — and stacking slips through.
How Automated Stacking Detection Works
The funders running the tightest stacking detection aren't doing it manually. They've built systems that do three things automatically:
Bank statement pattern analysis — Bank statements contain fingerprints of existing MCA positions: regular daily or weekly debits to known MCA funders, remittance patterns that don't match the merchant's stated revenue, and balance drawdowns that suggest multiple cash advance obligations. Automated systems extract these patterns from raw PDFs in minutes and flag merchants whose remittance patterns suggest 2+ existing positions before a human ever reviews the file.
UCC filing cross-reference — UCC-1 filings are public record. Every MCA funder that takes a security interest files one. Automated systems query UCC databases in real time, cross-reference the merchant's EIN and legal name against known MCA funder filing patterns, and surface existing positions that wouldn't appear in a standard credit pull. The limitation: UCC filings have a lag. A position taken 30 days ago may not be indexed yet — which is why bank statement analysis matters.
Industry data cross-referencing — Some funders participate in data-sharing consortiums that flag merchants with active positions across multiple funders. This is the most direct detection method but requires network participation to be effective.
The combination of all three — run in parallel, automatically, before underwriting review — is what gets stacking detection from 1–2 days down to under 10 minutes.
What 10-Minute Detection Actually Changes
The speed difference isn't just operational efficiency. It changes what's possible in your pipeline.
When detection takes 1–2 days, it becomes a gate that slows every deal. Underwriters wait on results before proceeding. Merchants who applied to multiple funders get funded by whoever moves fastest — often not you.
When detection runs in 10 minutes at intake, it becomes a filter, not a gate. Clean deals move immediately. Flagged deals get a second look. Your underwriters spend their time on credit decisions, not data gathering.
One MCA operation we worked with was running stacking detection manually across a team of three underwriters. After automating the process, those three underwriters handled 3x the deal volume with the same headcount — and the stacking-related default rate dropped by over 40% in the first six months.
Building vs. Buying
Off-the-shelf MCA platforms — Some loan management systems include basic stacking detection. Most rely primarily on UCC searches, which miss recent positions. Fine for low volume, insufficient for competitive operations.
Third-party detection services — Dedicated services that specialize in MCA fraud and stacking. Better coverage, but you're paying per lookup and dependent on their data refresh cycles.
Custom-built detection — An automated pipeline built for your data sources, your underwriting workflow, and your risk thresholds. Higher upfront investment, but it runs on your infrastructure and improves as your portfolio data grows.
For funders doing under 50 deals per month, a third-party service is probably sufficient. For funders doing 200+ deals per month, the cost of missed stacking at that volume typically justifies a custom build within the first year.
The Honest Assessment
No system catches 100% of stacked positions. UCC lag, data gaps, and sophisticated merchants mean some will get through. What automated detection does is change the economics — it makes detection fast enough to run on every deal, thorough enough to catch the majority of cases, and cheap enough that the system cost is a fraction of the defaults it prevents.
The funders losing the most to stacking aren't the ones who got unlucky. They're the ones who made detection optional.
If stacking is a meaningful part of your default rate, it's worth understanding exactly what your current process is catching and what it's missing. Book a 30-minute scoping call with our team — we'll map your current workflow, identify the gaps, and give you a concrete estimate of what automated detection would cost and save. No slide decks. Just numbers.