- Home
- Skills
- Agents & Orchestration
- stripe integration reviewer
Works with the AI Agents you already use
stripe integration reviewer
Audit and fix Stripe integration bugs including webhook idempotency, race conditions, and missing dispute handling.
$15
stripe integration reviewer
Example session with this skill installed
Audit our Express webhook handler in routes/stripe.js for idempotency and race conditions. We are seeing occasional duplicate subscription records in our database.
- Read your context and instructions
- Compiled the stripe integration reviewer
The handler lacks a completion marker. If your process crashes after DB insertion but before responding to Stripe, redelivery will skip the logic, causing data loss. I have generated a claim-then-complete fix using your PostgreSQL store and added a monotonicity check for subscription status.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Stripe integration code often fails silently in production due to redelivered webhooks, out-of-order events, and unhandled disputes. Developers frequently assume a try/catch block ensures idempotency, but without a dedicated claim-and-complete mechanism, you risk double-charging customers or losing data during crashes.
What it does
- Audits webhook handlers for strict signature verification using raw request bytes to prevent downgrade attacks.
- Identifies race conditions caused by Stripe's at-least-once, out-of-order event delivery guarantees.
- Verifies that idempotency logic uses an atomic claim-then-complete pattern keyed on event IDs.
- Checks for coverage of critical dispute and chargeback lifecycle events within your application logic.
- Generates integration tests utilizing Stripe Test Clocks to simulate subscription transitions like trial expiry and dunning.
Frameworks & tools
Works with Node.js (Express, Next.js Pages/App Router), Python (Flask, Django), and any stack using the official Stripe SDK. Specifically identifies framework-specific pitfalls like middleware body-parsing that breaks signature verification.
Why this beats prompting it yourself
General LLMs often suggest simple "insert-if-not-exists" patterns that still leave windows for data loss if a process crashes mid-execution. This skill enforces a specific two-step atomic protocol and monotonicity checks for state updates, ensuring your integration handles the edge cases documented in Stripe's technical snapshots.
Use cases
- Auditing a new payment flow before it handles real production transactions.
- Debugging "double-grant" or "double-charge" bugs caused by webhook redelivery.
- Adding programmatic handling for disputes and chargebacks to automate account flagging.
- Building a test suite that actually triggers time-dependent subscription events.
Known limitations
Does not cover PCI-DSS compliance or client-side script integrity. Limited to Stripe integrations, as logic does not transfer to other payment providers. Does not execute live API calls.
Focuses strictly on Stripe. Does not handle PCI-DSS audits. Does not execute code against live Stripe accounts. Requires access to webhook route configurations to verify raw body handling.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
No special permissions declared or detected