Changing your payment processor while an advance is outstanding

At some point in a bad month, somebody suggests it. A friend, a broker, a forum post: just move your processing. New merchant account, new processor, and the split stops.

We are not going to explain how to do that, and it is worth being direct about why. It is a breach of nearly every merchant cash advance agreement written in the last decade, it converts a limited guaranty into personal exposure in most of them, and it turns a negotiation you could have won into a lawsuit you cannot.

What follows is the honest version: what the contract says, what happens when volume moves, and what the real alternatives are.

Why the idea keeps coming up

The logic is not stupid. If the funder is taking 15 percent of card settlements before you ever see them, and your margin is 9 percent, the split is not a payment, it is a slow shutdown. Owners who reach that point are not trying to defraud anyone. They are trying to make payroll on Friday.

The other reason is that it feels reversible. Nobody is closing an account or hiding money. You are just choosing a different vendor, something every business does.

That framing is where it goes wrong, because the agreement you signed does not treat processing as a vendor choice.

What your agreement almost certainly says

Pull your funding documents and look for three things.

The processor covenant

Somewhere in the merchant covenants section is language that you will not change, add or terminate your credit card processor, or your depository bank, without the funder's prior written consent. Many agreements go further and prohibit you from taking any action that could reasonably be expected to reduce the receipts delivered under the agreement.

Note the breadth. It is not written as "do not switch processors." It is written as "do not do anything that reduces what we collect."

The events of default list

An unapproved processor change appears there explicitly in most agreements. So does a change of depository account, a stop payment order against the funder's debits, and closing or transferring the business while receipts remain uncollected.

The consequence attached to an event of default is acceleration. The full uncollected receivables amount becomes due at once, not the days you missed. A file that was $11,000 behind becomes a $160,000 demand on the same afternoon.

The guaranty

This is the one that surprises people. Many MCA guaranties are not guaranties of repayment. They are performance or validity guaranties, which means you did not personally promise the business would generate enough revenue. You personally promised the business would not do specific things.

Read the list of guaranteed events. Diverting receipts, changing processors without consent, and interfering with collection are on it in most drafts. Trigger one and a narrow guaranty becomes a personal obligation for the whole accelerated balance.

What actually happens when volume moves

They know in days, not months. Split remittances are watched daily. A batch that drops to zero while your doors are clearly open is the single most visible event in a funding portfolio. Bank statement covenants, processor relationships and the funder's UCC filing all confirm it within the week.

The demand accelerates. See above. The number you are negotiating over stops being the days you missed and becomes the entire uncollected balance, which on a mid-cycle file is a different order of magnitude.

The legal posture flips. MCA defense often turns on arguments about the structure of the deal itself, including whether a transaction styled as a purchase of receivables functions as a loan. Those arguments get made from a position of clean hands. A documented breach hands the funder a straightforward claim and puts you on the back foot in every conversation that follows.

Your processing relationships take the hit. Acquirers and ISOs share risk information. Mastercard's MATCH database, the successor to the Terminated Merchant File, holds listings for five years, and an acquirer that terminates a merchant for cause can add one. A merchant on MATCH has a hard time getting boarded anywhere.

The receivables assignment follows you. Under UCC 9-406, a secured party holding an assignment of accounts can notify the account debtor to pay it directly. In practice that means the funder can go to a processor, and in some businesses to your commercial customers, with a notice of assignment.

The three variants, and why each ends the same way

The idea shows up in a few different costumes. All of them run into the same clauses.

A second merchant account alongside the first. The covenant language does not say "do not close your account." It says do not take action that reduces the receipts delivered. Splitting volume across two accounts does exactly that. It also means representations on the new merchant application about existing obligations have to be accurate, and if they are not, the acquirer has its own claim.

A new entity with a new EIN. Continuing the same business through a new company while receivables remain uncollected is listed as a default event in most agreements, and transferring assets or revenue streams away from a creditor is the classic fact pattern under the Uniform Voidable Transactions Act, adopted in most states. It also tends to convert a narrow guaranty into personal liability.

Moving customers to cash, checks or direct ACH. Same covenant, same result, plus a paper trail in your deposits that any underwriter or collections analyst reads in one pass.

None of these are clever. They are the specific scenarios the agreements were drafted to catch, because funders have watched them for fifteen years.

When a processor change is legitimate, and it often is

Processors fail. POS vendors get acquired. Franchisors mandate platforms. Rates get renegotiated. None of that stops because you have an advance outstanding.

The difference between a normal vendor change and a breach is entirely procedural:

1. Notify the funder in writing before the change, not after.
2. State the business reason and the new processor.
3. Ask for written consent and provide whatever authorization is needed to re-establish the split at the new processor.
4. Keep the remittances running through the transition.

Funders approve these regularly, because the arrangement continues. Consent is usually a formality when the split is preserved. It is only a fight when the funder suspects the change is about the money rather than the vendor.

What to do instead when the payment is the problem

If the actual issue is that the daily amount is unsurvivable, there are three doors, and none of them require breaching anything.

Reconciliation. Many MCA agreements contain a reconciliation provision entitling you to an adjustment when actual receipts come in below the estimate the payment was built on. This is contractual, not discretionary. It is invoked in writing, with bank and processing statements attached, and funders that ignore a properly made request create a record that matters later.

Renegotiation. Funders would rather modify a paying file than write one off. Reduced payments, extended terms and temporary holds all exist. What you can get depends on how the request is framed and what the rest of your stack looks like.

Restructuring or settlement. When the stack is beyond what any single modification fixes, the work is to consolidate the payment obligations into something the business can actually carry, or to negotiate balances down with each funder. We do that work directly with funders, and where a file has already reached litigation, cases are reviewed by experienced MCA defense counsel.

The practical next step is to find the covenants section and the guaranty page in each of your agreements and read them before anyone gives you advice about processors. Ten minutes with those two pages tells you more about your actual position than any forum thread will.