Payout Guard vs the Payouts Page: Your Dashboard Shows You a Number, and It Is Not the Number That Decides

Start with the thing that is missing, because everything else follows from it. Read the Shopify Payments Terms of Service looking for the chargeback rate that triggers a reserve, and you will not find one. Not a percentage, not a ratio, not a count. What the document says instead is that Shopify may act “if we determine, in our sole discretion, that there is an elevated risk of chargebacks or disputes,” and that it may suspend or terminate an account “at any time, for any reason, including… significant credit or fraud risk.”

That is not a gotcha and it is not unusual — every acquirer writes its risk terms that way, because a published number is a number that gets gamed. But it has a consequence merchants rarely think through. The decision that can hold your money is made against a judgment, not a threshold. Meanwhile the Payments dashboard in your admin shows you a dispute count and a payout schedule: two facts about right now, presented without slope, without context, and without any statement of what would be too many.

So this comparison is not our app against a competing app. It is our app against the screen you already check, and the honest question is narrow: given that no one will tell you the threshold, what is actually worth measuring? Payout Guard is our answer, and by the end of this you will know exactly what it adds, which of its own numbers are borrowed rather than authoritative, and the substantial list of things it cannot see at all.

What the Terms Actually Say

Three provisions do the work, and they are worth reading in the original rather than in summary.

On reserves, the terms describe funds held to cover “chargebacks, refunds, disputes, or other payment obligations,” and reserve to Shopify the right to set the terms of any reserve account — which “may require that a certain amount (including the full amount) of the funds received for a Transaction are held for a period of time.” Merchants also acknowledge they are “not entitled to any interest or other compensation associated with the funds held in the Reserve Account.” The full amount, for a period Shopify sets. That is the exposure in one clause.

On disputes, there is a provision that surprises people: Shopify “may enroll you in automated dispute resolution programs… if we determine, in our sole discretion, that there is an elevated risk of chargebacks or disputes,” and while enrolled, “we will determine how disputes are handled on your behalf, and you will not be able to contest them.” The right to fight a chargeback is not unconditional.

On termination, the account may be suspended “at any time, for any reason,” with risk named explicitly among the reasons.

The One Published Number, and Why It Is Not Yours

There is a hard, numeric, published threshold in the payments chain. It belongs to Visa, not to Shopify, and the most common mistake merchants make is assuming it applies to the number on their dashboard. It does not, and the difference is not a technicality.

Visa's Acquirer Monitoring Program — VAMP — consolidated Visa's older fraud and dispute monitoring programs into a single global program. Its core metric, quoted from Visa's own program overview, is:

“VAMP Ratio = Count of [Fraud (TC40) + Disputes (TC15)] ÷ Count of Settled Transactions (TC05)”

Read that carefully against what your dashboard shows you. Three differences, each one enough on its own:

• The numerator adds fraud reports to disputes. A TC40 is a fraud report, not a chargeback. Your dispute count is one of two inputs.
• The denominator is settled card-not-present transactions, and Visa describes the metric as covering “card-not-present VisaNet transactions (domestic and cross-border)” — Visa only. Your dashboard's rate spans every card brand you accept.
• There is a floor, and it is high. For the AP, Canada, EU and U.S. regions the Excessive Merchant thresholds require a monthly count of fraud and disputes of at least 1,500. Below that count, a merchant is not identified by the program at all.

The ratio itself did tighten this year. Visa's overview lists the Excessive Merchant threshold for AP, Canada, EU and the U.S. at ≥220bps, with a footnote stating that it was “reduced to >=150bps in AP, Canada, EU, and U.S. regions on 1 April 2026.” Separately, an acquirer's whole portfolio is identified as “Above Standard” at ≥50bps and “Excessive” at ≥70bps. The program also excludes disputes resolved through pre-dispute solutions and certain fraud qualified under Compelling Evidence 3.0 — more reasons the VAMP ratio and your dispute rate are not the same quantity.

So What Is Left Worth Measuring?

If the thresholds are either undisclosed or measuring something else, the useful question changes shape. It stops being “am I over the line?” and becomes “which way am I moving, and how fast?” That is a question your dashboard genuinely does not answer, and it is the one thing Payout Guard is built to answer.

The engine takes your dispute and charge counts bucketed by period, computes the rate for each period, and fits a least-squares slope across them. From the slope and the current rate it derives a single figure it calls periods to action: at the rate you are currently trending, how many periods until you reach the line. That is arithmetic, not prophecy, and it is only meaningful because it is the arithmetic nobody is doing for you. A store sitting at a comfortable rate with a steep upward slope is in a materially different position from a store sitting at the same rate flat, and both look identical on the payouts page.

Around that sit three reference lines, and here is the honest accounting of where each one comes from: an early-warning band at roughly 0.65%, an action line at roughly 1%, and the Visa figure at 1.5%. Only the third is published, and as established above it measures a different ratio. The first two are our judgment about where attention is warranted. They are in the product because a slope with no reference points is hard to read, not because anybody ratified them.

The Detail That Changes How You Think About Disputes

One mechanical fact deserves its own section, because merchants routinely plan around the opposite assumption. The engine's own note states it plainly:

“Shopify's chargeback rate counts disputes FILED, not won — winning a dispute does NOT remove it from the rate.”

If you have been treating dispute wins as risk reduction, they are not. They recover the money and they are absolutely worth pursuing for that reason. They do not un-file the dispute. Which means the levers that actually move the rate all sit upstream of the dispute: clearer product descriptions, honest delivery estimates, a recognisable billing descriptor, responsive support before a customer gives up and calls their bank. Every one of those is a merchandising decision, not a payments one — and none of them is something an app can do for you.

What Payout Guard Cannot See

This is the section that decides whether a tool is worth trusting, so here it is with the receipts. Payout Guard requests exactly four scopes:

That last one is the important one. Payout Guard has no visibility into Shopify's own risk assessment, no channel into it, and no ability to influence it. It reads two payments endpoints and does arithmetic. It is the same scope discipline every app on the shelf follows, and it costs exactly what that article says it costs: the app cannot correlate disputes to individual orders, because it cannot see orders.

Which One You Should Actually Be Looking At

Both, for different questions, and the split is clean.

If you take one thing from this: the reason to watch the trend is not that a specific number is coming for you. It is that the people who decide are working from a judgment you cannot read, and the only honest preparation is to know which way you are moving before somebody else has to tell you. The dashboard is the record. The slope is the warning. Neither is the verdict, and nothing on this page — ours included — can tell you where the verdict falls.