Get Paid Without the Payment Headaches
Stripe subscriptions done right. No revenue leaks from failed payments.
TL;DR
The SaaS Monetization Kit handles everything between "sign up" and "revenue in bank":
- Tiered pricing with Stripe (Free, Pro, Enterprise)
- Subscription lifecycle (trials, upgrades, cancellations)
- Usage-based billing for API metering
- Failed payment recovery (no more silent revenue loss)
2 agents. 1 command. 1 skill. 1 MCP integration. Zero excuses for delaying monetization.
What's Inside
2 Agents
@payment-integration- Connect payment processors@stripe-pro- Stripe expert (products, webhooks, billing)
1 Command
/add-authentication-system- Secure auth before payments
1 Skill
better-auth- OAuth, JWT, session management
1 MCP
stripe- Direct Stripe API access from Claude
What You Actually Build With This
1. Launch Your First Pricing Tier in 20 Minutes
You've shipped your MVP. Now you need money. Free tier exists. Pro tier at $29/month doesn't.
@stripe-pro Build tiered pricing: Free (no payment), Pro ($29/mo), Enterprise (custom). Create checkout flow with test cards.
Result: Working Stripe checkout. Test mode configured. Ready to flip to production and charge real cards.
2. Handle Subscription Lifecycle Without Spreadsheets
Customers upgrade from Free to Pro. Some cancel. Some forget to cancel after trial. You need automation, not manual tracking.
@stripe-pro Full subscription lifecycle: 14-day trial, auto-charge, upgrade/downgrade with proration, webhook handlers for payment events.
Result: Subscription state machine. Webhooks for success/failure. Self-service customer portal for upgrades and cancellations.
3. Bill Per API Call (Usage-Based Pricing)
Your API charges per 1000 requests. Customers pay only for what they use. You need metered billing that invoices monthly.
@stripe-pro Usage-based billing with Stripe meters. Track API requests per customer. Bill monthly with $0.01 per 100 requests overage.
Result: Meter event streaming. Monthly invoice generation. Customer-facing usage dashboard.
4. Recover Failed Payments (Stop Losing $5K/Month)
2% of payments fail. Expired cards. Insufficient funds. Without retries, you lose revenue silently.
@stripe-pro Payment failure recovery: 3 retry attempts over 5 days, dunning emails, customer portal for card updates, auto-retry after update.
Result: Exponential backoff retry logic. Email reminders after each failure. Payment method update flow. Metrics dashboard tracking recovery rate.
5. Auto-Unlock Features After Payment
Customer pays. You manually send license key via email. Hours later. This doesn't scale.
@payment-integration Auto-grant GitHub repo access, Discord role, and email license key on payment. Revoke on cancellation.
Result: Webhook handlers for benefit grant/revoke. GitHub/Discord/email integrations. Zero manual work.
Why This Kit Exists
Payment Integration Is Not Your Core Product
You're building a SaaS, not a billing platform. Stripe docs are 400 pages. This kit gives you working code in 20 minutes.
Failed Payments Cost Real Money
2% payment failure rate on $20K MRR = $400/month lost. Automated retry + dunning recovers 40-60% of that. This kit pays for itself.
Revenue From Day One
No more "we'll add payments later." Install kit. Build checkout. Ship. Get paid. Actually validate if people will pay for your product.
Install & Start Building
Install the SaaS Monetization Kit:
Installs 2 agents, 1 command, 1 skill, 1 MCP integration. Ready in 30 seconds.
What Happens Next
- 1. Run
/add-authentication-systemto secure your app before payments - 2. Use
@stripe-proto set up products, prices, and checkout flow - 3. Test with Stripe test cards (4242... for success, 4000... for failure scenarios)
- 4. Implement webhook handlers for subscription events (payment success/failure)
- 5. Flip to production mode. Start charging real customers.
Pro Tips From People Who've Shipped This
Test thoroughly in Stripe test mode.
Use test cards: 4242... always succeeds, 4000... always fails. Test every edge case before production.
Webhook handlers must be idempotent.
Stripe retries webhooks. Process events by idempotency_key to avoid double-charging or duplicate benefit grants.
Store metadata in Stripe subscriptions.
Use subscription.metadata for team_id, plan_version, billing_cycle_start. Makes debugging payment issues 10x faster.
Monitor payment failures before customers complain.
Set up alerts for: payment failures, failed webhooks, unusual usage spikes. Fix issues before they cost you revenue.
Revenue Waiting on You
Stop delaying monetization. Install the kit. Ship payments. Get paid.
Part of Vibery Kits - Curated template stacks for Claude Code