Stripe and Square close accounts suddenly because both companies run automated risk systems tuned to protect their overall merchant pool, not any single business, and both companies say so plainly in their own published policies. Neither closure is usually personal or arbitrary from their side, but from the merchant’s side it can feel exactly that way: a working account, processing normally, and then a hold or a closure notice with limited explanation.
Why do aggregators close accounts faster than dedicated processors?
Because the underwriting happened after the fact instead of before it. A dedicated merchant account goes through underwriting before the first transaction runs, so the acquirer already knows what the business sells and roughly what its risk looks like. Stripe and Square, as aggregators, approve most accounts automatically at signup and then monitor behavior continuously afterward, which means the real underwriting decision happens on an ongoing basis, transaction by transaction, rather than once upfront. When a pattern trips their automated risk models, whether that is a volume spike, a shift in what is being sold, or a chargeback pattern, the response is also automated, which is why it can feel instant and unexplained.
What does Stripe’s own policy actually say about MATCH-listed businesses?
Stripe publishes that it generally cannot process for businesses listed on MATCH absent extenuating circumstances. This matters for two different situations: a business applying to Stripe while already MATCH-listed, and a business that gets listed as a result of a Stripe termination itself. In the first case, Stripe’s own stated policy is a near-automatic decline. In the second, a Stripe termination for a qualifying reason can result in Stripe reporting the business to MATCH the same as any other acquirer would, since the one-business-day reporting requirement applies network-wide, not only to dedicated processors. Read what to do specifically after Stripe closes an account for the practical next steps.
What actually triggers a Square deactivation?
Square’s system watches for pattern changes more than absolute numbers: a sudden jump in average ticket size, a shift toward higher-risk categories of goods, an unusual concentration of transactions in a short window, or a chargeback ratio moving the wrong direction. Square, like Stripe, discloses that risk review is ongoing and automated rather than a one-time approval, and that accounts can be limited or closed based on that ongoing review. What actually happens when Square deactivates an account covers the specific timeline businesses report and what tends to help during an appeal.
Is this different from how a dedicated merchant account gets terminated?
The underlying reasons overlap heavily, chargeback ratios, undisclosed business changes, fraud patterns, but the mechanism and the warning behavior differ. A dedicated account’s acquirer usually has a named underwriter or risk analyst who can be reached, and terminations more often come with some direct communication about the reason, since the acquirer has an ongoing underwriting relationship with that specific business. An aggregator’s scale means most reviews and closures are handled by automated systems first, with human review only available after an appeal is filed, if at all. Neither system is wrong, they are built for different volumes and different business models, but the experience of being on the receiving end of a closure is meaningfully different.
Why does this happen more in certain industries?
Because aggregators’ automated risk models are trained on patterns across their entire merchant base, and certain categories generate chargeback and fraud patterns often enough that the models flag them more readily, correctly or not. Businesses in categories covered on our industries pages, including travel, supplements and credit repair, report aggregator closures at a noticeably higher rate than average retail, which is a large part of why dedicated high risk merchant processing exists as a category in the first place: an acquirer that underwrites the specific business instead of running it through a generic automated model built for a much broader merchant base.
What should a business actually do if it gets a closure notice?
Read the notice for any reason given, even a brief one, since it shapes everything that follows. Check whether funds are being held, and for how long, separately from whether the account itself is closed, since these are different questions with different answers in each company’s policies. File whatever appeal process exists, in writing, with a clear and honest account of the business rather than a defensive one. And start the process of lining up a next processor immediately rather than waiting to see if the closure reverses, since the first week after a termination is when the groundwork for a fast replacement gets laid.
Does a Stripe or Square closure always mean permanent exclusion from both?
No. A closure from one does not automatically bar reapplication to the other, though a MATCH listing resulting from either would affect both, since MATCH is checked network-wide rather than by any single company. A business closed by one aggregator sometimes moves successfully to the other if the underlying issue does not rise to a MATCH-qualifying reason code. The safer assumption is not that either closure is permanent everywhere, but that the underlying cause needs to be fixed before applying anywhere else, aggregator or dedicated account alike.
Frequently asked questions
Do Stripe and Square use the same risk criteria? No. Each company runs its own proprietary risk models, though both publish that risk monitoring is ongoing and automated rather than a one-time approval decision.
Can an appeal actually reverse a Stripe or Square closure? Sometimes, particularly when the closure resulted from a misunderstanding the business can clearly document. Neither company publishes a guaranteed appeal outcome, and reviews take real time.
Does a closure from an aggregator get reported to MATCH automatically? Only if the termination meets the card networks’ definition of a qualifying reason, the same rule that applies to any acquirer, aggregator or dedicated.
Is it worth reapplying to the same aggregator after a closure? It depends entirely on the reason for the closure and whether it has genuinely been resolved. Reapplying without addressing the underlying cause tends to produce the same outcome.