Stripe 'Your Account Has Been Restricted' Email: What It Means (2026)
Stripe restriction email decoder: what restricted vs deactivated means, why accounts get restricted, the exact appeal steps, template, and evidence checklist.
Stripe 'Your Account Has Been Restricted' Email: What It Means (2026)#
TL;DR: Stripe's enforcement emails come in escalating tiers — "under review" (processing usually continues), "restricted" (payouts held), "deactivated" (terminal-adjacent) — and the exact wording tells you which stage you're in. The single most important move is to respond once, completely, through the Dashboard's "Submit information" flow, with documents that directly answer every risk signal the email names. Never open a second Stripe account while restricted — that reads as evasion and almost always ends in permanent termination.
Reading a Stripe restriction email at 7 a.m. is one of the more sickening moments of running an online business. The subject line is vague, the body is terse, and the same words can carry different mechanics depending on where they appear. Your payouts have stopped. Customers may still be able to pay you — or may already be seeing failures — and nobody at Stripe has told you in plain language what happened, why, or what you need to do.
This guide exists because most of the anxiety in that moment comes from not knowing which situation you're actually in. Stripe's enforcement communications escalate in tiers, and the wording of each tier tells you something concrete: whether you can keep processing, whether your money is frozen and for how long, and — critically — whether the situation is recoverable at all. Once you know which tier you're in, the response path becomes a finite, document-driven project instead of a panic.
It also exists because Stripe reviews are won and lost on paperwork, not apologies. A complete, consistent, evidence-backed response submitted through the correct channel resolves the majority of restrictions. A vague "we're sorry, please reinstate us" message does the opposite — it signals that you don't understand what triggered the review, and it invites the reviewer to look harder. Below you'll find the tier decode, the real reasons accounts get restricted, the exact submission flow inside the Dashboard, a fill-in appeal template, an evidence checklist, and the prevention habits that keep you out of the review queue in the first place.
One warning before we start, because it's the most expensive mistake people make: do not register a new Stripe account to keep taking payments while your current one is restricted. Stripe links accounts through identity data, bank details, device fingerprints, and business records. Circumventing a restriction is treated as an integrity violation and almost always converts a recoverable restriction into a permanent termination across all linked accounts.
Why Stripe Suspends Accounts#
Stripe restrictions almost always trace back to one of five trigger families. Your email will usually hint at which one applies, and your entire response should be built around it.
1. Dispute and Refund Spikes#
The most common risk trigger. If your dispute rate or refund rate jumps sharply — approaching or crossing the chargeback monitoring program thresholds set by the card networks — Stripe's automated risk systems flag the account. This can happen to a healthy business after a single bad product launch, a fulfillment delay, a misleading ad, or a card-testing attack. What matters here is that Stripe isn't asking whether the disputes were "fair" in the abstract; it's asking whether the underlying transactions are legitimate and whether you can demonstrate fulfillment and refund handling.
2. Mismatch Between Actual Business and Registered MCC#
When you activated your Stripe account, you declared your business type and industry, which maps to a merchant category code (MCC). If the business Stripe observes through your transactions, website, and customer complaints doesn't match what was declared — for example, you registered as "consulting" but are processing payments for a subscription box — the discrepancy reads as misrepresentation, and reviewers take it seriously even when the intent was innocent.
3. Unregistered Restricted Businesses#
Stripe maintains categories of restricted and prohibited business activity, including adult content, gambling, forex and certain financial services, and others. If you're processing for one of these without prior approval, the restriction email will often cite the relevant clause of the Stripe Services Agreement. This is one of the harder trigger families to appeal, because the business model itself — not your conduct — is the problem. Some categories can be approved through a formal underwriting review; others cannot.
4. Expired or Inconsistent KYC Data#
The friendliest trigger. KYC requirements mean Stripe must have current, matching records for your legal entity: the identity of beneficial owners, the bank account details, and the website information submitted at activation. If your ID document expired, your bank account changed without re-verification, or your site no longer matches what you submitted, you'll get an information request rather than a hard restriction — but ignoring it escalates into one.
5. Failed Website Review#
Stripe's underwriting and periodic reviews check your website for the disclosures required for a legitimate card-accepting business: terms of service, a refund and return policy, a privacy policy, contact information, and a description of the product or service being sold. If any of these are missing, empty, or contradictory (for instance, a refund policy that says "all sales final" on a product customers routinely dispute), the website review fails and the account is restricted until it passes.
Most restrictions are a combination: a dispute spike layered on top of a website that doesn't clearly explain the product, or a KYC gap discovered while investigating complaint patterns. Your response should address every element you can identify, not just the loudest one.
Appeal Entry Point and Process#
Stripe's restriction appeals do not run through email replies or a public form. Everything happens inside the Stripe Dashboard and, where needed, through support tickets. Here's the working sequence.
Step 1: Open the Dashboard and Read the Restriction Banner#
Log into dashboard.stripe.com. A restricted account shows a prominent banner at the top of the screen stating the restriction and, in nearly all cases, a "Submit information" button or an equivalent link into the review flow. This banner is your ground truth. It names the review area (risk, compliance, verification, disputes) and lists precisely what Stripe needs. The email you received is a notification; the Dashboard is the actual case file. Before writing anything, click through the entire review flow and inventory every requested item. Write the list down. Partial or fragmented responses are the single most common self-inflicted wound in Stripe reviews, because each new submission re-opens the review clock and reads as inconsistency.
Step 2: Fix the Live Account State Before You Submit#
Reviewers re-check your account after you respond, so repair whatever triggered the restriction first. If the trigger was website review failure, add or repair the missing pages — terms, refund policy, privacy policy, contact details, product description — and make sure they're consistent with how you actually operate. If the trigger was a dispute spike, update your billing descriptor so customers recognize charges, respond to open disputes with evidence, and make sure your refund process works and is documented. If the trigger was a business/MCC mismatch, update your business profile in Settings so it accurately describes what you sell. Submitting a response while the underlying problem is still live is the second most common mistake: it guarantees a second review cycle.
Step 3: Assemble the Complete Evidence Package#
Using the checklist in the next section, gather every named document plus the adjacent consistency materials. Stripe's reviewers are checking for coherence: does the bank statement match the invoices, does the invoice match the website's product, does the shipping proof match the customer address on the disputed transaction. A package that answers each named item with matching supporting evidence ends reviews. A package that only answers the named items, without consistency materials, invites a follow-up request and another week of frozen payouts. If your restriction is KYC-related, this step may be all that's needed: update the business information in the Dashboard, upload the verification documents, and wait for the risk re-check — no narrative appeal required.
Step 4: Submit Once, Through the Dashboard, Then Follow Up Intelligently#
Write your response using the template in the next section, attach the full evidence package, and submit it through the "Submit information" flow in a single complete response. After submission, Stripe's review typically takes anywhere from a few business days to two weeks for straightforward cases; reviews involving high-risk industries or deeper compliance questions can take longer, and Stripe does not guarantee reinstatement regardless of the quality of your response. If you hear nothing after two weeks with a complete response on file, send one concise follow-up through a support ticket referencing your original submission — not a new case, and not multiple tickets, which fragments the record. Our step-by-step reinstatement walkthrough covers the post-deactivation variant of this flow in more detail.
How to Write the Appeal#
A strong Stripe response is a factual document, not a plea. It has three parts: a factual statement addressing each cited risk signal, an acknowledgment of the problem where one genuinely exists, and a concrete description of the remediation you've already implemented. Copy this structure and adapt it:
SUBJECT: Response to account restriction — [Business legal name], acct ID [from Dashboard]
1. FACTUAL RESPONSE TO EACH CITED SIGNAL
Signal 1 — [e.g., "elevated dispute activity in recent weeks"]:
- Dispute volume: X disputes on Y transactions over the period = Z% of volume.
- Root cause identified: [e.g., shipping delay after carrier disruption in March;
misleading ad variant on Meta that has since been paused].
- Evidence attached: fulfillment records for all disputed transactions
(tracking numbers, delivery confirmations), customer communications,
proof of refunds issued where fulfillment was not possible.
Signal 2 — [e.g., "additional information about your business"]:
- Business activity: plain-English description of what we sell, to whom,
and how it is delivered.
- Documents attached: entity registration, ownership IDs, bank statement,
supplier invoices, and screenshots of the updated website pages
(terms, refund policy, contact page, product description).
2. ACKNOWLEDGMENT
We take this seriously. [State plainly what went wrong — e.g., "Our billing
descriptor did not clearly identify our brand, which contributed to
customers not recognizing charges." Do not fabricate an explanation and
do not deny verifiable facts; reviewers have the transaction data.]
3. REMEDIATION ALREADY IMPLEMENTED
- Billing descriptor updated to "[new descriptor]" on [date].
- Website updated: refund policy, terms of service, and contact page now
live at [URLs], consistent with our actual practices.
- Refund process: refund requests now processed within [X business days],
with automated confirmation emails (sample attached).
- Dispute handling: all open disputes responded to with evidence; [N]
resolved in our favor / refunded proactively.
4. WHAT WE'RE ASKING FOR
We respectfully request that the restriction be lifted and normal payout
processing resumed. We're happy to provide any additional information or
accept interim conditions (e.g., a rolling reserve) that would allow
processing to continue under closer monitoring.
[Name, role, phone, email — must match the account's listed owner]
Three principles govern this template. First, respond to the specific signals, item by item — the pro tip that matters most in Stripe reviews is answering exactly what the email lists, not submitting a generic apology. Second, own real problems: if the descriptor was confusing or a product launch went badly, say so plainly and show the fix. Reviewers respond to demonstrated operational maturity; evasion reads as future risk. Third, show, don't promise: every remediation item should be dated and verifiable, because reviewers can and do re-check the live account.
Evidence Checklist#
Use this before you hit submit. The goal is that every named item has a document, and every document has a matching corroborating item.
- Copy of the restriction email and a screenshot of the full Dashboard banner, including the exact items requested
- Government-issued photo ID (current, unexpired) for the account owner and all beneficial owners listed on the account
- Business formation documents: certificate of incorporation, business registration, or equivalent for your entity type
- Recent bank statement for the payout account, showing the account name and number matching your Stripe payout settings
- Supplier invoices or proof of product sourcing, matching the products visible on your website
- Fulfillment evidence for recent and disputed orders: shipping labels, tracking numbers with delivery confirmation, or service-delivery screenshots (project files, access grants, completion records)
- Your refund and return policy page (live URL) plus 2–3 examples of refunds actually processed through it, with timestamps
- Customer support contact evidence: working email address, contact form, and/or support channel shown on your website
- Terms of service and privacy policy pages (live URLs), consistent with your actual business practices
- Dispute analysis: a simple sheet listing each dispute — date, amount, transaction ID, outcome, and the evidence submitted for that dispute
- Billing descriptor screenshot from your Dashboard settings, if descriptor confusion was part of the problem
- Clear business description text: one paragraph explaining what you sell, your delivery model, and your typical customer — matching your registered MCC
Our full appeal evidence documentation guide walks through how to organize these into a package reviewers can process in one pass.
FAQ#
Q: The email says my account is "under review" but doesn't say why. What do I do?
Respond completely to any information request in the email or Dashboard, then ask support directly which review category applies — verification/KYC, risk, or disputes. The category determines which additional evidence carries weight. Under review usually means processing continues while payouts may pause, so keep operating normally and avoid changing your pricing, products, or descriptor mid-review, since new signals extend the review.
Q: Can I keep processing payments while restricted?
Usually yes at the "under review" tier, and often partially at the "restricted" tier — but payouts are held, which means every new sale accrues to the frozen balance. Read the email literally about which functions are paused. What you must never do is open a second Stripe account to route around the restriction: linked-account detection treats that as circumventing the review and nearly always results in permanent termination of all associated accounts.
Q: How long does a Stripe review take?
There is no published SLA, and timelines vary by review type. Complete, document-rich responses commonly resolve within a few business days to two weeks; high-risk industry or compliance reviews can take longer, and there is no guarantee of reinstatement in any case. If you have a complete response on file and total silence at the two-week mark, send one follow-up support ticket referencing the original submission.
Q: My account was deactivated, not just restricted. Is it over?
Not automatically, but it's the hardest tier. Processing has ended, and the email will set a timeline for releasing remaining funds — commonly described as a 90–180 day rolling window tied to dispute liability. You can submit one thorough appeal if you have substantive new information, but reversals at this tier are uncommon. Your practical priorities shift: confirm the fund-release schedule in writing, keep your payout bank account valid and accessible, and plan cash flow around the reserve window. See our reinstatement walkthrough for the endgame mechanics.
Q: What's the difference between "under review" and "restricted" in practice?
Tier mechanics. Under review: processing typically continues; respond to the document request and otherwise operate normally. Restricted: payouts pause and processing may be limited — meaning every new sale piles onto the frozen balance, so response urgency is real. Deactivated: operations end and the money timeline begins. Acting on the wrong tier's playbook wastes the leverage you have at the earlier stages.
Q: The email cites "the Stripe Services Agreement, Section [X]." What does that mean?
That's the legal citation, and the cited section usually names the category family Stripe believes applies — restricted business types, prohibited activity, or the general risk-management provisions. Read the cited section carefully before writing your response. If the citation concerns an unregistered restricted business (adult, gambling, forex, and similar), a standard evidence appeal won't fix it; the path is either formal approval for the category or migrating that business line elsewhere.
Q: Funds are held for a stated number of days. Does appealing shorten that?
No — the fund-hold clock is a dispute-liability window, not a punishment, and it runs independently of your appeal. A successful appeal can restore processing and future payouts, but the hold on existing funds generally runs its course. Confirm the end date in writing, keep your payout bank account valid, and read our restricted account response guide for how to handle cash flow during the hold.
Q: Should I reply to the restriction email directly?
The email usually directs you to the Dashboard, and that's where the case actually lives. Use email replies only for clarifying questions if no Dashboard channel exists. All evidence and narrative responses belong in the "Submit information" flow, so the full package sits in one reviewable place rather than scattered across a support inbox.
Preventing the Next Restriction#
Once you're reinstated, the review file stays open in Stripe's systems for a long time. These habits keep it from reopening:
- Keep your dispute rate visibly managed. Track disputes weekly, not monthly. A sudden spike — even from one bad campaign or carrier disruption — is the most common risk trigger. Respond to every dispute with evidence, and refund borderline cases proactively; a refund costs you the margin, a dispute monitoring program costs you far more.
- Keep your website permanently review-ready. Terms of service, refund policy, privacy policy, contact details, and a clear product description should always be live, accurate, and consistent with what you actually do. Reviewers re-check after any restriction, and a stale site re-triggers failure.
- Update KYC the moment reality changes. New beneficial owner, new bank account, new entity address, new product line — update the business profile in the Dashboard promptly so your declared information never drifts from observed reality.
- Keep your billing descriptor recognizable. Use a descriptor customers will connect to your brand, and put the same name on receipts and confirmation emails. Descriptor confusion is a leading, and completely avoidable, dispute generator.
- Match your registered business type to what you sell. If you expand into a new product line or industry, update your MCC-relevant business information — and check whether the new line touches a restricted category before you process for it.
- Respond to every Stripe information request fast and completely. Aged, unanswered requests escalate to restrictions on their own. Treat any "we need additional information" email as a same-week deadline with a one-shot, complete response.
- Run a periodic self-audit. Our account suspension prevention checklist gives you a repeatable quarterly review covering exactly the signals Stripe's systems watch.
Conclusion#
A Stripe restriction email feels like a verdict, but it's almost always a request for proof. Decode the tier from the wording, fix the live account state, assemble a complete and internally consistent evidence package, and submit one thorough response through the Dashboard's "Submit information" flow — that sequence resolves the large majority of reviews, especially the KYC and documentation-driven ones. The exceptions are permanent terminations and restricted-business citations, where your energy shifts from appealing to planning cash flow around the fund-release window and finding compliant processing. If you're staring at a restricted account right now and want help building a response that addresses Stripe's actual review mechanics — or you want to compare notes across how other platforms handle suspensions — UnBanAI's Stripe toolkit structures your appeal around exactly what reviewers look for.
Related Reading#
- Stripe Account Disabled: Step-by-Step Reinstatement (2026) — the full recovery flow for deactivated accounts
- Stripe Account Restricted: Complete Guide — restriction types, holds, and response strategies in depth
- Stripe Account Restricted: What To Do Right Now — the immediate first-48-hours playbook
- Account Suspension Prevention Checklist — the quarterly audit that keeps your account clean
- How Long Does Reinstatement Take? Platform Timeline Overview (2026) — appeal timelines across major platforms
- Appeal Evidence Documentation Guide (2026) — how to build a package reviewers accept in one pass
- UnBanAI for Stripe — our dedicated Stripe recovery resource hub
UnBanAI Team
The UnBanAI editorial team specializes in marketplace and payment-platform account suspensions — Amazon, Stripe, PayPal, Meta, and Google Ads appeals. Our guides are built from patterns across thousands of real appeal cases and are reviewed against each platform's current public policies.
About the team·Success stories·Published August 5, 2026 · Last reviewed November 22, 2026