On Oct 21, Anthropic opened a waitlist preview of Claude Duet, a proactive agent app it says it built "for professionals and small business owners." It sends a morning brief, checks your connected apps every few hours and works in its own browser. Shopify and Stripe were both there on day one.
Before you connect it, or any other Always On Agent, to your store and your payments, sit down for 30 minutes and draw one map. Every money action the agent could reach, where it runs, and who says yes.
Same agent, same refund, two different rules.
Why one map
Here is the catch in the fine print. The same agent meets two different money rules depending on which system the action runs in.
In Shopify, per the Shopify connector for Claude help page, a connected AI tool cannot issue refunds, cancel or capture orders, mark orders paid, process returns, or create and adjust gift cards. Shopify says: "These actions are blocked even when you approve write access."
In Stripe, refunds are allowed. Stripe says that through Stripe MCP, Duet users can send invoices and payment links, manage products and prices, analyze revenue and issue refunds. Purchases go through Link, approved by the user and paid with a virtual card.
So a customer asks for their money back, and the answer depends on where the agent tries it. Find out before the first request comes in.
The map, in seven moves
Get a notepad and whoever handles refunds today.
1. List every money action
Write down everything the agent could touch: refunds, discounts, price changes, invoices, payment links, subscription cancels, purchases, gift cards. Next to each one, write the system it lives in. Shopify, Stripe, your card, somewhere else.
2. Cross off what the platform already blocks
On Shopify's connector, refunds, cancels, captures, returns and gift cards are already off. Duet itself has hard limits too. Anthropic says it shows you the action and waits before it sends a message, makes a payment, signs a document or deletes anything, and some actions stay off limits even with approval, like trading securities or moving money between accounts.
Don't build your own gate for something that's already blocked. Spend the time on what's allowed.
3. Put approval on what's left
Most of what's left lives in Stripe. Stripe's two-party approvals keep default approval rules for agent-tagged keys on "Refund is created" and "Subscription is canceled." You can add conditions on amount, actor and rate, require approval, or block outright. A user can't approve their own request.
If your agent connects to Stripe through user OAuth instead, Stripe MCP asks a human to confirm refunds and outbound payments through a link, and unapproved requests expire after 24 hours. Neither Anthropic nor Stripe says which path Duet's connector uses, so check both settings. Then name the person who clicks the link, and make it someone other than the person running the agent.
4. Give the agent its own seat on each side
On Shopify, writes depend on the staff account the agent acts through. Give it a dedicated staff account with only the permissions it needs. On Stripe, use an agent-tagged key with only the permissions it needs, or a separate OAuth session you can revoke. We wrote more on why each Always On Agent gets its own seat. Before you hand out new keys, audit the logins your agents already hold.
5. Cap purchases the way Walmart does
Walmart published the shopper side of this on Oct 21. Its Agent Profiles give each agent its own profile, list its purchases separately, require approval per purchase or a spending limit the customer sets, and can be revoked any time. Agents never receive card data or change payment methods. Walmart's terms say: "Agents must not take actions beyond what the shopper intends." Profiles launch within the next month.
Copy that for your own agent. Approval per purchase by default, a small cap if you want speed, one-time cards through Link, and a purchase list you read every week.
6. Swap your Stripe keys by Nov 30
This one has a date on it. Stripe's MCP docs say: "Starting in December, Stripe MCP will stop accepting full-access secret keys and restricted API keys without the Agent tag." Stripe asks for the migration by November 30.
If any agent you run talks to Stripe MCP with a full secret key or an untagged restricted key, it stops working in December. Move it to an agent key or OAuth now, and the approval rules from move 3 come with it.
7. Send theme edits through a copy
Shopify's connector can't edit, publish or delete your live theme. It can edit a duplicate, and you publish. Keep it that way. A person looks before customers do.
Then log the stops
Keep a record of every action the agent was blocked from or asked you about. Stripe keeps an approval history. Read it with your weekly purchase list. Those stops tell you where the map needs a new line.
What this doesn't tell you
Duet is a waitlist research preview, and its safety mechanisms are Anthropic's own claims. The Shopify limits sit on the Claude connector page, and other agents may reach your store through other apps. Help pages change, so check both again before you connect.
It does give you one page that says what your agent can do with money, where, and who approves it. That's the same idea as your agent access policy, pointed at your own agent instead of visiting ones.
This week
Draw the map. Cross off the blocked actions. Turn on Stripe's refund and cancel approval rules and name a reviewer. Set up the agent's own Shopify staff account and its own Stripe key. Put Nov 30 on the calendar.
If you want that map built into how your store and your agents run, Start your build.
Linked sources
- Anthropic: Claude Duet (2026-10-21)
- Stripe Newsroom: Anthropic and Stripe (2026-10-21)
- Shopify Help Center: Shopify connector for Claude
- Stripe Docs: Stripe MCP
- Stripe Docs: Set up two-party approvals
- Walmart: Making it possible for agents to shop on behalf of customers (2026-10-21)
- Related article: Write your store's agent access policy this week
- Related article: Give each Always On Agent its own seat, not your login
- Related article: Audit your agent's logins in 20 minutes, before your bank does it for you
Get our Articles and posts by email.
Up to one email a day with new Articles and posts from 22atlas.com and sean-weldon.com, plus occasional news about 22Atlas services.
Also on the desk
Technique
Write your store's agent access policy this week
BCG surveyed big retailers and found most have already picked a stance on outside shopping agents. Pick yours on purpose, draw the data line, and put it on one page.
Technique
Give each Always On Agent its own seat, not your login
Google's new Gemini coworker agent gets its own account, its own audit trail and a spend cap that pauses it. You can set up your agents the same way today on the tools you already pay for. Five moves.
Technique
Audit your agent's logins in 20 minutes, before your bank does it for you
Banks have started blocking AI agents that sign in with the owner's password, and Chase now puts agent errors on the customer. List every login your agent holds and move each one to the right kind of access.