How to
How to connect Claude to Stripe safely
Stripe is where the money is, which makes it the clearest case for gated write access. Claude can prepare a refund or an invoice completely, and nothing moves until you approve it.
Connect Claude to Stripe safely through a custom MCP connector that authenticates with OAuth and keeps read and write tools separate. Claude can look up customers, charges, and invoices freely, while money-moving actions like issuing refunds, sending invoices, and changing subscriptions are gated: prepared by Claude, executed only after you approve.
Key takeaways
- The common Stripe connection is read-leaning: it can look up payments but usually cannot refund, invoice, or edit subscriptions.
- A custom connector adds those write actions, each scoped and separate from reading.
- Money-moving actions, refunds, charges, and sending invoices, always require your confirmation.
- The connector inherits your Stripe permissions and can be revoked from Stripe at any time.
Can Claude do real billing work in Stripe, or just look things up?
The common way to connect Claude to Stripe today is read-leaning: Claude can often look up customers, charges, or invoices, but creating refunds, editing subscriptions, and sending invoices are usually limited or out of reach. A custom connector adds those write actions behind scoped, human-in-the-loop controls.
Lookups already help: pulling up a customer, finding the charge behind a dispute email, checking an invoice's status. But the follow-up, the refund, the corrected invoice, the plan change, still means tab-switching into the Stripe dashboard.
A custom connector closes that loop without removing the human from it. Claude prepares the billing action in full, and the money-moving step waits for you.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I connect Claude to Stripe safely?
Through a custom MCP connector built with separation and gating from the start. It authenticates to Stripe with OAuth and the narrowest scopes the work needs, keeps read tools apart from write tools, and requires your confirmation on refunds, invoice sends, and other money-moving actions.
The setup runs in a few steps:
- 1Tell us which billing workflows Claude should handle: refunds, invoicing, subscription changes, reconciliation.
- 2We build a custom MCP connector with read tools (look up customers, charges, invoices) and write tools (refund, invoice, subscription changes) kept strictly separate.
- 3You authenticate through OAuth with the narrowest scopes the work needs, so the connector never has more access than your own Stripe account.
- 4Claude starts handling billing follow-ups in your conversations, and every money-moving action waits for your explicit approval.
Money movement is never automatic
Issuing a refund, creating a charge, and sending an invoice are always gated write tools. Claude can prepare the action down to the exact charge and amount, but nothing moves money until you approve it.
Can Claude issue a refund in Stripe?
Yes, with a custom connector. Refunding is a separate write tool, `issue_refund`, that targets a specific charge and a full or partial amount, and it runs only after you approve it. The read-leaning default connection can look up a payment but cannot move money.
The precision is the safety feature. A refund is never a vague instruction; it is a specific charge, a specific amount, full or partial, shown to you before it executes. You are approving exactly what will happen, not a general intent.
Can Claude create and send invoices from Stripe?
Yes. Claude drafts an invoice for a customer at a stated amount with `create_invoice`, ready for your review, and sending is gated as an outbound action that waits for your confirmation. Claude prepares everything, but nothing leaves your account until you approve the send.
Around invoicing sit the customer and reconciliation tasks that make it useful:
- Create or update a customer record with billing details before invoicing.
- Look up a payment and reconcile it against an open invoice.
- Issue a full or partial refund on a specific charge after approval.
Drafting and lookups flow freely; the send is the moment that touches the customer, so the send is the moment that waits for you.
Can Claude update or cancel a Stripe subscription?
Yes. With scoped write tools like `update_subscription`, Claude can change a subscription's plan, quantity, or billing cycle, or cancel it to end at period end. These changes affect what a customer is charged, so they run with your approval, like every other money-adjacent write.
Scheduling a cancellation at period end rather than immediately is the kind of detail that matters in billing, and it is exactly the kind of option Claude can present for you to choose before anything executes.
What access does a Claude Stripe connector get, and can I revoke it?
The connector authenticates to Stripe through OAuth and inherits your existing permissions and the scopes you grant, never more. You can revoke that access from Stripe at any time without touching the rest of your setup, and read and write tools stay separated for the life of the connector.
Because access is granted through Stripe itself, the kill switch lives there too. Revoking the connector in Stripe cuts it off immediately, independent of anything on the Claude side.