Stacking Detection
Every existing advance found before you fund, with its daily debit and the line that proves it.
Why it matters
Merchants take second, third and fourth positions within weeks; UCC filings lag the funding and other funders’ debits hide behind cryptic ACH descriptions.
How the solution handles it
Agents match recurring ACH debits to known funders, read UCC-1 filings and existing contracts, and add up what the merchant already owes each day. A checker compares what was declared with what was found. The funding underwriter decides position, payoffs and whether to fund.
How a position check moves
Five agents find every existing advance in debits, UCC filings and contracts and add up the burden; a funding underwriter decides the position.
What it reads, and what it hands back.
What goes in
- Business bank statements
- UCC-1 search results
- Credit report inquiries
- Existing MCA contracts and payoff letters
- Application disclosures
What comes out
- Position map with daily debits
- Combined holdback burden
- Undisclosed-position flags
- Payoff and consolidation conditions
Who uses it
The difference, in numbers.
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“Target” = design goal, measured in the live solution · “Typical” = decline thresholds reported in funder underwriting guides · UCC filings can lag funding by weeks, so debits are read too
5 specialist agents. One person decides.
More in this division.
Every ISO submission read, screened and routed within minutes of arriving, while the merchant is still shopping.
Statement UnderwritingSix months of statements scrubbed to true revenue and daily balances in minutes, every number tied to its line.
Altered StatementsEvery statement tested for edits before it is underwritten, each finding marked on the page.
Build this
for your team.
We’ll show Stacking Detection running on your own documents.