Stripe Account Health

Stripe runs automated risk systems that continuously evaluate your account across several dimensions. These are not manual reviews by a person reading your dashboard — they are algorithmic assessments that can trigger actions on your account with no warning and no human in the loop.

The primary signals Stripe evaluates include your dispute rate (chargebacks as a percentage of total transactions), your refund rate, the velocity and pattern of your transaction volume, the categories you sell in, and compliance-related keyword flags in your product descriptions, business name, or website.

What makes this dangerous for merchants is the asymmetry of information. Stripe can see all of these signals in real time. You, as a merchant, see a dashboard that shows payment volume and maybe a few disputes. There is no native "account health" score in Stripe. No warning light. No countdown timer showing you how close you are to a freeze. You are flying blind unless you build your own monitoring — or use something purpose-built for it.

Stripe publishes a dispute rate threshold of 0.75%. This is measured as the number of disputes divided by the number of transactions in a given period. Once your account exceeds this rate, you are in the danger zone — and Stripe's automated systems begin evaluating your account for potential holds, reserves, or termination.

The math is straightforward but the implications catch people off guard. If you process 400 transactions in a month and receive 3 disputes, your dispute rate is 0.75% — right at the threshold. Four disputes and you are over. For a business doing $50K/month in revenue, three chargebacks is all it takes.

What most merchants don't realize: dispute rate is calculated on a rolling basis, not monthly. Stripe uses a trailing window. This means a burst of disputes in a short period can spike your rate even if your monthly average looks fine. A bad week can trigger what a bad month would not.

Crossing the 0.75% threshold does not automatically mean an instant freeze. Stripe's response is tiered, but the tiers are not transparent. Based on patterns across hundreds of merchant cases, here is what typically happens:

Stage 1 — Warning email. Stripe sends a notification that your dispute rate is elevated. This is your best window to act. Many merchants ignore this email or assume it is routine. It is not.

Stage 2 — Reserve or payout hold. Stripe places a percentage of your incoming payments into a reserve (usually 5-10%) or delays payouts. Your business can still process charges, but cash flow takes a hit. This is Stripe protecting themselves against future chargebacks on your transactions.

Stage 3 — Full freeze. Processing is suspended. Payouts are held. New charges are blocked. You are now in crisis mode. At this stage, your options narrow significantly and recovery depends on the quality of your appeal.

Stage 4 — Termination and potential MATCH listing. If your dispute rate stays elevated or Stripe determines the risk is too high, they terminate your account and may report you to the MATCH list — a payment processing blacklist that follows you for five years.

Refunds are a double-edged signal. On one hand, proactive refunds prevent disputes — every refund you issue is a potential chargeback that never gets filed. On the other hand, a high refund rate tells Stripe that something is wrong with your product, your marketing, or your customer experience.

There is no published refund rate threshold from Stripe the way there is for disputes. But from merchant patterns, refund rates consistently above 10-15% tend to draw increased scrutiny, especially when combined with other risk signals. A merchant running a 12% refund rate and a 0.5% dispute rate looks very different to Stripe's systems than a merchant with the same dispute rate and a 2% refund rate.

The strategic play is to use refunds as a tool to keep your dispute rate down — but to do it selectively. Refunding a $15 product to prevent a chargeback saves you $30 in dispute fees and protects your rate. But refunding everything defensively drives your refund rate up and signals a product problem. The math matters on a per-transaction basis.

This is the trigger that catches legitimate businesses off guard the most. You launch a successful product, go viral on social media, or hit a seasonal peak — and Stripe freezes your account in the middle of it. It feels punitive. It is not personal. It is Stripe's automated systems interpreting a sudden change in pattern as a potential fraud signal.

Stripe builds a baseline profile of your business: typical transaction volume, average transaction size, customer geography, and processing patterns. When your actual activity deviates significantly from this baseline — especially a sudden spike — the risk systems flag it. A business that normally processes $20K/month suddenly processing $80K in a week looks, to an algorithm, identical to a compromised account being drained.

The fix is proactive communication. Before a product launch, Black Friday rush, or any expected volume increase, email Stripe support and tell them what to expect. Include specifics: expected volume, date range, and the reason for the increase. This does not guarantee immunity, but it creates a record that reduces the chance of an automated flag.

PayCanary's monitoring detects when your volume is trending above your baseline and generates a pre-written notification you can send to Stripe before their systems flag you. Think of it as an early warning system — not for disputes, but for the volume spike that triggers the review.

The MATCH list (Mastercard Alert to Control High-Risk Merchants) is the nuclear option. If Stripe terminates your account due to excessive disputes, fraud, or certain compliance violations, they can report you to MATCH. Once you are on it, no major payment processor — not Stripe, not Square, not Adyen, not anyone using Visa or Mastercard rails — will onboard you for five years.

Not every Stripe termination results in MATCH listing. The most common reason for MATCH placement is excessive chargebacks (reason code 04 in the MATCH system). If your dispute rate has been persistently high and Stripe terminates your account specifically for chargeback levels, the probability of MATCH listing is significant.

PayCanary's MATCH List Proximity Alert shows you exactly how many disputes separate you from the zone where termination and MATCH listing become real possibilities. It is the metric most merchants never think about until the email arrives.

PayCanary's risk score weights all of the signals described above into a single deterministic score: (Dispute Rate x 40) + (Refund Rate x 25) + (Volume Spike x 20) + (Keyword Flags x 15). No AI, no black box. These are the same risk factors Stripe evaluates — we just make them visible and trackable.

On paid plans, monitoring runs continuously — webhooks process disputes and refunds in real time, and a 15-minute backstop cycle recalculates your full risk score, checks your dispute rate trajectory against the 0.75% threshold, monitors for volume spikes against your baseline, and evaluates whether any combination of signals has moved you into a higher risk band.

When a threshold is approaching, you get an alert — not after you have crossed it, but while you still have time to act. That is the difference between "your account has been frozen" and "your dispute rate is trending toward 0.6%, here are three things you can do right now." One of those messages costs you weeks of downtime. The other costs you five minutes of attention.

Start with the free Stripe health check to see where your account stands right now. No Stripe connection required — enter your metrics manually and get your risk score in 30 seconds.