MCA funder bank statement stacking detection — how funders identify existing MCAs on your statements.

The 60-second answer

Modern MCA funders run a dedicated stacking-detection pass on every set of bank statements they receive. The pass scans the withdrawals side of the statement looking for the daily ACH patterns that almost always identify an existing merchant cash advance.

The detection rarely misses. Funders maintain shared and proprietary databases of ACH descriptors used by other MCA funders, third-party originators, and collection agents. Even when a competing funder uses an obscure originator name, the pattern of daily-or -weekday-only fixed-amount withdrawals over a multi-month window is enough to flag the file.

For most A-paper and B-paper funders, a detected existing MCA is a hard decline. For stacking-friendly funders, it is the start of a different (and more expensive) conversation.

What the detection looks for

1. Recognized funder ACH descriptors

Each MCA funder uses one or more ACH descriptors when pulling daily payments. Some are obvious (the funder's brand name in the descriptor); some are obscured through third-party originators (Repay, Actum, Pinnacle, Drchrono, NACHA-assigned generic descriptors). The detection system maintains a maintained database of known patterns and matches each withdrawal against it.

Coverage in 2026 is high. Most of the top 100 funders are identifiable from their descriptors with above 95 percent accuracy. The remainder are caught by the pattern detection below.

2. Fixed-amount daily-frequency withdrawals

MCA daily ACH has a characteristic signature: same exact dollar amount, same time of day, business days only, persistent across weeks. Almost no other payment type has that exact shape. Vendor recurring payments are typically monthly. Payroll is bi-weekly or weekly. Card-processor fees are typically batched and variable.

The detection scans for sequences of 5+ withdrawals at the same dollar amount within a 10-business-day window. The hit rate for identifying MCAs from this pattern alone is extremely high, even when the funder descriptor is unknown.

3. Variable-amount holdback patterns

Some MCAs collect via a fixed percentage of daily card-processor settlements rather than a fixed dollar amount. These show up as variable withdrawals correlated with the card batches — typically 5–20 percent of the batch deposit, withdrawn within 1–3 days of the batch landing. The detection systems pair the deposits and withdrawals and flag the implied holdback.

4. Lockbox or sweep accounts

Some MCAs use a lockbox or sweep arrangement where customer deposits route through an account the funder controls before being released to the merchant. These show up as a large gross deposit followed quickly by a slightly smaller transfer to the merchant's operating account. The detection systems recognize the pattern as funder-controlled collection.

5. Loan-disbursement patterns

Even without ongoing payments visible, the detection can identify recently-disbursed MCAs. A large ACH credit from a known funder counterparty in the most recent 30 days, with the first daily payment not yet posted, gets flagged as "new MCA in disbursement window."

How the disclosure question interacts with detection

Almost every MCA application includes a disclosure question along the lines of: "Do you have any open MCAs? If yes, list funder names, balances, and daily payments."

The funder then runs detection and compares the answer to the detected reality. Three possible outcomes:

• Disclosure matches detection. File proceeds normally — to a stacking decline at most A-paper funders, or to a second-position conversation at stacking-friendly funders.
• Disclosure overstates the debt. The funder treats this as honest and cautious. File usually proceeds with the disclosed debt level.
• Disclosure understates the debt or denies it entirely. The funder declines for misrepresentation. This is usually a permanent flag — the merchant is unlikely to be reconsidered by that funder regardless of future credit improvement.

The third outcome is by far the worst. A merchant who has an existing MCA and discloses it honestly may be declined by 6 of 8 funders but funded by 2. A merchant who tries to hide an existing MCA is usually declined by all 8 and flagged on industry-wide databases.

The funder tiers on stacking policy

Tier 1 — strict no-stack funders

Decline any file with detected ongoing MCA. Will fund recently-paid-off files. Best pricing in the market. Most A-paper funders fall here.

Tier 2 — conditional stack funders

Will fund second position under specific conditions: prior MCA must be in good standing, combined daily payment must stay under a stated percentage of revenue (often 18–22 percent), and the merchant must accept a payoff condition that uses part of the new advance to retire the prior MCA. Pricing premium of 5–10 factor points.

Tier 3 — explicit stack funders

Will fund second or third position with full knowledge. Pricing premium 12–22 factor points. Shorter terms. Smaller offer sizes. Often used as a bridge by merchants who plan to consolidate later.

Tier 4 — distressed/predatory funders

Will fund into stacked positions of any depth. Very high factor rates, very short terms, significant penalty clauses for missed payments. Almost always the worst long-term outcome for the merchant.

Why stacking is so heavily-scrutinized

Stacking is the single largest cause of MCA default in 2026. Industry data consistently shows default rates 4–8x higher on stacked merchants than on first-position merchants. Funders price for the risk where they fund it, and avoid the risk where they can.

From the merchant's perspective, the math is unambiguous: two MCAs at the same time create combined daily ACH that almost always exceeds what the business can sustain without sacrificing payroll or vendor payments. The defaults that follow are usually forecastable from the file at the moment of stacking.

The detection systems exist primarily so that funders can either decline the file entirely or price for the visible risk. The merchant's interest is usually best served by avoiding the stack in the first place — either by consolidating into a single larger MCA at renewal time or by finding non-MCA capital (line of credit, SBA, term loan, friends and family) for the second tranche.

Worked example — three stacking scenarios

Scenario A: Merchant has a fully-paid-off MCA from 6 months ago. Bank statements show the prior daily payments stopping cleanly. Disclosure mentions the prior MCA. Underwriter treats as renewal-style and offers favorable terms.

Scenario B: Merchant has an ongoing MCA at $300/day with 4 months remaining. Disclosed honestly. Stacking-friendly Tier 2 funder offers second position at factor 1.42 with a payoff condition: $40k of the new $90k advance retires the existing MCA, leaving $50k net. Combined post-funding daily payment under 22 percent of revenue. Proceeds.

Scenario C: Merchant has the same ongoing MCA, does not disclose, hopes detection misses. Detection catches it via the daily ACH pattern. File declined for misrepresentation. Merchant flagged on industry database. No funding from any reputable source for 6+ months.

The bottom line

Stacking detection is one of the most reliable parts of MCA underwriting. The detection almost always catches existing MCAs even when the funder descriptor is obscure. The disclosure question is a test of merchant honesty more than a real information request. Merchants who disclose honestly get routed to the small set of funders that will work with their situation. Merchants who try to hide existing MCAs almost always get caught and lose access to good funders for months or longer.