catalog / commerce

Subscription Billing

Recurring charges, plan changes and the proration nobody gets right first time.

19 capabilities 2 sections reference specification

Build against it

# give your agent the catalog — no account, no install
claude mcp add provespec -- npx -y provespec-mcp

# then, from any agent session
spec_get(slug: "subscription-billing")                → the capability tree
spec_checklist(slug: "subscription-billing")          → the questions to answer
spec_grade(slug: "subscription-billing", grades: [...])  → parity % + the gap list

# or just fetch it
curl https://provespec.com/catalog/subscription-billing/spec.json

Grade every capability below as yes · partial · no · na, with a file reference as evidence. Whatever you leave ungraded counts as missing — the gap list is the work queue.

Or just paste this to your agent

Use the ProveSpec MCP server. Fetch the "subscription-billing" spec with
spec_get, then walk spec_checklist and grade this repository against it —
one verdict per capability, each with a file reference as the note.
Call spec_grade with the results and give me the gap list as the plan.

If the server is not registered, add it first:
  claude mcp add provespec -- npx -y provespec-mcp

The specification

AI 16

Plans
  • Plans with interval, price and currency monthly, yearly
  • Tiered, per-seat and usage-based pricing
  • Trial period with or without a card
Lifecycle
  • Subscribe, pause, resume, cancel cancel at period end or immediately
  • Upgrade and downgrade mid-period
  • Proration on plan change credit for unused time, stated formula
Billing
  • Invoice generated per period with line items
  • Taxes applied by customer location VAT/GST registration handled
  • Credits, refunds and partial refunds
Dunning
  • Retry schedule on failed payment bounded, with backoff
  • Customer notified before and after each attempt
  • Grace period then downgrade or suspension stated, not silent
Metering
  • Usage recorded and aggregated per period
  • Overage handling and caps
Records
  • Immutable invoice history never rewritten after issue
  • Revenue recognised per period, not per payment

UI 3

Portal
  • Customer sees plan, next charge and payment method
  • Self-service upgrade, downgrade and cancel
  • Invoice download as PDF
Download spec.json All 85 specs