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.