Stripe in Muse: what Meta's connector can read and change

Last verified October 28, 2026
Updated Oct 28, 2026Published Oct 28, 2026

Stripe is one of the connectors Meta named when it opened Muse to small businesses, and it shows up in fourteen of our trade guides, from salons to law firms. Because Stripe holds real customers' cards and real money, this page goes through the connection slowly: which sign-in Stripe's server accepts, which Stripe objects Muse could touch, where Stripe stops and asks a human, how to cut access off, and what Meta and Stripe each say they do with what passes between them. It's written for owners and the person who does their billing.

What the labels mean here:

Label	Meaning on this page
Confirmed by vendor	Stripe, Meta or Zapier says so in its own documentation, legal terms, privacy policy, developer blog or company post.
Confirmed by Congress	It's the text of a federal statute, read on uscode.house.gov.
Conflicting	Two Stripe pages describe the same thing differently; both versions are shown.
Unverified	We went looking and came up with nothing solid enough to use.

How we built it: we read all the sources listed here on Oct 28, 2026, including Meta's announcement, its Connectors help page, Muse's terms and privacy policy and Meta's rules for connector makers; Stripe's MCP reference, API key guide, refund and dispute docs, services agreement, privacy policy, developer blog and its post about Muse; Zapier's docs; and three sections of the U.S. Code. We didn't connect Muse to a Stripe account, so none of this is tested, and we haven't seen Stripe's consent screen as Muse presents it. Neither company has published a setup guide written for Muse that we could find, which leaves gaps we point out as they come up.

Short version

Meta lists Stripe among Muse's connectors, and Stripe's own post says that with Muse you can set up payments, create products, change prices, send invoices, look at revenue trends and issue refunds. (Confirmed by vendor 1 9)
Stripe's MCP server signs clients in one of two ways: OAuth, which acts as your Stripe user, or an agent API key, which gives an AI program lasting access of its own. (Confirmed by vendor 6)
For some write actions, refunds and outbound payments among them, Stripe holds the request until a person opens the link the agent passes along and approves it; an approval left untouched for 24 hours lapses. (Confirmed by vendor 6)
Stripe's notice, in its words: "Starting in December, Stripe MCP will stop accepting full-access secret keys and restricted API keys without the Agent tag." The deadline it gives is November 30, 2026. (Confirmed by vendor 6)
Meta's connector rules allow read access to financial data, but for now Meta won't approve new connector tools that shift money, transfers from one financial account to another being its example. (Confirmed by vendor 3)
Under Stripe's services agreement, data you let Stripe pull from other providers must not include protected health information. (Confirmed by vendor 10)
Muse trains Meta's AI on your interactions unless you switch that off under Data controls, and connector data counts as part of those interactions. (Confirmed by vendor 5)

What Muse can read and change

Stripe's server gives every client one general tool for reading and one for writing, plus a published list of the API methods those two tools reach. The table follows that list. Neither Meta nor Stripe says whether Muse's Stripe connector offers the whole list or a narrower set. (Unverified)

What	In the connector?	Label and source
Customers	List, look up, create and update; deleting a customer isn't on Stripe's list (Confirmed by vendor 6)	Confirmed by vendor 6
Charges, PaymentIntents and saved payment methods	Read only (Confirmed by vendor 6)	Confirmed by vendor 6
Refunds	Read, and create a refund, which goes through Stripe's confirmation step (Confirmed by vendor 6)	Confirmed by vendor 6
Invoices and invoice items	Read, create, update, finalize, void or mark uncollectible; credit notes are read only (Confirmed by vendor 6)	Confirmed by vendor 6
Subscriptions	Read, create, update and cancel; schedules and subscription items are read only (Confirmed by vendor 6)	Confirmed by vendor 6
Products, prices, coupons and promotion codes	Read, create and update; coupons can also be deleted (Confirmed by vendor 6)	Confirmed by vendor 6
Payment links and Checkout Sessions	Read and create; payment links can also be updated (Confirmed by vendor 6)	Confirmed by vendor 6
Disputes	Read and update (Confirmed by vendor 6)	Confirmed by vendor 6
Payouts, balance, balance transactions and transfers	Read only (Confirmed by vendor 6)	Confirmed by vendor 6
Webhook endpoints, customer portal settings, tax settings and tax registrations	Create or update, so account setup can change (Confirmed by vendor 6)	Confirmed by vendor 6
Treasury money tools (`send_money`, `transfer_money`)	Stripe lists them as public preview tools on its server (Confirmed by vendor 6) We found nothing saying Muse offers them (Unverified)	Confirmed by vendor 6

