The email usually arrives without warning: your Stripe account is "under review," payouts are paused, and a reserve may be applied to future processing. For an online store that depends on daily cash flow, a risk review feels like an account freeze — even when the account is technically still active. The confusion is often worse than the hold itself, because Stripe rarely tells you which specific signal caused the flag.
A risk review is not a punishment. It is Stripe's underwriting team re-checking whether your business still matches the profile they approved, driven by automated signals from your processing history. Merchants who understand what reviewers look for can usually resolve a review in days rather than weeks. This article explains the four triggers that flag most accounts, the response sequence that works in practice, and how reserves function once they are applied.
What a Stripe Risk Review Actually Is
Stripe operates as a payment facilitator: it aggregates millions of merchants under its own master merchant accounts with acquiring banks. Because Stripe carries the financial liability for chargebacks and fraud losses across that portfolio, it continuously scores every connected account for risk. When the internal score crosses a threshold, the account is routed to a human reviewer who decides whether to ask for documents, hold funds, or close the account.
During a review, Stripe may restrict payouts, request verification documents, apply a reserve, or — in serious cases — terminate the account and place the business on the MATCH list shared across the acquiring industry. The review process itself is standard across all payment aggregators; what varies is how quickly you can satisfy the reviewer's questions. Speed and completeness of your response matter more than the trigger that started it.
The Four Triggers That Flag Most Accounts
While Stripe's exact risk model is proprietary, the signals below account for the large majority of reviews merchants report. Each one is visible in your own data before it becomes a problem.
1. Sudden Volume Spikes
If your store normally processes $8,000 a month and suddenly runs $40,000 in a week — because of a product launch, a viral post, or a wholesale order — the risk model treats that pattern as a potential bust-out. Fraudsters commonly run a burst of stolen-card transactions and disappear before the chargebacks arrive, so legitimate growth can look identical to fraud in the raw data. You can pre-empt this trigger: contact support before a planned spike with your expected volume, average order value, and fulfillment plan in writing.
2. Category Risk
Some business categories carry structurally higher dispute rates or regulatory exposure: supplements, digital services, subscriptions with free trials, travel, ticketing, and anything adjacent to restricted product lists. If your catalog drifts into a riskier category than the one you were underwritten for — for example, adding ingestible wellness products to a skincare store — a review is almost automatic. The merchant category code assigned at onboarding defines your baseline; selling meaningfully outside it is a classic trigger.
3. Chargeback Ratio
Card networks monitor the ratio of chargebacks to transactions. Crossing roughly 0.9% historically placed a merchant into Visa's dispute monitoring program, and about 1% into Mastercard's equivalent — these thresholds change, so check the current network program rules. Stripe's internal tripwires sit below the network thresholds, because Stripe pays penalties when its portfolio breaches them. A single bad month with a handful of chargebacks on low volume can flag an account that has been clean for years. For prevention tactics, see our guide on reducing chargebacks in online stores.
4. Business-Information Mismatch
Reviewers reconcile your application data against what they can independently verify: does the website match the stated products, does the legal entity match the bank account, does the domain registration match the business address? Common mismatches include a personal bank account on a business application, a website with no refund policy or contact page, a domain registered last week for a company claiming five years of history, or product photos that clearly belong to a different brand. Each inconsistency reads as a potential front operation.
The Response Sequence When Your Account Gets Flagged
Once a review starts, the order in which you act matters. The sequence below reflects what resolves reviews fastest in practice.
- Read the request carefully and note the deadline. Stripe typically gives a fixed window — often a few business days — to submit documents. Missing the deadline converts a review into a hard restriction.
- Gather evidence before you reply. Standard requests include government ID, business registration, supplier invoices, fulfillment proof for recent orders (tracking numbers showing delivery), and bank statements. Prepare one complete packet rather than trickling documents in.
- Write a short factual summary of your business. Two paragraphs: what you sell, who your customers are, your average order value, monthly volume, and how you fulfill orders. Attach it to the submission.
- Explain the anomaly directly. If the trigger was a volume spike, state the cause — a launch, a wholesale deal, seasonality — and show evidence such as ad campaign data or a signed purchase order. Reviewers close cases faster when your explanation matches the data they already see.
- Respond through the dashboard channel requested, then open a support ticket as a record. Keep every communication in writing and save the ticket IDs.
- Keep selling on a backup channel while you wait. A review can take days or weeks. Merchants with a secondary processor or a non-card rail keep revenue flowing; our article on durable payment channel structures explains how to set that up before you need it.
What not to do: do not open a second Stripe account for the same business, do not route volume through someone else's account, and do not send angry messages to the review team. Each of these converts a routine review into a termination signal.
Reserves: Rolling, Fixed, and Full Payout Pauses
A reserve is Stripe's way of collateralizing your chargeback exposure. It is not a fee — the money remains yours — but it is cash you cannot use while held. Three structures are common in practice:
| Reserve type | How it works | Typical trigger | Release pattern |
|---|---|---|---|
| Rolling reserve | A percentage of each payout (often 5–30%) is held for a fixed window, commonly 90–180 days | Elevated dispute ratio or new category risk | Funds release continuously as each holding window passes |
| Fixed (capped) reserve | A percentage is withheld until a set currency amount accumulates, then withholding stops | Moderate risk with predictable volume | Held until the account closes or a later review lifts it |
| Full payout pause | All payouts held pending document review | Verification failure or a severe trigger | Releases once the review closes successfully |
Reserve terms are set case by case and the percentages vary widely. Check the official Stripe documentation and your own dashboard notice for current terms rather than relying on forum figures. If a reserve is applied, you can sometimes negotiate it down by supplying additional fulfillment evidence or demonstrating a longer clean processing history.
How to Lower Your Review Risk Over Time
Reviews are a fact of life for aggregated payment accounts, but you can make your account a boring one. The merchants who get flagged least tend to share the same habits:
- Keep your catalog aligned with the category you were approved for, and notify your processor before adding a new product line.
- Warm up volume increases gradually, and pre-notify support before predictable spikes such as holiday sales.
- Hold your dispute ratio well below 0.5% so a single bad week cannot trip internal thresholds.
- Maintain a complete public website: refund policy, shipping terms, contact page, and a business address matching your registration.
- Use a business bank account in the exact legal entity name on the application.
- Export your customer and transaction data regularly so a sudden restriction cannot lock away your records.
It also makes sense to treat any single payment channel as a single point of failure. Diversifying across processors — and across payment rails — means a review at one provider is an inconvenience rather than an existential event.
Conclusion
A Stripe risk review is triggered by data, not by animus: volume spikes, category drift, chargeback ratio, and mismatched business information account for most flags. The response that works is fast, complete, documented, and boring — one evidence packet, one clear explanation, no workarounds. Over the long run, keeping dispute ratios low and business information consistent is what keeps your account off the review queue. And if card-network risk is a recurring feature of your business model, it may be worth adding a payment rail that operates outside the card system entirely. USDT payments settle on-chain with no chargebacks and no rolling reserves; the USDTGate documentation covers integration options, and you can create an account to test the flow alongside your existing setup.