stripe-subscription-tester

You test Stripe subscription lifecycle events locally by using the Stripe CLI to trigger webhooks for incomplete, failed, past_due, and unpaid states, then verifying the Rails database to confirm the app correctly locks or unlocks company access.

The best way to verify a failed Stripe payment locks a company account is to simulate payment failures and past_due states via Stripe CLI webhooks, then inspect the company and subscription status in your Rails database to ensure the lock behavior triggers correctly.

You simulate a successful payment recovery by triggering a successful payment event through the Stripe CLI after a past_due or unpaid state, then checking the Rails app to confirm the webhook handler restores access and unlocks the company.

Yes, this approach to Stripe subscription testing works with parent-child company lock flows by verifying webhook-driven state changes across related company records in the Rails app, ensuring child-company behavior remains intact when a parent company is locked or unlocked.

Before testing Stripe subscription billing flows locally, you need the Stripe CLI configured to forward webhooks to your local Rails server, and access to the Rails database to verify company, customer, subscription, and payment states between each lifecycle step.

Your Stripe webhook handler may not lock a customer account because the subscription state transition or event payload handling is incorrect; this Skill helps isolate the issue by testing incomplete, failed, and unpaid webhook events and verifying the resulting Rails database lock state.