Stripe rejected or restricted your account: why, and what to do

Updated August 2026

Stripe rejections come in two flavors: an application that never gets approved, and — more painful — an account that worked for weeks and then gets restricted after a periodic re-review, sometimes with funds held. Both usually trace back to the same place: what your website says.

The common reasons, in rough order of frequency for SaaS

Your website reads as a restricted category. Stripe maintains a restricted-businesses list, and its risk systems classify you by your site's language. Vocabulary implying unsolicited contact ("leads", "outreach", "scraping"), income claims, or engagement-selling puts a legitimate product into a restricted bucket by association. This is the classic fixable rejection — see the vocabulary guide.
The business can't be verified. Identity documents, business registration, or the website not matching the legal entity on the application.
The site is incomplete. No terms, privacy, or refund pages; no visible pricing; no way to see the product; no contact information. (Legal-pages checklist.)
Actual restricted activity. If the product genuinely is in a restricted category, no rewording helps — you need a processor that explicitly supports that category.

Restricted after weeks of working fine?

Stripe re-reviews live accounts — a copy change, a spike in volume, or a routine sweep can trigger it. The frustrating implication is also the useful one: the review is of your current website, so fixing the website is a real lever even mid-restriction.

Check your own copy in 30 seconds. The free Audeza scanner flags the phrases payment platforms treat as risk signals — and suggests safer wording. No signup.

Run the free check

What to do, in order

Fix before you reply. An appeal against an unchanged site gets an unchanged answer. Audit the copy, add the missing pages, make the product inspectable.
Answer their questions literally and completely. Stripe's emails usually ask something specific. Vague or defensive replies stall; boring, factual, complete replies move.
Describe what the product factually does — including the phrases that remove the risk scenario ("no automated sending", "users contact their own customers only").
Never open a second account to route around a rejection. That's ban evasion; it converts a fixable copy problem into a permanent fraud flag.

If Stripe stays closed: the merchant-of-record route

A rejection from Stripe is not a rejection from the ecosystem. Merchants of record — Paddle, Polar, Lemon Squeezy — run their own underwriting, and for a solo SaaS founder they remove the VAT/sales-tax burden too (the trade-offs: Stripe vs merchant of record). Their reviews check the same fundamentals, so fix your site first, then apply — the pre-flight checklist is the 10-minute version.