agentleFS
Sign inStart free
charanjit-singhcharanjit-singh/lovable-skills/skills/payment-failed-and-recovery/SKILL.md

payment-failed-and-recovery

Skill10 starsChanged 6 months agoMITView on GitHub

Use when handling failed Stripe payments: invoice.payment_failed, past_due subscriptions, dunning emails, grace periods, or billing recovery UX. Not for initial Checkout setup or webhook signature basics (use stripe-payment-webhooks).

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document in code comments:

    line 26
  2. Very specific:

    Default recommendation: 3–7 day grace + banner.

    line 32
  3. Distinctive:

    Do not delete user data on first failure.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Payment failed and recovery

Failed renewals are normal. Handle via webhooks + clear UX, not silent lockout.

Webhook events

EventMeaning
invoice.payment_failedCharge failed; subscription often → past_due
customer.subscription.updatedStatus may be past_due, unpaid
invoice.paidRecovery successful — restore active

Handler: upsert subscriptions.status from Stripe object; never invent status client-side.

Entitlement policy (choose explicitly)

Document in code comments:

Strict — revoke pro immediately on past_due.

Grace — keep pro for N days while past_due; store grace_until on subscription row.

Default recommendation: 3–7 day grace + banner; full revoke when status canceled or unpaid.

UX

  • Global banner for past_due: "Payment failed — update card" → Customer Portal link.
  • stripe.billingPortal.sessions.create({ customer, return_url }) from edge function or authenticated API.
  • Do not delete user data on first failure.

Email (optional)

On invoice.payment_failed, invoke send-email edge function (email-and-notifications skill) with idempotency key event.id.

Stripe settings

  • Smart Retries enabled in Stripe Billing settings.
  • Configure dunning emails in Stripe or your app, not both blindly (duplicate emails).

Avoid

  • Ignoring invoice.payment_failed.
  • Permanent ban without subscription.deleted or explicit cancel.
  • Charging again from custom code instead of Stripe retry + Portal.

Checklist

  • invoice.payment_failed updates DB status
  • Portal link in app for affected users
  • invoice.paid restores access
  • Idempotent on event replay

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free