Stripe Pay for AI agents: the approval rules

Stripe now has a command called `stripe pay` that sends money from one Stripe business to another, using the other business's Stripe Profile handle instead of bank details. Stripe also published a skill file that tells AI coding agents how to use it. That means an agent running on your machine can, in principle, pay a supplier. For a small business, the useful questions are which steps a person must still take, and what limits should sit around the agent before it touches a real balance.

We read Stripe's stripe pay CLI reference, the Stripe Directory docs and the stripe-pay agent skill on GitHub on October 30, 2026. Everything below about how the tool behaves comes from those pages. The workflows and limits further down are our own view of how we would set it up.

Stripe Pay is a preview tool for eligible US and UK businesses. It moves money between Stripe businesses in the same currency, in USD, GBP or USDC. Stripe's own instructions for agents say the agent should show the transfer first, wait for the person to confirm, and never guess the recipient or the amount. Those rules are a good floor. For a business paying real bills, we would add a short list of allowed recipients, a cap per transfer and per day, and a record of every transfer written back to your books.

Both sides need a Stripe Profile. The sender needs a funded Stripe Treasury financial account. The recipient needs either a Treasury financial account or a bank account that can receive payouts, linked to its profile. If either side is missing that setup, the transfer cannot go through, and Stripe's skill tells the agent to stop and explain the problem rather than keep retrying.

You sign the command line in with `stripe login`, and Stripe's reference says to run `stripe whoami` before sending, so you know which account the money would leave from. That check matters more than it looks. Many businesses have a test account, a live account and sometimes a second company on the same login. An agent that sends from the wrong one makes a mistake that is hard to undo.

A recipient is named by a handle, such as @supplier, or by a network ID that starts with `profile_`. If you do not have the exact handle, the docs point to Stripe Directory, which you install as a CLI plugin and search with `stripe directory search`. The directory covers Stripe Apps, Stripe Projects providers, paid endpoints for machines and businesses on Stripe's network.

The Directory docs are firm on one point: when a search returns more than one possible match, show the short list and let the person choose. The agent should not pick the closest name. Two businesses can have similar names, and a payment to the wrong one is a refund request to a stranger.

The stripe-pay skill lists the rules an agent should follow. In plain terms:

1. 1Do not send money unless the person clearly asked for it.
2. 2Show the exact `stripe pay` command and get a yes before running it.
3. 3Run it first with `--agent` or `--json`, so the person can read the transfer details.
4. 4Do not add `--yes`, which skips the final prompt, until the person has confirmed the recipient, amount, currency and the account the money leaves from.
5. 5Do not guess the handle, the financial account, the amount, the currency, the internal note or the memo.
6. 6Do not print full API keys.

The command also shows the fee and delivery timing before you confirm, and the skill tells the agent not to assume a transfer is free or instant. There is a `--dry-run` option that checks the whole flow without creating or sending anything. We would use it on every new recipient before the first real payment.

Stripe's rules cover one transfer at a time with a person watching. They do not know your business. They do not know that a supplier is only paid against an approved invoice, that a new supplier needs a second person to sign off, or that nothing over a set amount should leave on a Friday afternoon. They also rely on the person reading the summary carefully. After the fortieth approval in a month, most people click yes without reading.

So the rules that matter most have to live outside the command, in the workflow that decides when the agent is even allowed to propose a payment. We cover the general pattern in our post on human approval gates for finance AI agents. Here is how we would apply it to Stripe Pay.

These are examples of how we would set this up. None of them is a client result.

• Pay an approved bill. A bill gets approved in your accounting tool. The agent matches it to a supplier whose Stripe handle is already stored on the supplier record, runs the transfer in review mode and posts the recipient, amount, fee and timing to the approver in Slack or email. Only after the approver says yes does the agent send, and it writes the transfer ID back to the bill so the books match.
• Pay a partner commission. At month end the agent totals what each partner earned from your own records, prepares one transfer per partner and sends the whole batch to a person for review. Anything that changed from last month by more than a set percentage is flagged in the summary.
• Move money between your own companies. If you run two businesses that both have Stripe Profiles, the agent can prepare the transfer between them on a schedule, with the same review step, so the owner does not have to log in to two dashboards.

In each case we would add four limits of our own:

• An allowed recipient list. The agent can only pay handles already saved on a supplier or partner record. Adding a new recipient is a separate step done by a person, never by the agent.
• Caps. A maximum per transfer and per day, checked before the agent even prepares the command.
• A different approver. The person who approves is not the person who asked the agent to pay, for anything over a set amount.
• A written record. Every proposed transfer, every approval and every result goes into a log with who, what and when. If the same bill is processed twice, the record stops a second payment. We explain that check in our post on stopping duplicate actions from AI agents.

If most of your suppliers are not on Stripe, there is no one to pay by handle yet, and a normal bill-pay tool or your bank will do more. If you send a handful of payments a month, a person paying them in the dashboard is faster than building and testing an agent around it. If you need to pay in a different currency from your balance, or you operate outside the US and UK, the preview does not cover you today. And if you do not already have a Treasury financial account, setting one up only for this is a big step for a small gain.

It is also a preview. Commands and rules can change, so anything we build on it gets checked again before it touches live money, and we keep a manual way to pay every recipient in case the tool changes.

We build agents that prepare payments and leave the decision with a person through our AI agents service, and we connect Stripe to accounting, CRM and approval tools through systems integration. Our Stripe integration page covers the wider set of Stripe workflows we connect. If you want to know whether paying suppliers this way makes sense for you, start with a free automation audit and we will look at who you pay, how often and what approvals you already have.

OrchestriAI is an independent implementation provider. Product names are used for identification only. OrchestriAI is not affiliated with, endorsed by, or sponsored by Stripe. This article summarizes Stripe's public documentation as read on October 30, 2026, and is not financial or legal advice. Check Stripe's current docs and your own controls before letting any tool move money.