Connect Claude to Stripe by opening Customize > Connectors, adding Stripe from the directory, signing in through Stripe's own window with read access only, then switching Stripe on in a chat. It works on every Claude plan, Free included, and you can ask, "What made Monday's payout $2,279.80 smaller than the invoices paid?" Refunds stay yours to approve.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowOne catch before you start: the connector is not read-only out of the box. Stripe's server gives Claude a general read tool and a general write tool, and the write tool can create invoices, update customers and cancel subscriptions. Only some actions, such as creating a refund, pause for Stripe's own confirmation. So the setup below uses three layers: a Stripe login that can only view, Claude's write tools set to Blocked, and Manual mode in any chat that touches money.
What can Claude see and change once Stripe is connected?
Once Stripe is connected, Claude can read payouts, balance transactions, charges, refunds, disputes, invoices and customers, and a separate write tool can create or change things such as invoices and subscriptions.
The Stripe connector in Claude's directory is published by Stripe, carries the "Anthropic verified" label and points Claude at Stripe's remote server. The listing names eleven tools. Five of them matter for payout and refund questions, and two of those are general-purpose, with names that hide how much they can do.
| Tool Claude sees | What it does | Risk for a non-technical owner |
|---|---|---|
| stripe_api_read | Any Stripe "list" or "retrieve" request: payouts, balance transactions, charges, refunds, disputes, invoices, customers | Low. This is the tool your payout and refund questions use. |
| stripe_api_write | Any create, update or delete request Stripe supports through the server | High. Covers new invoices, coupon changes, cancelled subscriptions and refunds. |
| stripe_analytics | Metrics, reporting tables and reports; turns a plain question into a query (preview) | Low, read-only, but answers depend on report data being ready. |
| get_balance_summary | An interactive summary across your Stripe balance and Treasury accounts (public preview) | Low. |
| search_stripe_documentation | Searches Stripe's help and docs | None. Useful for "what does this status mean?" |
Stripe's own documentation is blunt about the write tool: confirmation depends on the action, not the tool name. Creating a refund triggers Stripe's "Human confirmation" step. Cancelling a subscription, voiding an invoice or creating a coupon do not carry that badge, so unless your account has extra approval rules, a misread request with the write tool allowed changes things straight away. That is why the stages below remove the write tool rather than relying on Claude to ask nicely.
How do you give Claude a Stripe login that can only look?
A Stripe login with the View Only role is the safest one to give Claude, as the role can view payments, balance, payouts, disputes and customers but cannot move money. When you connect through Stripe's sign-in window, you can only grant permissions you already hold in the Dashboard, so connecting with a login whose role cannot move money at all is the strongest safety switch available. That role can also create and download financial reports. It cannot create or refund payments, pay out to a bank, edit the payout schedule or touch bank details.
- In the Stripe Dashboard, open Team and security in your settings and invite a new team member. Use an email address you control, such as a finance alias, rather than your personal admin login.
- Give that member the View Only role and nothing else. Stripe warns that a user with several roles gets every permission of each, so one role keeps it clean.
- Accept the invitation from that inbox and set up two-step sign-in for it.
- If you are an Administrator, check the team-wide MCP and CLI access setting. Stripe lets you switch MCP access on or off separately for live mode and for sandboxes.
Budget about ten minutes. If you skip this stage and connect with your own Administrator login, everything still works, but the only things standing between Claude and a cancelled subscription are the permissions you tick in the next stage and the tool settings in Claude.
How do you connect Stripe in Claude and pick the live account?
Connect Stripe in Claude through Customize > Connectors: find Stripe in Discover, select Connect to Claude, sign in with the View Only login and tick only the live account.
Connectors are listed on every Claude plan on the pricing page, from Free at $0 to Pro at $20 a month billed monthly and the Team plan's $25 a seat monthly. The steps are the same on the web and in Claude Desktop:
- In Claude, go to Customize > Connectors, select Discover, type Stripe into Search connectors, open its page and select Connect to Claude.
- Stripe's sign-in window opens. Sign in with the View Only login from Stage 1, not your own.
- Choose the account. Stripe lets one connection cover live mode accounts and sandboxes, with different permissions for each. Tick only the live account you want answers about.
- Grant read permissions. If you want analytics answers as well as lookups, Stripe's guide names three to grant: Data > Metrics: Read, Data > Queries: Read and Data > Reports: Read. Those let Claude analyse without changing anything.
- Back in a chat, click "+", hover over Connectors and switch Stripe on for that conversation.
On Team and Enterprise plans, an Owner first adds the connector for the organisation (the button reads Connect for your team), then each person signs in to Stripe individually; members who can't add it see Request instead. To check the connection from Stripe's side, open your user settings in the Dashboard and look under OAuth sessions; the overflow menu there has Revoke access when you want to cut Claude off.
A note on dates if anyone in your business connected Stripe with a pasted key rather than the sign-in window. Stripe set a deadline of 30 November 2026: from December its server stops accepting full-access secret keys and restricted keys without the Agent tag, and returns an error instead. The fix is to reconnect through the sign-in window or create a new agent API key. A connection made through Claude's directory and the sign-in window is not affected.
How do you block Claude's Stripe write tools and use Manual mode?
Set Stripe's read tools to Always allow and its write and delete tools to Blocked in Claude, and use Manual mode for refund chats; Blocked is the only setting that holds in every mode.
Claude has two separate controls, and owners mix them up. Tool permissions are set per connector: in Customize > Connectors, select Stripe under Your connectors and, under Tool permissions, choose Always allow, Needs approval or Blocked for each group of tools or for a single tool. On Team and Enterprise plans the Owner can set these for everyone, and members cannot override them. Be careful with the approval pop-up in a chat too: Allow once lets one call through, while Always allow switches that tool's prompt off from then on. The mode is chosen per conversation from the mode selector in the message box: Manual, Auto or Skip.
How the two combine, according to Claude's help centre:
| Mode | Tool set to Always allow | Tool set to Needs approval | Tool set to Blocked |
|---|---|---|---|
| Manual | Runs | Asks you first | Refused |
| Auto | Read-only tools run; write tools run unless an automated check flags them | Runs without asking unless the check flags it | Refused |
| Skip | Runs | Runs | Refused |
The row that matters is the last column. Blocked is the only setting that holds in every mode, and Needs approval quietly stops asking once someone switches a chat to Auto. Anthropic's own wording on Auto is that the check can miss risky actions, and it suggests switching back to Manual for work involving money or messages sent as you. So for Stripe: read-only tools on Always allow, write and delete tools on Blocked, and Manual mode in any chat about refunds.
The same logic applies if Gmail is connected in the same chat, which is common when you want Claude to draft a refund update for a customer. Claude's Gmail connector can now send, reply and forward. Outside Auto mode it asks before each send by default; in Auto mode a send can go out without asking unless the automated check flags it. If you want a human to press send every time, set Gmail's sending tools to Blocked so Claude can only draft, or stay in Manual mode and read each request before you allow it.
If you ever do allow Stripe's write tool, Stripe adds its own brake for refunds. Claude hands you a link, you review the refund in the Dashboard and click Approve, then you tell Claude to retry the request. An approval you ignore expires after 24 hours. Every call Claude makes is also listed in Stripe's Workbench, under the Logs tab at MCP tool calls, where you can filter by tool and see the arguments and response. Checking that list once a month takes two minutes and shows exactly what Claude read.
Which Stripe payout questions does Claude answer best?
Claude answers payout questions best when each one names a payout, a date range and the breakdown you want. These four cover most weeks; the sample answers are illustrative, with what to check underneath each.
List every payout that arrived or is due between 1 and 31 October.
For each: payout ID, estimated arrival date, amount, status.
Flag any payout that failed or is still in transit.
Illustrative answer: "Four automatic payouts, all paid: 5 Oct $8,941.20, 12 Oct $6,120.20, 19 Oct $11,402.90, 26 Oct $7,365.10. One more, $5,880.45, is due 2 Nov and includes card payments from the last week of October." What to check: the total of the four, $33,829.40, should equal the payout line in Stripe's Balance summary for the month. If Claude's list is shorter than the Dashboard's Payouts page, ask it to count the payouts first and list them second.
Break down payout [payout ID] into its charges, refunds, disputes and fees.
Give gross, fees and net for each group, then explain in two sentences
why the payout differs from the total of invoices paid that week.
This is the question owners actually have, and the worked example below walks through one answer in full. What to check: the groups should add up to the payout to the cent. If they don't, the answer probably mixed in a transaction from the next payout.
Compare the last eight weekly payouts. Which one is furthest below the
average, and which single transaction explains most of the gap?
Illustrative answer: "The 12 Oct payout was $6,120.20 against an eight-week average of $8,402. The largest single deduction was a $1,200.00 refund on 8 Oct." What to fix: averages hide one-off invoices, so ask for the median too when one big project lands in a single week.
How much money is in Stripe right now that has not been paid out yet,
split into available and pending? When will the pending part become available?
Useful on the last working day of a month, when your accountant asks how much of the month's takings is still sitting in Stripe. The answer comes from your balance, which Stripe splits into available and pending funds.
One marketing agency's October payouts against the bank
Take an illustrative six-person marketing agency that bills monthly retainers and one-off projects through Stripe invoices, with automatic payouts every Monday. In early November the owner wants October's payouts tied to the business bank account before the bookkeeper closes the month. She uploads the bank statement as a CSV, switches Stripe on and asks Claude to match each payout to a deposit by amount, allowing up to three working days for the bank to post it.
| Stripe payout | Estimated arrival | Bank deposit found | Claude's verdict |
|---|---|---|---|
| $8,941.20 | Mon 5 Oct | $8,941.20 on 5 Oct | Matched |
| $6,120.20 | Mon 12 Oct | $6,120.20 on 13 Oct | Matched, posted a day later |
| $11,402.90 | Mon 19 Oct | $11,402.90 on 19 Oct | Matched |
| $7,365.10 | Mon 26 Oct | $7,365.10 on 26 Oct | Matched |
| None | None | $2,400.00 on 21 Oct | Not a Stripe payout |
Two lines deserve a second look. The 12 October payout landed a day late, which is normal: Stripe's payout reconciliation report groups payouts by the estimated arrival date on the Payouts page, not by the date your bank posts the money. And the $2,400.00 deposit on 21 October tempted Claude, because a client had also paid a $2,400.00 invoice by card that month. Card payments never reach the bank one by one; they arrive bundled inside a payout, net of fees. The $2,400.00 was a client's direct bank transfer, and it belongs in the books as its own receipt.
Then the question she cared about: why was the 12 October payout so small? Claude's illustrative breakdown:
| Group | Count | Gross | Fees | Net |
|---|---|---|---|---|
| Card payments for invoices ($3,200, $2,400, $1,850, $950) | 4 | $8,400.00 | $244.80 | $8,155.20 |
| Refund for a cancelled September campaign | 1 | -$1,200.00 | $0.00 | -$1,200.00 |
| Dispute on an earlier $820 payment | 1 | -$820.00 | $15.00 | -$835.00 |
| Payout | $6,120.20 |
The fees follow Stripe's standard rate for domestic cards, 2.9% plus 30 cents per successful payment: 2.9% of $8,400 is $243.60, plus four lots of 30 cents makes $244.80. The dispute line carries Stripe's $15 fee for a dispute received. So the plain-English answer is: invoices worth $8,400.00 were paid, Stripe kept $244.80, and $2,035.00 left for a refund and a dispute, a gap of $2,279.80 in all. The owner now knows the dispute needs a response and that the refund cost more than it looked, because the original $35.10 fee on that $1,200 payment is not returned.
One payout falls across the month line. The $5,880.45 due on 2 November contains charges from the last days of October, so October's sales and October's deposits will never be the same figure. Stripe's report shows those unsettled amounts in its Ending balance reconciliation section, and Claude can list them on request. That list is what the bookkeeper needs to treat the money as "in transit" at month end.
Time taken: about 20 minutes, against the hour or so it takes to download the itemised report and tick it against the statement by hand. If your books are in Xero, the same idea of checking matches before you post them is covered in checking Xero matches with Claude before you reconcile; for the accounting side of payout fees, see reconciling payouts and fees in your accounting software.
If the bank-matching spreadsheet is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
What do Stripe's refund statuses mean for your customers?
Stripe's refund statuses (pending, succeeded, requires_action, failed and canceled) each mean something specific, and plain English helps most here. Here is what each tells you, in the words you would use with a customer:
| Status Claude reports | What it means | What you do |
|---|---|---|
pending | Sent, not yet confirmed, or waiting for your balance to cover it | Check your available balance if it has been more than a day |
succeeded | Stripe has sent it; the customer usually sees it in 5 to 10 business days | Give the customer the date and, once available, the reference number |
requires_action | For some payment methods Stripe needs the customer's bank details first | Tell the customer to answer Stripe's email |
failed | The bank could not process it, for example a closed account; money returns to your balance | Refund the customer another way |
canceled | Cancelled before it reached the customer | Confirm that was intended |
Three refund facts change how you answer customers. Refunds come out of your available Stripe balance, not pending funds. If the balance cannot cover a card refund, Stripe holds it as pending until it can; after 45 days it fails with an insufficient funds reason. You can cancel an eligible card refund in the Dashboard only within 30 minutes of creating it. And Stripe does not return the processing fee from the original payment, which adds up.
A quick sum shows how much. Say the agency refunded nine card payments last quarter, totalling $5,400. The fees on those payments were 2.9% of $5,400, which is $156.60, plus nine lots of 30 cents, $2.70: $159.30 gone for good. Ask Claude "What did refunds cost us in fees last quarter?" and it can total the fee lines on the refunded charges for you. If refunds keep repeating for the same reason, the fix sits in your policy rather than in Stripe; writing clear refund rules before automating them covers that.
Here is the before and after of the most common refund chore. Before: a client emails, "You said you'd refunded the $450 audit fee on 3 November. Nothing has arrived." The owner opens the Dashboard, searches the customer, opens the payment, scrolls the timeline and writes a reply from memory. After: she asks Claude:
Find the refund for [client name] around 3 November for about $450.
Tell me its status, the date it was created, and whether a refund
reference number is available yet. Then draft a short, friendly reply
with the date the customer should expect it. Do not send anything.
Illustrative answer: "Refund of $450.00 created 3 Nov, status succeeded. No reference number yet. Draft: 'Hi [first name], the $450.00 refund left us on 3 November. Banks usually show refunds within 5 to 10 business days, so it should appear by 17 November. If it hasn't by then, reply and I'll send you the bank reference to quote.'" What to fix: Stripe says card references such as the acquirer reference number can take up to 7 business days to arrive, so promise the reference on request rather than in the first reply.
Where do Claude's Stripe answers go wrong, and how would you notice?
Claude's Stripe answers mostly go wrong when the question is one Stripe's data cannot answer cleanly, not because Claude invents numbers. Five worth knowing:
- Sandbox data in a live answer. If you ticked a sandbox as well as the live account at sign-in, Claude can answer from the wrong one. It shows up as "no refunds this month" when you know there were three. Fix: grant live mode only, or start the chat with "use the live account only".
- Instant and manual payouts. Stripe cannot say which transactions sit inside an instant payout, and its payout reconciliation report only covers automatic payouts. Ask Claude to break down an instant payout and you'll get a guess. Reconcile those against your balance history instead.
- Report data arriving late. Stripe's reporting runs on its own schedule, so a payout can reach your bank before its breakdown is ready. A breakdown that comes back empty on payout morning usually just needs a few hours.
- Day boundaries. Stripe records payments and payouts in UTC in most markets, so a payment taken late in your evening can belong to the next day in Stripe. Ask for totals by your own time zone if a daily figure looks one payment off.
- Negative payouts. If refunds exceed takings, your balance goes negative and Stripe can create a payout that debits your bank. Claude reports it as a payout with a minus sign; owners reading quickly assume it is money in.
One more slip from the agency example: an early run listed only the first page of October's charges and called the month quiet. It showed up because the count, 31 charges, did not match the Dashboard's 58. Asking "how many charges did you retrieve, and is that all of them?" before the analysis catches it every time.
If you want help fitting this into how your business actually runs, I offer one-to-one AI consultations for small businesses.
A 15-minute Monday payout check you can repeat
Here is the agency's routine, filled in for an illustrative week, so you can see the shape before adapting it:
- Payout landed? Claude lists this week's payout: $7,365.10, estimated 26 Oct. Bank shows $7,365.10 on 26 Oct. Tick.
- Payout explained? Breakdown: 5 card payments, $7,600.00 gross, $234.90 fees. No refunds or disputes. Tick.
- Refunds moving? One refund pending since Thursday; balance was low after a large refund. Note it and check again Wednesday.
- Disputes open? None new. The $820 dispute from 12 Oct is waiting for evidence, due date noted in the Dashboard.
- Anything Claude did? Workbench MCP tool calls show read requests only. Tick.
Check the sum in step 2 yourself the first few weeks: 2.9% of $7,600 is $220.40, plus five lots of 30 cents makes $221.90, so a $234.90 fee line means one payment cost more than the standard rate. Stripe's pricing page lists the usual reasons: 1.5% extra for an international card, 0.5% for a manually entered card and 1% where currency conversion is needed. That kind of question, "which payment had the higher fee and why?", is exactly what the connector is for. For the other apps worth connecting alongside Stripe, see the Claude connectors worth switching on in a small business, and if you run a Team plan, set the Stripe tool permissions as part of your Claude Team admin settings so nobody has to remember them per chat.
Claude and Stripe: questions owners ask
Does connecting Claude to Stripe cost anything extra?
No, Stripe's MCP documentation lists no charge for the server itself. Connectors are included on every Claude plan, Free included, and Pro is $20 a month billed monthly. Stripe's guide to analysing data with AI notes that its Queries API, which analytics questions can draw on, is free until 31 January 2027, with usage-based pricing from 1 February 2027, so check the price before relying on heavy analytics after that date.
How do I connect Claude to Stripe?
Open Customize > Connectors in Claude, select Discover, search for Stripe and select Connect to Claude. Sign in through Stripe's window with a View Only login, tick only the live account and grant read permissions. Then click "+" in a chat, hover over Connectors and switch Stripe on for that conversation.
Can my bookkeeper use this without my admin login?
Yes. Invite the bookkeeper to Stripe as a team member with the View Only role, then they connect Stripe in their own Claude account. Stripe only lets a connection grant permissions the person already has, so their Claude can read payouts, balances and refunds but cannot refund or pay out. On Claude Team plans an Owner adds the connector first; each person still signs in to Stripe separately.
Will Claude's payout dates match my accounting software?
Not always. Stripe groups each automatic payout by its estimated arrival date, while your bank feed shows the date the bank posted the deposit, which can be a working day or more later. Match on the payout amount and the payout ID rather than the date, and allow a window of a few working days around weekends and holidays.
What happens if Claude tries to create a refund?
Claude cannot complete it without you. Stripe marks creating a refund as an action that needs human confirmation: Claude receives a link, you open it and review the request in the Stripe Dashboard, and if you approve, you then tell Claude to retry. Unapproved requests expire after 24 hours. If you blocked Claude's write tools, as recommended here, the request never gets that far.
Further reads
- How to Connect Claude to QuickBooks Online, Read-Only First — The same read-only-first approach applied to QuickBooks.
- Claude Month-End Close: QuickBooks, PayPal and a Packet for Your Accountant — Turn payout checks into a month-end packet for your accountant.
- Claude and Zapier: Link a Business App Claude Has No Connector For — Reach a payments or booking app that has no Claude connector.
- Claude Gmail, Calendar and Drive Connectors: Set Up Safely — Keep Gmail sending behind your approval when Claude drafts replies.
- Chargeback Response Template: How to Write One With AI — Reason-code mapping, an evidence checklist and a response template you can fill with AI, plus the rule that nothing gets invented.
Browse all AI-for-business tutorials
Sources: Stripe docs (MCP server, API keys, restricted API keys, user roles, refunds, payouts, payout reconciliation report, analyse your data with AI, Workbench) and stripe.com pricing; Claude Help Centre articles on connectors, Google Workspace connectors and Cowork permission modes; claude.com pricing and the Stripe connector listing. All checked 18 November 2026.
