War-game a merchant risk tier before scoring inputs, review SLAs, and rollback steps harden into what every underwrite will quote.
Tier grids fail when the score invents precision the data never had, when allowlists dual-count the same merchant as high risk and as exempt, when money routes still lack a named false-positive owner, and when ops cannot show who owns the decision after a partial tier misfire. A neat matrix slide is not evidence.
What to freeze first
Write the one sentence for why the tier exists, which product lines and regions it covers, who owns scoring inputs, logging, and rollback, and the abort trigger if false positives or appeal lag past a named threshold. Attach the draft grid, sample underwrite logs, allowlist map, and the measured path from score to restricted payout. If risk, sales, and product disagree on which lines are truly covered, stop and reconcile first.
State the decision you will make if the war game finds nothing new, and the delay criteria if any money path still lacks a named rollback owner or a verified canary cohort.
Hostile chairs
Payments ops should name where scoring invents coverage or hides shared rules across rails. Risk should name where bypasses still leave the queue and become standing exceptions. Sales should name which partner promise breaks first when a legitimate merchant lands in a restrictive tier. Support should show how status language trails the merchant-visible appeal rate. A skeptic seat should pick the claim that looks strongest and is least evidenced by prior tier drills.
Give every seat the same source pack. Secret allowlists for favorite partners only create fake calm. Require a canary cohort with a measured score-and-restrict pass before any money path joins the grid. If the canary still depends on a verbal override, keep the change in hold.
Run and keep a change log
Feed Pingpong the draft grid, canary notes, and open risk list. Early passes steelman the design. Later passes attack from ops, risk, sales, support, and skeptic seats. End with a pass that turns surviving objections into clearer owners, a timed canary, or a hold. Delete invented "we already tier cleanly" claims and dual-counted success rates.
Ask for a month-after narrative: what happens if a marketplace seller is over-tiered, if a co-branded merchant starts failing bot checks, or if an operator widens an allowlist under launch pressure. If those stories outrun the mitigation plan, fix the package before you ship the grid.
Pair with the payments ops lead seat, the payments risk lead seat, a payout hold policy review, and the war-game decisions hub.