stripe

Implements Stripe checkout, webhooks, refunds, and Connect changes with payment safety invariants.

1|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/amoai-tech/mdeai --skill stripe-amoai-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe
Source: https://github.com/amoai-tech/mdeai/tree/main/.claude/skills/stripe
Command: npx skills add https://github.com/amoai-tech/mdeai --skill stripe-amoai-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Payment changes are high-risk: a mishandled webhook, an exposed secret key, or a non-idempotent handler can duplicate tickets, corrupt ledgers, or leak credentials. This Skill enforces safe Stripe implementation practices for checkout, payment intents, refunds, Connect, and webhook handling in the MDE codebase. ## Core Features & Use Cases - Payment Safety Invariants: Enforces rules like never exposing secret keys to client code, verifying webhook signatures from the raw request body, and never trusting client redirects as proof of payment. - Idempotent Webhook Handling: Ensures duplicate webhook deliveries do not duplicate tickets, ledger rows, or fulfillment. - Scoped Workflow: Traces the current request and persistence path end to end, defines duplicate/retry/failure behavior before editing, and makes the smallest safe change. - Use Case: When adding a refund flow to ticket checkout, use this Skill to trace the existing payment path, verify current Stripe API behavior in official docs, implement the change, and test duplicate-delivery and invalid-signature webhook cases. ## Quick Start Use the stripe skill to implement an idempotent webhook handler for ticket payment confirmation with signature verification.

Frequently Asked Questions about stripe

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

FAQPage Schema
How do I handle Stripe webhooks idempotently?

Verify the webhook signature from the raw request body before trusting any event, then make all side effects idempotent so duplicate deliveries do not duplicate tickets, ledger rows, or fulfillment. Test with duplicate-delivery and invalid-signature cases before shipping.

How do I verify a Stripe webhook signature?

Verify the signature against the raw request body, not a parsed or re-serialized payload, using the webhook secret kept server-side only. Never trust a client redirect or client-supplied status as proof of successful payment.

Does this project require adding the Stripe npm package?

No. The current repository has no direct Stripe npm dependency and uses an edge/HTTP pattern instead. Only add the Stripe package if the task explicitly requires it and the existing pattern is insufficient.

When should payment work be handed off to other skills?

Route ticket and event business rules to the events skill, RLS and schema questions to supabase, unknown root-cause failures to systematic-debugging, and production-critical completion claims to task-verifier. The stripe skill owns only Stripe-specific implementation and payment safety.

What are the security rules for Stripe secret keys?

Never expose secret keys or webhook secrets to client code. Keep payment writes scoped to the authenticated organization or user and the intended checkout object, and verify all webhook events server-side before acting on them.