How the shutdown happens
Stripe's onboarding is designed for speed. Any application that passes basic KYC and document checks gets approved — often within hours. The automated system doesn't deeply evaluate what you sell. It checks identity, business registration, and banking details. If those clear, you're live.
The review comes later. Somewhere between 30 and 90 days, Stripe's compliance team manually reviews the account. They look at the actual product, the website content, and the transaction patterns. If the business operates in a restricted category — nutraceuticals, CBD, peptides, prop trading, crypto, iGaming — the account gets terminated. The business can be completely legitimate, fully compliant, with healthy chargeback ratios. Doesn't matter. Category policy overrides everything.
The cycle that follows
After a Stripe shutdown, the merchant scrambles. They sign up with another mainstream processor — maybe Square, maybe a PayPal checkout, maybe a smaller Stripe competitor. The same pattern repeats: automated approval, a few months of processing, manual review, termination.
- Each shutdown kills active subscriptions that can't be migrated to the new processor
- Customers receive decline notifications and lose trust in the brand
- Days of revenue are lost during every transition
- Subscriber re-enrollment rates drop with each successive switch — most customers don't re-enter payment details
- The merchant's internal team spends more time managing payment crises than running the business
Some merchants try to obscure what they sell — vague product descriptions, generic MCCs, indirect language. This delays the shutdown but doesn't prevent it. When it happens, the termination is worse: the processor flags it as deceptive, which can result in MATCH listing and make future PSP applications harder.
Why 'find a better mainstream processor' doesn't work
Stripe, Square, PayPal, and Adyen's retail product all operate the same way. They're built for low-risk, high-volume onboarding. Their acquiring bank relationships don't include restricted categories. No amount of clean processing history on your end changes the acquiring bank's category policy. The problem is structural, not reputational.
What actually fixes it
The fix is onboarding to PSPs that explicitly underwrite your vertical — what proper high risk payment processing looks like in practice. These processors have acquiring bank relationships where the restricted category is in the risk appetite. The application discloses exactly what you sell — full transparency from the start. The acquirer knows what they're underwriting. There are no surprises and no delayed terminations.
- Application discloses the vertical up front — no category surprises downstream
- Acquiring bank has the category in its risk appetite and prices for it
- Fees are higher than Stripe's headline rate — but Stripe's rate is meaningless if the account gets closed
- The relationship is built on transparency, which means it lasts
- Stability compounds: subscriptions survive, customers trust the checkout, and the business can plan around reliable payment infrastructure
The fee difference is real. A high-risk PSP charges more than Stripe's 2.9% + 30¢. But a rate from a processor that's going to terminate you in 90 days isn't a real rate. Stability is the variable that matters for any business running subscriptions, recurring billing, or customer lifetime value models. The alternative — what an actual high-risk merchant account looks like structurally — is a fundamentally different commercial relationship.
Key Takeaways
- Stripe approves via automation and terminates via manual review — 30 to 90 days later.
- Restricted categories get shut down regardless of compliance or chargeback health.
- Cycling through mainstream processors repeats the same pattern and destroys subscriber trust.
- The fix is a PSP that underwrites your specific vertical with full category disclosure.
- Higher fees on a stable account always beat low fees on a temporary one.