Connect Stripe to Codex
Give Codex governed access to Stripe’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Stripe to Codex in four steps
Admins approve the server once. Everyone in Codex 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 Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Stripe’s 10 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex 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 Codex
Stripe’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
10 Stripe tools in Codex
Runlayer policy decides which of these Codex 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 Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Stripe call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more