RevampKeyRevampKey home
Download

Plan and build a Stripe integration with AI

Uses Stripe's own implementation planner and current docs to choose the right products (Checkout, Billing, Connect), then writes the endpoints, webhooks and test-mode setup in your codebase.

Asks before writingUses 5 Stripe toolsWorks in RevampKey, Claude Code, Codex and Cursor

Use in RevampKey

Get RevampKey to connect Stripe

RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Stripe is one click away with its skills already attached.

Download RevampKey

Not now? Use the skills in your current tool

curl -fsSL --create-dirs -o .claude/skills/stripe-integration-plan/SKILL.md https://revampkey.com/marketplace/stripe/skills/integration-plan/SKILL.md
Other agents
Other agents

When to use it

  • Adding payments or subscriptions to an app
  • Choosing between Checkout and the Payment Element
  • Setting up webhooks correctly

What it looks like

You

Add monthly and yearly subscriptions to this Next.js app.

stripe_implementation_plannersearch_stripe_documentationstripe_api_searchstripe_api_details+1 more
Agent

Plan: Stripe Billing with hosted Checkout. One product with two prices, a /api/checkout route that creates the session, the customer portal for changes, and a webhook for checkout.session.completed, invoice.paid and invoice.payment_failed. Create the test-mode product and prices now?

The SKILL.md file

View raw
name: stripe-integration-plan

Plan and build a Stripe integration, such as Checkout, Billing subscriptions, Connect or webhooks, using Stripe's implementation planner and current docs, with test-mode verification. Use when the user wants to add payments, subscriptions or Stripe webhooks to their app, or asks which Stripe product to use.

Steps

  1. Ask, or read from the repo: what they sell (one-off, subscription, usage-based or marketplace), the stack, and where customers pay (hosted page, embedded, or mobile).
  2. Run stripe_implementation_planner with that context to get Stripe's recommended approach, such as Checkout vs Payment Element, Billing, or Connect.
  3. Check the details in current docs with search_stripe_documentation, and the exact API objects with stripe_api_search and stripe_api_details. Prefer the newest recommended APIs over older ones you remember.
  4. Write the plan:
    • products and prices to create;
    • server endpoints, such as creating a Checkout Session, and the client changes;
    • webhooks to handle (at least checkout.session.completed and invoice.paid or invoice.payment_failed for subscriptions), with signature verification;
    • test cards and test clocks for subscriptions.
  5. When the repo is open, implement it step by step, with keys read from environment variables.
  6. Create test-mode products or prices with stripe_api_write only after the user approves, and never in live mode during setup.

Done means

A full test-mode payment works end to end, the webhook handler verifies signatures, and the user has a short checklist for going live.

Stripe tools it uses

  • stripe_implementation_planner
  • search_stripe_documentation
  • stripe_api_search
  • stripe_api_details
  • stripe_api_writeAsks first

Tool list from Stripe MCP documentation.

FAQ

Does it use the latest Stripe APIs?

Yes. It checks Stripe's current docs and planner rather than relying on memory.

Will it touch my live account?

No. Setup happens in test mode, and anything it creates needs your yes.