agentleFS
Sign inStart free
charanjit-singhcharanjit-singh/lovable-skills/skills/payment-webhook-testing/SKILL.md

payment-webhook-testing

Skill10 starsChanged 6 months agoMITView on GitHub

Use when testing Stripe payment webhooks locally, debugging webhook failures, Stripe CLI forward, replaying events, or webhook logs. Not for production deploy only or writing marketing copy.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read response body and status.

    line 54
  2. Very specific:

    Use Resend after fix to replay (still idempotent on event.id)

    line 55
  3. Very specific:

    Use test cards: 4242 4242 4242 4242

    line 68
  4. Distinctive:

    Never use live keys in Lovable preview or git.

    line 69

≈ “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 webhook testing

Stripe CLI (local)

stripe login
stripe listen --forward-to http://127.0.0.1:54321/functions/v1/stripe-webhook

Copy the webhook signing secret CLI prints (whsec_...) into local STRIPE_WEBHOOK_SECRET (not production secret).

Trigger test events:

stripe trigger checkout.session.completed
stripe trigger customer.subscription.updated
stripe trigger invoice.payment_failed

For custom metadata (user_id), create sessions via API in test mode, then complete Checkout in browser, or use stripe trigger with fixtures where supported.

Supabase local functions

supabase functions serve stripe-webhook --env-file ./supabase/.env.local

Env file must include:

  • STRIPE_SECRET_KEY (sk_test_...)
  • STRIPE_WEBHOOK_SECRET (from stripe listen)
  • SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY

Verify checklist

CheckHow
SignatureWrong secret → 400; correct → 200
IdempotencySend same event.id twice → second 200, no double DB row
DB writeRow in subscriptions / orders matches Stripe Dashboard
Live vs testevent.livemode matches environment

Dashboard debugging

  • Stripe → Developers → Webhooks → select endpoint → Recent deliveries
  • Read response body and status; fix 4xx/5xx before shipping
  • Use Resend after fix to replay (still idempotent on event.id)

Common failures

SymptomFix
Invalid signatureRaw body parsing; wrong whsec; body parsed as JSON before verify
500 timeoutReturn 200 after DB write; move email to async
User not linkedMissing client_reference_id / metadata.user_id on Checkout
Pro not unlockedClient gating before webhook; add polling or Realtime on subscriptions

Test mode data

  • Use test cards: 4242 4242 4242 4242
  • Never use live keys in Lovable preview or git.

Avoid

  • Disabling signature verification locally "temporarily" and shipping it.
  • Testing only via success_url without firing webhook.

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