Stripe Billing Operations

Contents: Ideal State · Intent Routing · Data & Config · Tool contract · Gotchas · Examples

Answers and acts on Stripe billing questions: promotion codes and coupons, products and prices, subscriptions and subscriber counts, MRR and revenue, customers, payments, invoices, refunds and payment links, across one main account and any number of additional ones. With more than one Stripe account, using the wrong key returns wrong numbers silently, so every call names the account's key.

Ideal State

• Every figure comes from the account the user meant, through that account's env var, with keys loaded from ~/.claude/.env and never printed or hardcoded; a missing Config.md or STRIPE_SDK_DIR stops the run with a pointer to Setup.md instead of a guess.
• Counts and revenue cover every page of the list they come from, and historical views keep canceled and churned subscriptions and attribute every row to a product.
• No write reaches Stripe without the user's explicit approval, and every write reports the resulting object back.

Intent Routing

Intent	Trigger	File
ListProducts	"products", "what products", "list products"	Intents/ListProducts.md
Subscriptions	"subscriptions", "subscribers", "how many subscribers"	Intents/Subscriptions.md
Revenue	"revenue", "MRR", "how much", "earnings", "income"	Intents/Revenue.md
Customers	"customers", "customer list", "who subscribes"	Intents/Customers.md
Payments	"payments", "recent payments", "charges"	Intents/Payments.md
Manage	"promotion codes", "promo code", "find a coupon", "create product", "create price", "change the price", "cancel", "refund", "coupon", "invoice", "payment link"	Intents/Manage.md

File	Read when
Setup.md	first-time setup: Config.md, STRIPE_SDK_DIR, the per-account key env vars, and the check that it works