Paywalls, Billing & Policies

Products, checkout links, subscriptions, and entitlement keys come from connected billing plugins instead of hard-coded pricing tables.

An organization can create a named policy and say any of these entitlement keys unlock content with that policy.

Editors can attach a content policy to an article, making paywall state part of article metadata instead of a frontend convention.

Audience products can list the products exposed by billing integrations and send logged-in readers into provider checkout.

After purchase, the billing plugin can return the reader's active subscriptions and entitlement keys so access can be linked back to policies.

The platform is being wired toward API-layer body restriction when a request lacks a logged-in reader token with the required entitlement.