payment-failure-handler

Automate Stripe payment failure retries with webhooks and notifications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/josuerivera300891-prog/GymTime --skill payment-failure-handler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: payment-failure-handler
Source: https://github.com/josuerivera300891-prog/GymTime/tree/main/skills/payment-failure-handler
Command: npx skills add https://github.com/josuerivera300891-prog/GymTime --skill payment-failure-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires stripe, twilio, supabase.

What problem does it solve?

Proactively manages recurring payment failures to minimize revenue loss, keeps admins and members informed, and automates retry workflows.

Core Features & Use Cases

  • Webhook-driven failure detection and status updates for Stripe events like payment_intent.payment_failed and invoice.payment_failed.
  • Automatic member and admin notifications, with a clear retry and escalation flow.
  • Grace-period-based retries that preserve access while attempting recovery.

Quick Start

Configure Stripe webhooks for payment failures and deploy the handler to start automatic retries.

Frequently Asked Questions about payment-failure-handler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Stripe payment failure recovery for recurring memberships?

Automate Stripe payment failure recovery by configuring webhooks to detect failed invoices and trigger a workflow that updates membership status, schedules retries, and sends alerts. This handler manages the entire process, enforcing a grace period with up to three retries while notifying members and admins.

Do I need Twilio and Supabase to handle Stripe webhook payment failures?

Yes, you need Twilio and Supabase to handle Stripe webhook payment failures with this handler. The workflow requires Supabase to update and track membership status, and Twilio to deliver automated notifications to members and admins regarding retry schedules and escalation.

What happens to a member's access during a failed payment retry grace period?

During a failed payment retry grace period, the member's access is preserved while the system attempts recovery. This handler schedules up to three automated retries across the grace period, ensuring members retain their access until all recovery attempts are exhausted.

How do I set up Stripe webhooks for failed invoice payments and retries?

Set up Stripe webhooks for failed invoice payments by configuring your Stripe dashboard to send events like invoice.payment_failed to your handler endpoint. Once deployed, the handler automatically detects these events, updates membership status, and schedules the retry workflow.

Can I customize the number of payment retries for failed Stripe memberships?

The number of payment retries for failed Stripe memberships is fixed at a maximum of three attempts. This handler enforces this limit across a defined grace period, automatically escalating notifications to admins and members if recovery fails after the final attempt.