The overnight email is the whole file now. Your processor cut the account, and the packing table still has orders. What to do when your processor drops you is smaller than it feels: read the notice before you type a reply, save every page of it, stop charging on a dead MID, and ask in writing where residual funds sit.
That is the morning. The weeks after live on a different page. Today you keep the record clean and you stop making the hole deeper.
Read the notice before you reply
Open the email, the in-app banner, and any PDF sitting in the merchant portal. Save all three before you touch live chat. Portal copy disappears. Chat logs get summarized by a vendor you will never speak to again.
Read for the words that travel. MATCH, TMF, terminated for cause, prohibited, acceptable use, and risk review are the ones a later underwriter will ask you to explain. A soft line like “we are no longer able to support your business” still ends the MID. It just tells you less. If the letter names Mastercard’s MATCH file, treat that as part of the event, not a side note. MATCH is Mastercard’s database of merchants an acquirer terminated for cause, as Mastercard sets out in its Security Rules and Procedures.
Write one question, in email, once. Ask them to confirm the reason in writing. Ask whether they reported the MID to MATCH or to Visa’s merchant screening service. Ask for the merchant ID, the legal name on the file, and the date the account closed. You already know it closed. You need the paper.
Skip the first angry call. A phone agent can read a script. They cannot un-decide an acquirer’s risk file. Anything you shout becomes a note. Anything you invent, a product you “will stop selling,” a volume you “never really ran,” sits in that note when the next bank asks for history.
Stay inside what you can prove. If the store sells a subscription, say it sells a subscription. If last month’s disputes spiked after a delayed ship, say that. The processor already has the dispute file. Your job today is to capture their reason, not to win the argument.
A complaint, a chargeback on their fee, or a social post does not put the MID back on. The acquirer that closed you made a risk decision. We place a new file later. We do not reverse theirs.
If the notice is a Stripe closure, a Square deactivation, or a PayPal limitation, you are looking at an aggregator cutoff. Those platforms can darken checkout in a night. Save the email anyway. The next underwriter will ask for it by name.
Funds, MATCH, and what to save
Money from yesterday’s batches is still in their system. It does not move because you are upset, and it does not vanish because the MID is dead. It sits where the processing agreement already said it would sit: pending settlement, a reserve, a rolling hold, or a closure hold while refunds and disputes drain off.
Ask in writing where each bucket is. Pending batches. Reserve. Refunds already in flight. How they want a payout request. Who the acquiring bank is, if they will name one. You want dates and account last-fours, not a chatbot paragraph.
PayPal is the one hold with a published ceiling we can point to. PayPal’s User Agreement says PayPal may hold funds for up to 180 days when an account is limited or closed. That is a maximum they reserve the right to apply, not a clock that starts the same way for every shop. Other processors write their own hold language. Read that language. Do not borrow PayPal’s number and paste it onto Stripe or Square.
MATCH is the other file that can outlive the money. If the acquirer adds you, Mastercard keeps the listing for five years from the add date and then purges it. No application. No fee. Only the acquirer that placed the listing can take it off earlier, and only where it was added in error or where reason code 12, PCI DSS non-compliance, applies and the underlying issue is fixed. That rule lives in the same Mastercard manual. We cannot remove a listing. Nobody selling “MATCH removal” can either.
Some notices never say MATCH and still lead there. A letter that cites excessive chargebacks is speaking the language of MATCH reason code 4. Mastercard’s test, as reproduced in Stripe’s MATCH documentation, is a calendar-month pair: Mastercard chargebacks over 1% of that month’s Mastercard sales, and those chargebacks totaling USD 5,000 or more. Both in the same month. Excessive fraud is reason code 5, with its own pair of tests. You do not need to litigate the code today. You need to see whether the letter is already using that vocabulary, then read the MATCH list before you fill in anyone else’s application.
Save a folder while the portal still lets you in.
- Export or screenshot the closure notice, every attachment, and the portal banner that says the account is restricted.
- Pull statements, payout reports, dispute notices, retrievals, and the processing agreement, as far back as the portal will still give you.
- Copy the MID, the DBA, the legal entity, the descriptors customers saw on their card statements, and the last few settlement deposits into your bank.
Twelve months of statements is the file an underwriter actually reads. If the portal will only give you ninety days, take the ninety and add bank deposits that show the rest. Do this before you argue. Access is a privilege they can cut.
Stop charging, then pick the next path
Turn card checkout off. A dead MID still attached to Shopify, WooCommerce, or an invoice tool will fail in front of the customer, or worse, it will look live while every auth declines. Stored cards and subscription rebills are the quiet leak. A rebill that hits a closed account is a failed renewal and a support ticket you now owe.
Pause the card button. Leave ACH, wires, and existing unpaid invoices on a path that does not touch the dead processor. If a box is already labeled and the card was captured yesterday, ship against funds you can still see. Do not run a new card “just this once” on an account the processor has already closed.
Then pick the next rail with the termination in the open. An aggregator (Stripe, Square, PayPal, and the checkout buttons that sit on top of them) underwrites in batches and can cut you the same way they just did. A dedicated merchant account is a MID at an acquiring bank, with a named underwriter and a file. The difference is the subject of payment aggregator vs merchant account. Day one is when people reach for another aggregator because the form is short. That is how you collect a second closure before lunch.
If you already opened a backup merchant account while the first one was healthy, this is the morning that account was for. Point the gateway at it. Tell the backup’s underwriter that the primary MID closed, and send the notice. Surprise is what burns a backup. Disclosure is what keeps it.
If you do not have a backup, you have a gap. We can read the notice and the statements with you and place a file with an acquirer that actually boards the category. We do not approve the application. The acquiring bank does. If no acquirer we know will take the file, we say that. The rest of the sequence, residual funds, a second account, and living with a MATCH hit, is on the longer page for what to do when your processor drops you. Today you stop the bleeding and you keep the documents.
Causes live on a separate post. If you need the pattern that got the MID killed, read what gets a merchant account terminated after the checkout is dark. Do not diagnose the account while cards are still hitting it.
What not to do on day one
Do not open a new aggregator under a different email, a spouse’s name, or a fresh LLC while the old store, the old descriptor, and the old fulfillment address stay the same. That is the same merchant with a costume on. Underwriters compare tax IDs, URLs, processors’ prior closures, and MATCH. A second shutdown on a hidden file is worse than one honest closure.
Do not split next week’s volume across three new buttons to duck a monitoring program. Do not change the MCC story so a supplement brand looks like a bookstore. Honest disclosure is the only version of this story that still has a next processor.
Do not keep the card form live “until the declines pile up.” Customers who pay twice, or who never get a ship date, file disputes against a MID that can no longer respond well. Those disputes still attach to the business.
Do not promise the room that cards will work this afternoon. Tell staff the processor closed the account. Take phone orders onto a method you still control. Update the site banner so people stop paying into a dead rail.
Do not sign the first high-risk contract that lands in the inbox before you have read the reserve, the termination clause, and the rolling hold. A merchant sees the full schedule, including any reserve, before signing. If a salesperson will not put the reserve in writing, you do not have an offer.
Do not spend the day trying to get the old acquirer to take it back. Send the written questions. Save the answers. Move the store. The old decision stays theirs.
Frequently asked questions
Can I keep running cards today on the account they just closed?
No. Turn checkout off and stop stored-card rebills on that MID. Auths will fail, and a charge that somehow lands still sits on a processor that has already ended the relationship. Take new orders on a method that is still yours.
How do I know if they put me on MATCH?
The notice sometimes says MATCH or TMF in plain text. Sometimes it only says terminated for cause. Ask the processor in writing whether they reported the MID. Only that acquirer, and Mastercard’s process, control the listing. A later application that comes back declined for a prior termination is often how a merchant finds out.
When do I get the money still sitting with them?
Ask in writing where pending batches, reserves, and closure holds sit, and how they pay them out. PayPal may hold funds for up to 180 days when it limits or closes an account, as a maximum in its User Agreement. Other processors follow their own agreement. Nobody here can force a faster release.
Should I open Square or Stripe under a new email so the store can sell this week?
Apply later, on the real entity, with the closure in the file. A new aggregator login that hides the last termination is a second risk event, not a fix. If you already have a dedicated backup MID, use that and tell that underwriter what happened.
Will a new merchant account undo the old processor’s decision?
No. The old acquirer closed their MID. A new file is a new MID at a new bank. We can help place that file. We cannot reopen the one they shut off.