More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Stripe Integration Check

    1

    A webhook handler that trusts req.body lets anyone send a fake "payment succeeded" event, and an amount taken from the request lets a buyer pay 1 cent for anything.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Stripe Integration Check

    Stripe Integration Check

    Example session with this skill installed

    Check this project with stripe-integration-check.

    • Read your context and instructions
    • Compiled the stripe integration check

    $ python3 scripts/check_stripe.py examples/risky
    BLOCK server/checkout.js:1 S01 LIVE_SECRET_IN_CODE
    sk_... key (19 chars, hidden)
    Why: A live secret key (sk_live_), a live restricted key (rk_live_) or a webhook signing secret (whsec_) is written in a code or config file. Anyone with the repository, a build or a backup can charge cards, issue refunds, read customer data, or forge webhook events.
    Safer: Load keys from environment variables or a secrets manager, never from code. Roll the key in the Stripe Dashboard (Developers > API keys) now, because it stays in the repository history.

    BLOCK server/checkout.js:5 S04 AMOUNT_FROM_CLIENT
    BLOCK server/webhook.js:3 S03 WEBHOOK_NOT_VERIFIED
    BLOCK src/components/Checkout.jsx:2 S02 SECRET_KEY_IN_BROWSER
    REVIEW scripts/seed.js:1 S11 TEST_KEY_IN_CODE
    REVIEW server/checkout.js:5 S13 NO_IDEMPOTENCY_KEY
    REVIEW server/refunds-webhook.js:5 S12 WEBHOOK_BODY_PARSED_FIRST
    REVIEW server/webhook.js:3 S15 PAYMENT_STATUS_NOT_CHECKED
    REVIEW src/components/Checkout.jsx:5 S14 RAW_CARD_DATA
    REVIEW src/components/Checkout.jsx:6 S14 RAW_CARD_DATA

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 5 files, 5 with Stripe content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A webhook handler that trusts req.body lets anyone send a fake "payment succeeded" event, and an amount taken from the request lets a buyer pay 1 cent for anything. This skill finds those and seven other Stripe integration mistakes before you go live, and tells you how to fix each one.

    Your agent runs a scanner on your code (Node.js, Next.js, Python, PHP, Ruby, front-end files), config files and .env files. Comments are skipped, so a signature check that was commented out counts as missing. It tells browser code from server code, and follows request values through variables (const { amount } = req.body). It never calls Stripe. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Keys are never printed.

    What it checks

    BLOCK

    • S01: a live secret key, live restricted key or webhook signing secret in code or config
    • S02: a secret key in browser code (loadStripe with sk_, client components, NEXT_PUBLIC_ or VITE_ variables)
    • S03: a webhook handler with no constructEvent (signature) check
    • S04: amount, unit_amount or line_items taken from the request

    REVIEW

    • S11: a test secret key written in code
    • S12: the body parsed or re-encoded before the signature check
    • S13: PaymentIntents, charges, refunds or payouts created without an idempotency key
    • S14: card numbers or CVC codes on your own form or server
    • S15: checkout.session.completed handled without checking payment_status

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example project (server, webhook and React checkout), and the real report the scanner produces on the risky one

    Limits It reads code as text: values are followed within one file, so checks done in another module are not seen. Dashboard settings, hosting environment variables and Radar rules are not checked. NOT FLAGGED is not a guarantee.

    Static check of code and config text. Values are followed within one file only; Stripe Dashboard and hosting settings are not checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert keys (sk_live_EXAMPLE0000) for the scanner to find. They cannot be used with Stripe.

    Listed7 days ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads your code and config files as text. It never calls the Stripe API and needs no keys.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example project with a server, a webhook handler and a React checkout, and the real report the scanner prints on the risky example.

    New in APIs & Backend