Worked example — not a reported incidentpublished 2026-09-20

A subscription renews at a higher price than you agreed to

1. As reported

A worked example, not a reported incident: a service you subscribed to at one price renews at a higher one, and the first you hear of it is the statement. Shield's sandbox ships this exact scenario so anyone can run it.

2. The policy that would have held it

Subscription renewals: Ask me above $25
Price changes: Ask me on any increase

3. Run it

The public sandbox is local, deterministic and needs no account. Its records are labelled sandbox_fixture; they teach the verdict, they are not production signatures.

npx @decionis/shield-demo --scenario subscription-price-increase

Verdict

ASK

Changed commercial terms need approval: the renewal amount is higher than the amount the permission was granted for.

Sandbox scenarios and what each one teaches: docs/developers/sandbox.md.

4. What Shield could not have done

Shield cannot cancel the subscription or reverse a charge; the merchant or your payment provider does that.
Shield holds a renewal only when it passes through a supported app, agent or paired browser. A charge Shield never saw is not stopped by a rule.
The sandbox returns a labelled fixture, not a production signature; the real record is the Dispute Passport the app issues.