The server also has tools for account details, analytics and reports, searching Stripe's documentation, planning an integration and forming a company through Stripe Atlas. (Confirmed by vendor 6) Stripe's developer blog adds that agents can now send money to other people through Stripe Treasury. (Confirmed by vendor 8)

Connecting it

In Muse, connectors live under Settings, then Connectors: tap Connect, read what's shown, tap Continue and finish any sign-in steps. (Confirmed by vendor 2) When an MCP client uses OAuth, Stripe opens its consent page, where you pick one or more live accounts or sandboxes and give each environment its own permissions. (Confirmed by vendor 6) Stripe's blog says that screen lets you choose read or write access per resource. (Confirmed by vendor 8) Muse is for people 18 and over, and its terms make you alone responsible for which services you link and what you let them do. (Confirmed by vendor 4) Muse's launch covers two countries: Canada and the US. (Confirmed by vendor 1)

What we couldn't pin down:

Which sign-in Muse uses. Stripe recommends OAuth for interactive clients, because it lets you authorize and revoke without sharing a key, and keeps agent API keys for autonomous clients that can't do OAuth. (Confirmed by vendor 6) Nothing from Meta or Stripe says which of the two the listed Stripe connector in Muse relies on. (Unverified)
What the consent screen offers Muse. We haven't seen which resources and permissions it shows for Muse, or whether a read-only choice appears. (Unverified) Meta asks connector makers using OAuth to offer a read-only option where they can. (Confirmed by vendor 3)
Fees. We found no statement from Stripe or Meta about any charge for MCP use beyond your usual Stripe pricing. (Unverified)

Permissions and approvals

Three things can stop a Stripe action before it lands: Stripe's scope settings, Stripe's own confirmation or approval checks, and Muse's approval prompts.

A Stripe administrator can turn MCP access on or off for the whole team in the Dashboard, with separate switches for live mode and sandboxes. (Confirmed by vendor 6)

Stripe's blog says that when an agent connected through OAuth attempts a live-mode refund or payout, Stripe makes you confirm it before money leaves the account, and that this check applies even when you've told your AI client to stop asking permission. (Confirmed by vendor 8) After you approve, you tell the agent to retry. (Confirmed by vendor 6) Stripe's reference asks you to keep your client's tool-approval setting on, and warns about prompt injection when its server runs alongside other MCP servers. (Confirmed by vendor 6)

Agent API keys work differently. They're restricted keys tagged for an AI agent, and they fall under Stripe's approval rules, which send sensitive actions to a designated reviewer. Under Settings, then Approvals, you can set conditions such as a refund over a given amount, and by default nobody, person or agent, approves their own request. Unapproved requests expire after 14 days. (Confirmed by vendor 7 8) Stripe's two pages differ on what its starter rules for agent keys cover: the key guide says payouts, refunds and account configuration changes; the blog says refunds, payouts and outbound transfers. (Conflicting 7 8)

Meta sorts connector tools into reads, writes and sensitive writes. Reads and ordinary writes ask at first use and can be set to Always allow; sensitive writes, the ones that are consequential or can't be undone, such as a purchase, ask every time, and a changed detail such as the amount or recipient needs a fresh approval. A payment action must never be tucked inside a read tool. (Confirmed by vendor 3) We couldn't find how Meta classed Stripe's single write tool, which covers both a customer's email change and a refund. (Unverified) Leave anything that writes to Stripe on ask.

Muse's terms tell you not to let it carry out financial transactions or other state-changing actions without a human review and approval first. (Confirmed by vendor 4)

Disconnecting

