subscriptions

Subscriptions is pull-payment plumbing: a wallet grants a bounded permission once, and payments then happen on schedule without a signature per charge. Every bound (how much, how often, until when) is enforced by the program, so the thing being granted is a cap, never a blank check.

The cast, in the order you will meet them:

• a user establishes a subscription authority, the account that makes bounded pulls possible for their wallet at all;
• a merchant publishes plans (price, period, terms);
• a subscriber subscribes to a plan, which creates a delegation capped by that plan’s terms;
• a puller (the merchant’s collector) transfers against the subscription each period, within the cap;
• a delegator/delegatee pair can skip plans entirely and set up a direct, bounded delegation.

Every page in this guide is an executed test, not prose about one: the When lines are the steps, each Then is a claim the run verified (the ✓ is real), the sequence diagram shows who called whom, and the authority graph shows who signed for what, including the program signing through its PDA. The source link on each page points at the exact test that produced it. If the program’s behavior changes, these pages fail before they lie.