What problem does it solve? Payment and billing flows often trust client-side amounts, UI discounts, or asynchronous callbacks, letting testers report false positives or miss real ledger inconsistencies. This Skill enforces an evidence-gated method to verify that amounts, inventory, coupons, callbacks, refunds, and subscription states are authoritative only at the server-side ledger. ## Core Features & Use Cases - Engagement Gating: Requires recorded authorization, locked scope, and host/identity baselines before any probe runs, and stops immediately on third-party assets or production side effects. - Server-Authoritative Oracles: Treats only persistent ledger, entitlement, and inventory results that violate defined invariants as valid findings; frontend discounts, payment failure pages, and async delays are rejected. - Controlled Routing: Hands signed-callback cases to webhook-signature testing and concurrency cases to race-condition testing, keeping each probe single-variable and low-frequency. - Use Case: During an authorized test window, compare normal and boundary inputs on your own sandbox orders, read back results from the payment provider sandbox and backend ledger, and capture pre/post state with rollback evidence. ## Quick Start Use $hunt-payment-workflow to plan an evidence-gated, authorized validation path for my test payment orders.
