payments
This skill walks you through Stripe configuration for subscription-based SaaS, from initial setup through production launch. Learn to structure pricing tiers, implement webhook handlers for subscription events, configure the Customer Portal, and recover failed payments through dunning sequences. Covers tax compliance, testing checklists, and the business decisions that prevent billing bugs from eroding customer trust.
Payments helps you set up Stripe subscription billing, handle failed charges, and manage tax compliance for bootstrapped SaaS.
AI-generated summary based on this skill's SKILL.md
Install
whawkinsiv/solo-founder-skills/payments
git clone https://github.com/whawkinsiv/solo-founder-skills
cp -r solo-founder-skills/skills/payments ~/.claude/skills/paymentsnpx skillfed install whawkinsiv/solo-founder-skills/paymentsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I set up subscriptions with Stripe?
The payments skill guides you through Stripe subscription setup for SaaS products. Start by creating Products and Prices in your Stripe Dashboard, then implement server-side subscription creation using the Stripe API. Configure your webhook endpoint to listen for subscription lifecycle events (customer.subscription.created, customer.subscription.updated, invoice.payment_succeeded). Use the Customer Portal to let users manage their own subscriptions. The skill covers environment variable management for API keys, testing in test mode before going live, and structuring pricing tiers to match your business model.
How to set up Stripe for SaaS?
The payments skill provides a complete roadmap for Stripe SaaS implementation. Begin with account setup and API key configuration, then design your pricing tiers and create Products in Stripe. Implement Checkout or build a custom form to collect payment details. Set up webhooks to handle subscription events reliably—this is critical for syncing billing state with your database. Configure the Customer Portal so users can update payment methods and manage subscriptions themselves. Add tax collection settings for compliance, then run through the testing checklist before switching to live mode.
How do I handle failed payments and set up dunning?
The payments skill teaches you to recover revenue from failed payments using Stripe's retry logic and dunning workflows. Enable Stripe's automatic retry schedule to attempt failed charges multiple times. Implement webhook handlers for invoice.payment_failed events to trigger your own dunning email sequence—notify customers early, offer payment method updates, and escalate if needed. Use the Customer Portal to let customers fix payment issues themselves. The skill covers graceful error handling so failed payments don't break the user experience, and shows how to balance aggressive recovery with customer retention.
What's the right way to set up Stripe webhooks?
The payments skill emphasizes webhook reliability for subscription lifecycle management. Create a dedicated endpoint that verifies Stripe's signature using your webhook secret—never trust unsigned requests. Listen for key events: customer.subscription.created, customer.subscription.updated, customer.subscription.deleted, invoice.payment_succeeded, and invoice.payment_failed. Store events in your database and process them asynchronously to avoid timeout issues. Test your webhook handler in test mode first, then register it in your Stripe Dashboard. The skill covers idempotency so duplicate webhook deliveries don't cause bugs.
How do I configure tax collection and ensure compliance?
The payments skill covers Stripe tax compliance for SaaS billing. Enable Tax in your Stripe account and configure your business location and tax IDs. Use Stripe Tax API calls when creating checkout sessions or calculating invoice totals—Stripe will determine applicable sales tax or VAT based on customer location. The skill explains nexus rules, when to collect tax, and how to handle tax-exempt customers. It also covers documentation and reporting requirements so you stay compliant across jurisdictions without manual calculation errors.
What testing should I do before going live?
The payments skill includes a testing checklist to prevent trust-breaking billing bugs. Test subscription creation, upgrades, downgrades, and cancellations in test mode using Stripe's test card numbers. Verify webhook delivery and idempotency—simulate failed webhooks and duplicate events. Test failed payment scenarios and confirm your dunning sequence triggers correctly. Validate tax calculation for different customer locations. Test the Customer Portal and payment method updates. Check proration logic for mid-cycle changes. Only after passing these checks should you switch API keys to live mode and monitor production closely for the first billing cycle.
SKILL.md
rendered from the published skill — quoted content, verbatim
Payments & Billing Operations
Billing is 20% code and 80% configuration and business decisions. This skill helps you set up Stripe correctly, handle the edge cases, and avoid the mistakes that lose customer trust.
Core Principles
- Stripe is the right choice for 95% of bootstrapped SaaS. Do not overthink this decision.
- Test mode exists for a reason. Never touch live mode until you've tested every flow.
- Billing is the one place you cannot "move fast and break things." A billing bug loses trust permanently.
- Automate everything. Manual invoicing doesn't scale and you will forget.
- Tax compliance is not optional. Set it up from day one.
Stripe Setup Checklist
``` Stripe Configuration: - [ ] Create Stripe account and verify identity - [ ] Enable test mode (toggle in top-right of
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/payments/SKILL.md