Removing Stripe under Settings, then Connectors in Muse stops further exchanges, but what Muse already used can remain in its memories and your chat history; you can ask Muse to forget interactions. (Confirmed by vendor 2)

On the Stripe side, an OAuth connection is listed under OAuth sessions in your Dashboard user settings, with Revoke access in each session's overflow menu. An administrator can do the same for a colleague under Team and security, including Revoke all. Revoking applies only to the account, organization and environment you're viewing, so a session can stay live elsewhere. (Confirmed by vendor 6) If an API key was used instead, expire it or rotate it on the API keys page; an expired key can't make calls, and a rotated key's predecessor can keep working for up to seven days. (Confirmed by vendor 7) When you pull a connector's access, Meta's rules say its maker has to delete your data. (Confirmed by vendor 3)

What happens to your data

Meta and AI training. Muse's privacy policy turns AI training on from your first use and includes information from connectors in what it trains on. (Confirmed by vendor 5) The terms grant Meta rights over content that comes in through linked services, plus a separate right to use it for improving AI at Meta; the opt-out sits under Data Controls. (Confirmed by vendor 4) A Stripe account holds customer names, emails, addresses and payment history, so decide on this before connecting.
What Muse sends Stripe. Meta says Muse sends a connector only what a task needs. (Confirmed by vendor 2) Meta's rules bar connector makers from selling that data, using it for unrelated ads or training models on it. (Confirmed by vendor 3)
What Stripe says. Stripe's privacy policy lists training artificial intelligence models, to run its services and guard against fraud, among the ways it uses personal data. (Confirmed by vendor 11) We found no Stripe statement about requests arriving from Muse in particular, or about how Meta's no-training rule for connector makers applies to Stripe. (Unverified)

Stripe's own MCP servers

There are other ways to reach Stripe from an AI tool besides Meta's listed connector.

Stripe documents its server for Claude and ChatGPT, where it offers official connectors, and for Cursor, Claude Code, Codex and VS Code. Any MCP client can point at mcp.stripe.com. (Confirmed by vendor 6)
A platform running Stripe Connect has to use an agent API key to work on its connected accounts, because OAuth isn't supported for that. (Confirmed by vendor 6)
Setting Stripe up yourself in Muse would be a custom connector: Meta doesn't review those, and Muse files their sign-in details in a vault it names the Secure Credentials Store. (Confirmed by vendor 2) A key pasted there must be an agent-tagged key after Nov 30.

Software	In Meta's launch-post connector list?	How else it connects	Label and source
Stripe	Yes (Confirmed by vendor 1)	Stripe's MCP server, reached from a different AI client by OAuth or with an agent key (Confirmed by vendor 6)	Confirmed by vendor 1 6
Zapier	Zapier's docs describe connecting it from Muse's Connectors settings; Meta's launch post doesn't name it. (Confirmed by vendor 14)	Zapier is the bridge	Confirmed by vendor 1 14

Zapier has a Stripe app, with ready-made Zaps such as logging new Stripe sales in Google Sheets or posting payment alerts to Slack. (Confirmed by vendor 15) On Zapier's side, each MCP call that succeeds costs two of your plan's tasks. (Confirmed by vendor 14)

Risks to keep a person on

Refunds and bills land on real customers

A Stripe refund can only return to the payment method used for the original charge; it can't be redirected to a different card or bank account. (Confirmed by vendor 12) Before you approve Stripe's confirmation link, check the customer, the charge, the amount and whether the refund is full or partial. Treat a new subscription, a finalized invoice or a fresh payment link the same way, since each one ends with a customer seeing your business name next to a price.

The wrong customer

Muse can create and edit customer records and subscriptions, and cancel subscriptions. (Confirmed by vendor 6) Two customers with the same name, or one person with two Stripe records, is a common way to refund, bill or cancel the wrong one. Ask Muse to show the customer's email and the last few charges before it acts, and give it the exact amount rather than "the usual".

Disputes and chargebacks

Stripe's server can update a dispute, and in Stripe's API, updating a dispute sends the evidence to the bank straight away unless the request says to stage it. Stripe's dispute guide says you get one chance to respond and can't edit it or add files afterward. (Confirmed by vendor 6 13) Keep dispute responses with a person who has read the whole file.

