Implements Stripe payment flows -- Checkout Sessions, Payment Element, subscription signup, and customer reuse. Use when the user wants to "add checkout", "build a payment flow", "integrate Stripe payments", "add a paywall", or "subscription signup". For conversion analysis, see checkout-conversion.
Analyzes Stripe subscription churn — cancellations, ended subs, voluntary vs involuntary signals, and period-over-period trends. Use when the user mentions "churn", "cancellations", "subs leaving", "retention", or "why are we losing subscribers". Pair with past-due-dunning for payment-driven churn.
Builds subscriber cohort retention and revenue-retention tables grouped by signup month from Stripe data. Use when the user mentions "cohort", "retention curve", "LTV curve", "how long do subscribers stay", or "retention by signup month". For overall churn, see churn-analysis.
Audits Stripe coupons and promotion codes — active discounts, redemptions, and revenue impact. Use when the user mentions "coupons", "promo codes", "discounts", or "promotion usage".
Builds a full profile for a single Stripe customer -- subscriptions, LTV, invoice history, payment health, discounts, and churn risk. Use when the user asks about "this customer", "customer detail", "look up customer", "customer LTV", or gives a customer/email/sub ID. For whole-base segments, see customer-segmentation.
Audits and recommends Stripe Customer Portal configuration — payment method updates, cancellation flow, plan changes. Use when the user mentions "customer portal", "billing portal", "update payment method", or "self-serve subscription management".
Segments the Stripe subscriber base by plan, country, card funding, tenure, or value -- with per-segment MRR and churn. Use when the user mentions "segment customers", "break down by country/plan", "who are our best customers", or "value tiers". For a single customer, see customer-360.
Reviews Stripe disputes, chargebacks, and refunds — volume, reasons, and revenue leakage. Use when the user mentions "disputes", "chargebacks", "refunds", or "fraud losses".
Audits payment-failed and dunning email flows — Stripe built-in emails vs custom webhook emails. Use when the user asks "payment failed email", "dunning emails", "billing emails setup", or "notify users when card fails".
Reconciles Stripe payouts to bank deposits and breaks down balance transactions -- gross, fees, refunds, net. Use when the user mentions "reconciliation", "payout doesn't match bank", "Stripe fees", "balance transactions", or "where did the money go". For balance snapshot only, see payout-balance-report.
Reviews Stripe invoices — paid, open, uncollectible, revenue by period, and subscription billing health. Use when the user asks about "invoices", "billing history", "uncollectible", or "collected revenue" (cash, not MRR).
Computes current MRR, ARR, and revenue breakdown from active Stripe subscriptions — by plan, interval, and currency. Use when the user asks "what is our MRR", "monthly recurring revenue", "ARR", "how much recurring revenue", or "revenue by plan". For full health check, see stripe-health-dashboard. For churn impact…
Investigates pastdue and unpaid Stripe subscriptions — failed invoice attempts, MRR at risk, and dunning/retry status. Use when the user mentions "past due", "unpaid subs", "dunning", "smart retries", "grace period", or "recover failed renewals".
Audits failed Stripe payments — declined charges, PaymentIntents, invoice failures, decline codes, and failure rates. Use when the user asks "how many payments failed", "decline reasons", "card declined", or "payment failure rate".
Reports Stripe balance, available/pending funds, payouts, and cash flow. Use when the user asks "Stripe balance", "payouts", "how much money in Stripe", or "when do we get paid".
Designs Stripe pricing A/B tests, price increases, grandfathering, and elasticity analysis. Use when the user mentions "price test", "raise prices", "pricing experiment", "grandfathering", "price elasticity", or "should we change pricing". For catalog audit, see pricing-products-audit.
Maps Stripe products and prices — plans, intervals, amounts, active vs archived, and which prices appear on live subscriptions. Use when the user asks "what products do we sell", "price IDs", "pricing tiers", "plan structure", or "where does revenue go".
Designs and audits Stripe Radar fraud rules — block prepaid, 3DS, risk levels, lists, and decline patterns. Use when the user mentions "Radar", "fraud rules", "block prepaid", "3D Secure", "high risk payments", or "reduce fraud". For funding mix data, see card-funding-risk.
Projects future MRR, ARR, and revenue run-rate from current Stripe subscription trends, new-sub velocity, and churn. Use when the user asks "revenue forecast", "MRR projection", "where will we be in 6 months", "ARR run-rate", or "growth trajectory". For current MRR only, see mrr-arr-snapshot.
Explains and computes deferred revenue, recognized revenue, and MRR-vs-cash differences from Stripe data for accounting. Use when the user mentions "revenue recognition", "deferred revenue", "recognized revenue", "accrual", "MRR vs cash", or "annual plan accounting". For cash collected, see invoice-revenue-audit.
Creates or updates a stripe-billing-context.md with business model, Stripe account, products/prices, webhook endpoints, email flows, and KPI targets. Use FIRST for a new Stripe account or when other skills need business context. Triggers: "set up stripe context", "billing brief", "document our Stripe setup".
Guides Stripe Connect for marketplaces/platforms -- connected accounts, payouts to sellers, application fees, and onboarding. Use when the user mentions "Connect", "marketplace payments", "pay out to sellers/creators", "connected accounts", "application fee", or "split payments".
Full Stripe billing health check — MRR, subs, churn signals, past due, failures, disputes, and top actions. Use for "Stripe health", "billing review", "weekly revenue check", or executive snapshot. Orchestrates multiple specialist skills.
Reviews Stripe integration code for correctness -- idempotency, error handling, API version pinning, webhook signature checks, and race conditions. Use when the user asks to "review Stripe code", "audit our Stripe integration", or mentions integration bugs, double-charging, or race conditions. For security…