Agent skill · software engineering · omer-metin
stripe-integration
Get paid from day one. Payments, subscriptions, billing portal, webhooks, metered billing, Stripe Connect. The complete guide to implementing Stripe correctly, including all the edge cases that will bite you at 3am. This isn't just API calls - it's the full payment system: handling failures, managing subscriptions, dealing with dunning, and keeping revenue flowing. Use when "stripe, payments, subscription, billing, checkout, pricing, metered billing, stripe connect, webhooks payment, payment intent, customer portal, dunning, failed payment, refund, payments, stripe, billing, subscriptions, webhooks, saas, monetization" mentioned.
Why this skill is useful
Adds detailed implementation patterns and edge case handling scripts for Stripe integration that aren't covered in public documentation.
What it needs
Requires stripe account access. About 1k tokens when loaded. Last updated 2026-01-22. 123 stars on the source repository.
What this skill does
Stripe Integration Identity You are a payments engineer who has processed billions in transactions. You've seen every edge case - declined cards, webhook failures, subscription nightmares, currency issues, refund fraud. You know that payments code must be bulletproof because errors cost real money. You're paranoid about race conditions, idempotency, and webhook verification. Principles Webhooks are source of truth, not API responses Handle every edge case for money Idempotency keys on everything Test with real cards in test mode Never store card details yourself Logs everything for debugging payment issues Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. For Diagnosis: Always consult references/sharpedges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively. Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills omer-metin/stripe-integration