Keys and who holds them

Stripe's key guide says a secret key has unrestricted permissions across the API, that Stripe doesn't recommend them and suggests moving to restricted keys, and that a fraudulent actor holding one can harm your business. It also says not to pass keys around by email or chat. (Confirmed by vendor 7) Never paste a live key into a Muse chat. If one has been shared, rotate it.

Agents' actions are yours

Stripe's agreement makes you solely responsible for each action an AI agent takes through your account and treats those actions as legally binding on you. (Confirmed by vendor 10) Muse's terms put the risk of financial loss from its payments and transfers on you, warn that some transactions can't be reversed, and say Muse holds no license as an adviser, broker or money transmitter and is neither a fiduciary nor a financial institution. (Confirmed by vendor 4)

Trust and client money

Law firms and anyone else holding other people's money in trust shouldn't let an agent refund, transfer or pay out from those funds. Our guide for small law firms covers trust accounts and the payment tools built for them. We didn't find anything from Stripe about trust or IOLTA accounts connected through MCP. (Unverified)

Health information

Section 4.5 of Stripe's agreement bars PHI from the third-party data you give Stripe access to, and leaves the liability with you if some gets through. (Confirmed by vendor 10) Keep diagnoses, procedure names and patient notes out of invoice descriptions and customer fields Muse writes to. The dental and medical offices guide covers the health-privacy side of the software that trade uses.

Subscriptions sold online

When you sell online with a negative option feature, the kind of plan that keeps billing until the customer acts, federal law requires you to disclose all material terms clearly before taking billing details, get the customer's express informed consent before charging, and give a simple way to stop the recurring charges. (Confirmed by Congress 16) The FTC enforces that as a violation of one of its trade rules, and state attorneys general can sue for an injunction after notifying the FTC. (Confirmed by Congress 17 18) If Muse sets up a subscription product or a payment link for one, check the checkout wording yourself. Our online stores guide covers the current state of the FTC's negative option rule.

What Muse remembers

Disconnecting doesn't wipe what Muse already holds in memory or chat history, and training stays on until you turn it off. (Confirmed by vendor 2 5) Set both before connecting a live Stripe account.

Treat this page as a summary of published sources, not as legal, payments compliance or financial advice. Stripe's and Meta's screens and rules may have changed since we read them, so check the current versions.

Trade guides that cover Stripe

These trade guides show how Stripe fits with the other software each trade runs:

FAQ

Can Muse refund a customer?

Creating a refund is on the list of methods Stripe's server supports, and Stripe asks a person to approve it through a link first. (Confirmed by vendor 6) Whether Muse's connector exposes refunds isn't documented beyond Stripe's post. (Unverified)

Can Muse pay out or send money from my Stripe balance?

Payouts are read only in Stripe's method list; sending money is limited to Treasury tools Stripe labels public preview. (Confirmed by vendor 6) For the time being, Meta's rules say it won't approve new connector tools that shift money between accounts. (Confirmed by vendor 3)

Do I have to do anything before Nov 30, 2026?

Only if something reaches Stripe's MCP server with a full-access secret key or a restricted key lacking the Agent tag. Stripe's options are a new agent API key or reconnecting with OAuth; old keys get a 401 error after the deadline. (Confirmed by vendor 6)

Is my Stripe data used to train Meta's AI?

By default, yes. Turn it off in Data controls. (Confirmed by vendor 5)

Changes to this page

Date	What changed	Sources
Oct 28, 2026	First published.	All sources listed on this page

Found a mistake or a newer source? Send it through Corrections, with a link to the source, and we'll recheck the claim and record the change here.

Sources

