Recurring payments enforced at the blockchain consensus layer — no payment processor, no webhook infrastructure, no failed-charge handling. The protocol collects, or the subscription lapses.
Subscriptions in Shamwari are stored as first-class account entities. The protocol processes billing automatically at the configured block height interval.
Billing frequency configured in blocks — daily (~7200 blocks), weekly, monthly, or any custom interval. Exact and deterministic — no timezone issues, no ambiguous billing dates.
Services can accept payment in chain coin, ShamwariPay currency, or Totem digital assets. The same subscription infrastructure supports any monetary instrument the protocol supports.
Services can restrict subscriptions to specific account types — BUSINESS, DEVELOPER, or PERSONAL only. Enforced at consensus — the protocol rejects subscriptions from non-permitted account types.
AccountType.AI agents can subscribe to services within their configured permission matrix. Subscription payments are included in the rolling spend window calculation for limit enforcement.
If funds are unavailable at renewal, the subscription lapses immediately. No retry logic, no dunning management, no failed payment handler. Protocol state reflects economic reality instantly.
CANCEL_SUBSCRIPTION is a consensus transaction — effective at the next block. No notice period ambiguity. Subscription entity deleted from state immediately.
Create subscription services that bill automatically — SaaS, media, data feeds, or any recurring revenue model.