Claude Code Stripe Integration

Authenticate the Stripe CLI

Opens a browser to pair the CLI with your account so it can forward and trigger events.

Forward webhook events to your local endpoint

Prints a webhook signing secret (whsec_...) to use for local signature verification.

Trigger a specific test event

Fires a realistic test event so you can build and verify the handler without a real purchase.

Create a product from the CLI

Creates a product in the current mode so your catalog can be reproduced across environments.

Create a recurring price for a product

Amounts are in the smallest currency unit, so 900 is 9.00 USD.

Tail live API request logs

Streams API request logs so Claude Code can help diagnose failing calls in real time.

Create a server route in my framework that builds a Stripe Checkout Session for a one-time purchase. Use the line items I provide, set success and cancel URLs, keep the secret key server-only, and return the session URL to redirect the browser to. Do not put any secret key in client code.

Set up Stripe embedded checkout so the payment form renders inside my own page instead of a redirect. Create the server route that returns the client secret and the client code that mounts the checkout, keeping all secret key usage on the server.

Build a subscription signup with Stripe. Create a Checkout Session in subscription mode tied to the recurring price I give you, then write the webhook handling that provisions access when the first invoice is paid and revokes it when the subscription is cancelled.

Write a Stripe webhook endpoint for my framework. Read the raw request body, verify the Stripe-Signature header against the webhook signing secret using the Stripe library, and only process the event after verification succeeds. Handle checkout.session.completed and invoice.payment_failed as examples.

Create a Payment Intent flow where I control the payment UI. Write the server route that creates the Payment Intent and returns the client secret, and the client code that confirms the payment, including handling a required Strong Customer Authentication step.

Create the products and prices for my catalog using the Stripe API or CLI. Here is the plan structure with names, amounts, currencies, and billing intervals. Give me reproducible commands or code so I can recreate the same catalog in test and live mode.

Review my payment-creating requests and add idempotency keys so a retried request after a network failure cannot charge a customer twice. Explain where the key should come from and how long Stripe honors it.

Give me the exact Stripe CLI commands to forward webhook events to my local endpoint and to trigger the specific events my handler cares about. Tell me where to find the printed signing secret and how to put it in my environment.

My webhook is returning a signature verification error. Look at my handler and explain the likely cause, such as parsing the body before verification or using the wrong signing secret, then fix it so verification uses the raw request body and the correct secret.

Stripe is not delivering events to my endpoint. Help me diagnose it: check whether the endpoint is registered for the right mode, whether the CLI is forwarding, whether the URL is reachable, and whether my handler is returning a 2xx quickly enough.

Add handling for failed card payments and past-due subscriptions. Wire up the events that fire on payment failure and recovery, and update my application state so access is revoked when a subscription lapses and restored when payment succeeds.

Add a refund flow that issues a full or partial refund against a charge or Payment Intent from my admin side. Update my own records to reflect the refunded amount and status, and handle the case where a refund fails.

Set up Stripe's hosted customer portal so customers can update their card, change plans, and cancel on their own. Create the server route that generates a portal session for the signed-in customer and redirect them to it.

Enable Stripe Tax on my checkout and subscriptions so tax is calculated based on the customer's location. Explain what I need to configure in the dashboard and what changes in my checkout code for tax to be collected correctly.

Audit my Stripe integration for test and live mode mistakes. Find anywhere I mix a test key with a live price ID or endpoint, confirm the secret key is server-only, and list everything that must change before I switch to live keys.

My charges are off by a factor of 100 or using the wrong currency. Explain how Stripe expects amounts in the smallest currency unit, review my code, and correct the amount and currency handling so customers are charged the right value.

Some payments require Strong Customer Authentication and are failing silently. Update my Payment Intent flow to handle the requires_action state, present the 3D Secure challenge, and confirm the payment after the customer completes it.

I am getting a no such price error when creating a checkout or subscription. Help me confirm the price ID exists in the current mode, that it is not a test price used with a live key, and fix my code to reference the correct price.

I accidentally called the Stripe secret key from the browser and I am seeing CORS and exposure problems. Move all secret key usage to a server route, keep only the publishable key on the client, and explain why the secret key must never be exposed.

Review my Stripe integration before launch as a careful engineer. Check signature verification, idempotency, test-to-live key separation, a pinned Stripe API version so behavior does not drift on upgrades, error handling on payment failures, and that no card data is logged. List blocking issues separately from nice-to-haves.

What is the Claude Code Stripe integration?

It is a workflow that lets Claude Code help you build and test Stripe payments. Claude Code can scaffold checkout and Payment Intents, write signed webhook handlers, generate Stripe CLI commands for local testing, and troubleshoot payment errors. It speeds up a correct integration while you keep control of every decision that touches money.

Is it safe to use Claude Code with my Stripe keys?

Yes, if you follow the same rules Stripe recommends. Keep the secret key server-only and never in client code or the repository, build in test mode first, and verify webhook signatures. For MCP, the remote server at mcp.stripe.com uses OAuth so no secret key sits on your machine, which is the safer default.

Can Claude Code set up Stripe Checkout?

Yes. Claude Code can scaffold a hosted or embedded Checkout Session, create the server route that builds it, and wire the success and cancel URLs. It keeps the secret key on the server and returns only the session URL or client secret to the browser.

Can Claude Code write my Stripe webhook handler?

Yes, and this is one of the most valuable things it does. Claude Code generates a webhook endpoint that reads the raw body, verifies the Stripe signature against your signing secret, and only then processes the event, which is the step developers most often get wrong.

How do I test Stripe locally with Claude Code?

Use the Stripe CLI. Claude Code can generate the stripe listen command to forward events to your local endpoint and the stripe trigger command to fire specific test events, so you can build and verify the flow with test cards without waiting for a real purchase.

Which Stripe MCP server should I use?

Stripe offers an official MCP server in two forms. The remote server at mcp.stripe.com connects over OAuth with no secret key on your machine and is the safer default. The local server runs via npx with a test-mode secret key and is convenient for development. Both are official.

Can Claude Code handle subscriptions and billing?

Yes. Claude Code can set up subscription products and recurring prices, build a subscription checkout, and handle the lifecycle events that provision access on payment and revoke it on cancellation, including failed payment and past-due handling.

What are the most common Stripe mistakes Claude Code helps avoid?

The recurring ones are exposing the secret key on the client, skipping or breaking webhook signature verification, mixing test and live keys, missing idempotency so retries double-charge, and passing amounts in the wrong unit. Claude Code can audit for all of these before you go live.