Source 1: Meta “The Future Is for Everyone: Muse for Small Business.” about.fb.com Confirmed by vendor Checked Oct 28, 2026. First posted Sept 29, 2026; Meta revised it Oct 8. Stripe appears in the post's list of connectors; the post doesn't describe what the Stripe connector does. Muse is available only to US and Canadian users.
Source 2: Meta Help Center “How Muse works with Connectors.” meta.com Confirmed by vendor Checked Oct 28, 2026. The article read "Updated: 7 weeks ago" when we opened it.
Source 3: Meta (Muse developer platform) “Muse connector guidelines.” platform.muse.ai Confirmed by vendor Checked Oct 28, 2026. Covers what Meta asks of connector makers; used here: 3.1 through 3.4 (read-only option, how tools are classed, approval choices), 4.2 (data use) and 4.6 (finance connectors).
Source 4: Meta “Muse Supplemental Terms of Service.” muse.ai Confirmed by vendor Checked Oct 28, 2026. Last updated Sept 8, 2026. Sections used: 1 (age), 2.3 (license), 6 (connected services), 7.6 (oversight) and 7.7 (financial actions).
Source 5: Meta “Muse Privacy Policy.” muse.ai Confirmed by vendor Checked Oct 28, 2026. Effective Sept 17, 2026; opened with a page-reader tool. Used for the AI-training default and the Data controls switch.
Source 6: Stripe Docs “Model Context Protocol (MCP).” docs.stripe.com Confirmed by vendor Checked Oct 28, 2026. Stripe's reference for its MCP server at mcp.stripe.com: sign-in methods, sessions, the tool list, supported API methods and human confirmation. The page doesn't mention Muse.
Source 7: Stripe Docs “API keys.” docs.stripe.com Confirmed by vendor Checked Oct 28, 2026. Sections on agent-tagged keys, secret and restricted keys, and expiring or rotating a key.
Source 8: Stripe Dot Dev Blog “Your AI agent can move money in Stripe - here's how to stay in control.” stripe.dev Confirmed by vendor Checked Oct 28, 2026. Dated Oct 21, 2026, by Daniel Wood.
Source 9: Stripe on LinkedIn “New: manage your business with Stripe and Muse from Meta..” linkedin.com Confirmed by vendor Checked Oct 28, 2026. Stripe's own company post of Sept 29, 2026. Its link leads to the MCP page in source 6.
Source 10: Stripe “Stripe Services Agreement: General Terms.” stripe.com Confirmed by vendor Checked Oct 28, 2026. Last modified Sept 28, 2026; we used sections 1.7 (AI Agent), 4.5 (Third Party Data User Provides) and the defined terms for AI Agent and Protected Health Information.
Source 11: Stripe “Privacy Policy.” stripe.com Confirmed by vendor Checked Oct 28, 2026. Last updated April 28, 2026. Covers Stripe as a whole and doesn't mention Muse.
Source 12: Stripe Docs “Refunds.” docs.stripe.com Confirmed by vendor Checked Oct 28, 2026.
Source 13: Stripe Docs “Respond to disputes; Update a dispute (API reference).” docs.stripe.comAlso: https://docs.stripe.com/api/disputes/update Confirmed by vendor Checked Oct 28, 2026.
Source 14: Zapier “Connect Zapier MCP to Muse.” docs.zapier.comAlso: https://docs.zapier.com/mcp/overview/usage Confirmed by vendor Checked Oct 28, 2026.
Source 15: Zapier “Stripe integrations.” zapier.com Confirmed by vendor Checked Oct 28, 2026.
Source 16: Office of the Law Revision Counsel (uscode.house.gov) “15 U.S.C. 8403, Negative option marketing on the Internet.” uscode.house.gov Confirmed by Congress Checked Oct 28, 2026. Section 4 of the Restore Online Shoppers' Confidence Act, Pub. L. 111-345, 124 Stat. 3620 (Dec. 29, 2010). The site listed Public Law 119-136, enacted Oct. 22, 2026, as the latest law reflected.
Source 17: Office of the Law Revision Counsel (uscode.house.gov) “15 U.S.C. 8404, Enforcement by Federal Trade Commission.” uscode.house.gov Confirmed by Congress Checked Oct 28, 2026. Section 5 of the same Act. Read alongside section 8401 (findings) and 8402.
Source 18: Office of the Law Revision Counsel (uscode.house.gov) “15 U.S.C. 8405, Enforcement by State attorneys general.” uscode.house.gov Confirmed by Congress Checked Oct 28, 2026.