laravel-billing_skill

Overview

This skill integrates Stripe and Paddle payments with Laravel Cashier to implement subscriptions, invoices, payment methods, webhooks, and billing portals. It provides architecture patterns, FuseCore module guidance, and a decision guide to choose Stripe vs Paddle based on tax, compliance, and business model. The skill also prescribes an agent workflow to run discovery, research, and validation agents before and after implementation.

How this skill works

Before coding, the workflow spawns three agents to inspect the codebase, verify Cashier docs, and query provider-specific patterns. Implementation follows a modular billing module (controllers, services, listeners, routes) and wiring of the Billable trait on the User model. After implementation, a validation agent runs automated checks against webhook handling, subscription flows, and configuration.

When to use it

• Adding subscription billing (recurring plans or meter-based pricing)
• Implementing one-time checkout flows and invoice generation
• Handling webhooks and server-to-server billing events
• Choosing between Stripe (processor) and Paddle (merchant of record)
• Integrating a customer billing portal for self-service management

Best practices

• Always use webhooks for payment confirmations and verify signatures
• Never store raw card details; use payment tokens/methods
• Test thoroughly with test keys and Stripe CLI before production
• Implement grace periods and handle incomplete payments (3D Secure)
• Keep price IDs and keys out of code; use env or module-level config

Example use cases

• Create subscription plans with trial periods and swap/cancel flows
• Implement Stripe Checkout and redirect users to a billing portal
• Process Paddle purchases where tax/compliance are handled by the provider
• Build webhook listeners that update subscription state and invoices
• Add metered billing endpoints to record usage for usage-based plans