Connect Stripe to Claude Code
Give Claude Code governed access to Stripe’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Stripe to Claude Code in four steps
Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.
- 1
Approve Stripe in Runlayer
Add Stripe from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Stripe’s 10 tools show up in Claude Code’s own tool list (supported Claude Code versions).
Claude Code setup guide - 3
Sign in to Stripe
Sign in the way Stripe requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Stripe from Claude Code
Stripe’s approved tools appear in Claude Code. Every call is checked against policy and recorded.
Tools
10 Stripe tools in Claude Code
Runlayer policy decides which of these Claude Code users can call.
List available accounts or orgs
Lists all Stripe accounts in this session with their stripe_context and livemode values.
Manage Stripe accounts
Returns a URL to the Stripe Dashboard where users can add accounts, remove accounts, or change permissions for this session.
Search Stripe documentation
Search the Stripe documentation for the given question and language.
Send Stripe feedback
Share feedback about Stripe's products.
Analytics
Is for analyzing Stripe Sigma and Metrics data (e.g. about revenue, charges, products, invoices, subscriptions, disputes, transactions, tax tables, payments etc) and running SQL-based reporting…
API details
Get detailed parameter information for a specific Stripe API operation.
Read API
Use stripe_api_search to find the operation ID.
API search
Search for Stripe API operations by providing an intent and a resource to operate on.
Control
What Runlayer can see and stop in Claude Code
Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.
Gateway policy (available)
Every Stripe call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
OTLP telemetry (available)
Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.
Stop a call before it runs (available)
Runlayer can deny a tool call before Claude Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Claude Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.
In Claude Code
- When a tool fails, Runlayer records the error but cannot hide it.
Frequently asked questions
Connect more