Post Subscriptions and Buyer Renewal State

Where you see this in the app

Open Settings → Post subscriptions to manage memberships you have joined. This is separate from your own GetPaidX Pro plan and the creator dashboard’s subscriber reports.

The page lists current recurring memberships. One-time post purchases are separate. A membership may include a post’s live sessions when the host uses membership-based admission; joining still depends on the session’s permissions, state and capacity.

The membership page opens with Other settings collapsed and the floating assistant compact, so the controls are immediately visible. You can open either when needed.

Price and billing period

Known membership terms show their own amount, currency and cadence. These can differ from today’s public post price. If only the original checkout is known, it is explicitly labeled Original checkout. A last-payment or receipt fallback does not invent current billing terms.

Trials are labeled Trial, with their end date when known. An active trial is not a claim that a payment has been collected.

Check current status

Use Check status to verify the membership through its original seller account and refresh its cancellation, billing period and known price. This action does not start another checkout or change billing.

A scheduled cancellation still has a usable status check. If an external change has resumed renewal, checking status restores the appropriate cancellation action. A failed check preserves the last known state and explains whether to retry or contact support.

Open a post or cancel a membership

The cancellation dialog explains the effect before confirmation. Existing charges are not refunded by these controls. Ending a membership removes it from the current-membership list; the empty state says there are no current memberships.

Programmatic access

The buyer-owned GET /api/users/me/post-subscriptions/{subscriptionId} uses billing:read. Add refresh=true for current provider verification. Checkout recovery supplies membershipId, which identifies this resource. The read also supports an ended membership whose ID is known.

The same operation is available through generic MCP/WebMCP API calls. OAuth MCP clients also need the existing posts:read catalog permission. Cancellation remains a separate DELETE operation under billing:manage with explicit mutation confirmation in MCP/WebMCP.