Skills

Skill 8 of 10

Stripe Pay

Helps users send funds to another Stripe business, transfer money to a Stripe Profile handle or network ID, or ask whether an agent can pay a Stripe business.

2 minutes · 480 words · 3 sections

Install

$ npx skills add stripe/ai --skill stripe-pay

$ npx skills add stripe/ai

» /plugin marketplace add stripe/ai

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Use stripe pay to send money from the authenticated Stripe business to another Stripe business identified by a Stripe Profile (opens in a new tab) handle, for example @recipient.

The stripe pay command is for business-to-business money transfers. Both the sender and the receiving business must have a Stripe Profile (opens in a new tab). In addition:

The sender needs a funded financial account (opens in a new tab).
The receiver needs an eligible transfer destination linked to their Stripe Profile (opens in a new tab).

If the user needs details about financial accounts, read Money Management (opens in a new tab). The command resolves the recipient’s payout configuration, which can route the payout to an attached financial account or linked bank account, and reports the fee and delivery timing before confirmation. Don’t assume that a transfer is free or instant.

Safety Rules

Don’t send money unless the user explicitly asks you to make the transfer.
Before running a command that can send money, show the exact stripe pay ... command you plan to run and get confirmation.
Use --agent or --json first so the user can review the transfer details.
Don’t pass -y or --yes until after the user confirms the reviewed transfer.
Don’t guess at the user’s intent. Don’t guess at the username, financial account ID, amount, currency, internal note, memo, or any other detail. Always confirm with the user.
Don’t print full API keys back to the user.

Choose the workflow

Read the documentation to accomplish your goal. You must read the relevant page before taking action:

Goal	Documentation
Find or verify a recipient when the user doesn’t provide an exact Stripe Profile handle or network ID	Use Stripe Directory with AI agents (opens in a new tab)
Review, send, handle approval, resume, or dry-run a transfer	`stripe pay` CLI reference (opens in a new tab)
Create or manage a Stripe Profile, including a recipient’s transfer destination	Stripe Profile (opens in a new tab)
Set up or understand an eligible financial account	Money Management (opens in a new tab)

Handle setup errors

Don’t continue the transfer when stripe pay reports missing setup. Explain what’s missing and give the user the corresponding next step. Before explaining how to resolve the error, read the documentation for the missing requirement in the workflow table:

If the sender is missing a Stripe Profile (opens in a new tab), tell the user to create one.
If the sender is missing an eligible financial account, tell the user to set up Global Payouts with an eligible financial account.
If the sender is missing both requirements, tell the user to complete both setup steps before trying the transfer again.
If the recipient doesn’t have an eligible transfer destination linked to their Stripe Profile, tell the user that the recipient must complete that setup before the transfer can proceed. Don’t retry the transfer until the recipient’s setup is corrected.
If the recipient is missing or invalid, read and follow the Stripe Directory agent workflow (opens in a new tab). If the user can provide the recipient’s exact Stripe Profile handle or network ID, ask them for it.

For sender setup, direct the user to the relevant Dashboard page:

To create a Stripe Profile, open https://dashboard.stripe.com/profiles (opens in a new tab) and click Get started.
To set up Global Payouts with an eligible financial account, open https://dashboard.stripe.com/balance/financial-accounts (opens in a new tab) and click Get started.

About this skill

Trigger

Helps users send funds to another Stripe business, transfer money to a Stripe Profile handle or network ID, or ask whether an agent can pay a Stripe business. Use Stripe Directory to find or verify a recipient when the user doesn't provide an exact Stripe Profile handle or network ID.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Allowed tools: Bash(stripe directory *)Bash(stripe pay *)Bash(stripe whoami *)
Also published for: Agent Plugins, Claude, Codex, Cursor, Grok — collapsed into this chapter because the copies are the same skill.
Source: skills/stripe-pay/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/stripe/ai, branch main, last pushed 23 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

10 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Duplicates collapsed

50 mirror copies folded into their canonical skill — republished for Agent Plugins, Claude, Codex, Cursor, Grok. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from the awesome-design-md registry — hue 278°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: sohne-var is not available to us; set in Inter.
Body: sohne-var is not available to us; set in Inter.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “stripe pay”, a leading h1 that duplicated the skill title.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Stripe, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /stripe/ai.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Safety Rules

Don’t send money unless the user explicitly asks you to make the transfer.

Before running a command that can send money, show the exact stripe pay ... command you plan to run and get confirmation.

Use --agent or --json first so the user can review the transfer details.

Don’t pass -y or --yes until after the user confirms the reviewed transfer.

Don’t guess at the user’s intent. Don’t guess at the username, financial account ID, amount, currency, internal note, memo, or any other detail. Always confirm with the user.

Don’t print full API keys back to the user.

Choose the workflow

Read the documentation to accomplish your goal. You must read the relevant page before taking action:

Goal	Documentation
Find or verify a recipient when the user doesn’t provide an exact Stripe Profile handle or network ID	Use Stripe Directory with AI agents (opens in a new tab)
Review, send, handle approval, resume, or dry-run a transfer	`stripe pay` CLI reference (opens in a new tab)
Create or manage a Stripe Profile, including a recipient’s transfer destination	Stripe Profile (opens in a new tab)
Set up or understand an eligible financial account	Money Management (opens in a new tab)

Handle setup errors

If the sender is missing a Stripe Profile, tell the user to create one.

If the sender is missing an eligible financial account, tell the user to set up Global Payouts with an eligible financial account.

If the sender is missing both requirements, tell the user to complete both setup steps before trying the transfer again.

If the recipient doesn’t have an eligible transfer destination linked to their Stripe Profile, tell the user that the recipient must complete that setup before the transfer can proceed. Don’t retry the transfer until the recipient’s setup is corrected.

If the recipient is missing or invalid, read and follow the Stripe Directory agent workflow. If the user can provide the recipient’s exact Stripe Profile handle or network ID, ask them for it.

For sender setup, direct the user to the relevant Dashboard page: