An MCA anti stacking clause is the promise in a merchant cash advance agreement that the merchant will not sell more of its future receipts, or take similar financing, while the advance is open unless the funder agrees. The funder checks for breaches in later bank statements, and a confirmed breach is usually written in as a default event.
What does an MCA anti-stacking clause prohibit?
An MCA anti-stacking clause prohibits the merchant from taking another advance, or any financing that claims the same receipts, before the current one is paid. The goal is to protect the share of daily sales the first funder bought. Most clauses reach further than other advances.
Read the scope line by line, because the reach varies between agreements. A narrow clause names only merchant cash advances and other purchases of future receipts. A wider one adds any financing repaid by automatic debit from the operating account, or any financing secured by the same receivables. The widest version bans any new debt at all without written consent, which is hard to police and easy for a merchant to break without noticing.
Clauses also differ on what they leave alone. Many carve out ordinary trade credit from suppliers, equipment leases and credit cards used in the normal course of business. Some allow a new advance if it pays the existing one off in full on the day it funds. That last carve-out matters, since a payoff from a new funder ends the first funder's exposure instead of adding to it.
Anti-stacking clause wording funders put in the agreement
Anti-stacking clause wording usually sits in three parts of the agreement: the merchant's covenants, the representations made at signing and the list of default events. Each part does a different job, and a clause with the ban but no remedy gives the funder little to act on.
The table below shows the parts a funder usually drafts. The wording in the middle column is an example written for this post, not text from any real contract, and counsel should draft the actual language.
| Clause part | Example wording | What it does |
|---|---|---|
| Scope | "Merchant will not sell, assign or encumber future receipts to any other party" | Defines what counts as stacking |
| Representation | "Merchant has disclosed every open advance and loan" | Makes the application a promise, not just a form |
| Consent | "Except with the prior written consent of the funder" | Lets the funder approve a new position case by case |
| Notice | "Merchant will notify the funder within two business days of any new financing" | Creates a duty that can be breached on its own |
| Remedy | "A breach of this section is an event of default" | Links the ban to the default terms |
| Carve-outs | "Trade credit and equipment leases in the ordinary course" | Keeps the ban from catching normal business debt |
The representation line does real work at renewal time. A funder looking at a renewal of an existing MCA compares the new statements against what the merchant disclosed. An undisclosed position found then is both a broken covenant and a false statement in the original file.
Who signs also matters. Many agreements ask the owner to sign a performance guarantee next to the business. Where spouses or other people are asked to sign, the funder should check the limits in the ECOA spousal signature rule before adding names to the signature page.
How do funders catch a stacked advance after funding?
Funders catch a stacked advance after funding by reading the merchant's later bank statements for a new deposit from another funder, followed by a new recurring debit a few days later. Some agreements require the merchant to send statements each month or to keep bank login access open so the funder can check.
The signals look the same as they do at underwriting. A large credit with a funder's name, a fresh daily or weekly debit of a fixed amount, or a rise in total debits against flat sales each point to a new position. The underwriting guide explains these signals in more depth under stacked positions spotted in MCA underwriting.
Monitoring adds one signal that underwriting does not have: the funder's own debit. If the funder's scheduled debit starts bouncing soon after an unknown credit appears, the new funder may be pulling from the same account first. Returned debits deserve a quick look at the full statement, not just a retry.
Brokers see this from the other side. An ISO that sends a file with several open positions should list them all on the submission, as the MCA ISO submission guide explains, because a funder that finds a hidden position later may treat the whole file as misrepresented.
A tool can help with the reading. TrueBankFlow sorts each statement line into categories such as loan payments and flags out-of-pattern deposits with the date and line, so an analyst can spot a new funder's credit quickly. Deciding whether that credit breaks the contract stays with the funder.
Anti-stacking clause breach remedies and default
Anti-stacking clause breach remedies follow from the default section of the agreement. Once a breach is confirmed, the funder can usually call the remaining balance due, add fees the contract names, and enforce the owner's performance guarantee. The exact options depend on the agreement and the governing state law.
In practice, funders often start softer. A call to the merchant may show the new advance was taken to cover a slow month, and the funder may accept a written promise not to take more. A funder might also ask the merchant to pay the new position off, or agree to a revised schedule that leaves the account room for both debits.
Harder steps come when the account can no longer carry the payments or the merchant stops answering. These include notices to the merchant's card processor, claims against the guarantor and litigation. The steps and their limits are part of what happens when a merchant cash advance defaults.
Funders should record each step in the file: the date the new position appeared, the statement line, the contact made and the merchant's answer. That record supports the funder if the case reaches a court, and it helps decide whether to work with the merchant again later.
When an anti-stacking clause does not stop a second funder
An anti-stacking clause binds only the merchant who signed it, so it does not stop a second funder from funding. A later funder may never see the first contract, or may see it and fund anyway at a higher price, accepting the breach risk itself.
That gap explains why stacking keeps happening. The merchant needs cash, a second funder offers it, and the first funder learns of it only from the next statement. The clause gives the first funder a claim against the merchant, but a claim against a business that is short on cash may not be worth much.
A few other weak points are worth knowing:
- Vague scope. A clause that bans "loans" may not reach a sale of receivables, which the other funder will say is not a loan.
- No notice duty. Without one, the merchant can stay silent until a debit bounces.
- No monitoring right. A funder with no right to later statements may only find out after a default.
- Remedies the funder will not use. Calling the full balance on a merchant who is still paying can turn a performing deal into a loss.
Clauses still work as a filter at signing. Merchants who intend to stack sometimes refuse to sign a strong one, and that refusal is itself useful information.