AutoGineer
Generated banner for Stripe Pay
Generated logo for Stripe Pay

Stripe Pay

StripeOfficialPublished by Stripe

  • Skill
  • Workflow
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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 description by Stripe

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The stripe-pay skill provides a structured workflow for agents to initiate and manage financial transfers between Stripe-enabled businesses. It integrates with the Stripe CLI to verify recipients, check transfer eligibility, and execute payments. The skill emphasizes safety by requiring explicit user confirmation before any transaction, supporting dry-runs for review, and providing clear guidance on resolving setup requirements for both senders and recipients.

What it does

  • Transfers funds between Stripe businesses using Profile handles or network IDs
  • Verifies recipient details using the Stripe Directory
  • Displays fee and delivery timing estimates prior to transaction confirmation
  • Provides payment links as a fallback when direct transfers are unavailable
  • Guides users through resolving missing setup requirements for financial accounts or profiles
  • Enforces safety protocols by requiring explicit user approval for all financial actions

When to use it

  • When a user needs to send money to another business via their Stripe Profile
  • When you need to verify a recipient's identity or handle before initiating a payment
  • When you need to check if a specific Stripe business can receive funds
  • When troubleshooting failed transfers due to missing financial account or profile configurations

Advantages

  • Ensures financial safety through mandatory user review and confirmation steps
  • Streamlines the transfer process by integrating directory lookups and payment execution
  • Provides clear error handling and actionable steps for missing account requirements
  • Supports dry-run capabilities to preview transfer details before final execution

Usage examples

“Can I send 500 USD to @acme-corp?”
The agent will verify the recipient, check for eligible financial accounts, and present the transfer details including fees and timing for your approval.
“Help me pay the business with network ID ni_12345.”
The agent will initiate the transfer workflow, validate the recipient, and request your confirmation before executing the payment.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/stripe/stripe-pay/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip stripe-pay.zip -d .agents/skills

Documentation by Stripe

stripe pay

Use stripe pay to send money from the authenticated Stripe business to another Stripe business identified by a Stripe Profile handle, for example @recipient.

For the financial-account transfer workflow documented here, both the sender and the receiving business must have a Stripe Profile. In addition:

If the user needs details about financial accounts, read Money Management. In this workflow, 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.

Eligible transfers take priority. If the sender has no eligible financial account or the recipient has no eligible transfer destination, stripe pay offers the recipient’s configured payment link, if available. Insufficient funds and currency errors alone don’t trigger this fallback.

For status: payment_link_available and transfer_sent: false, give the user payment_link_url to complete payment in Checkout, where they must enter the amount and check the currency. Transfer arguments don’t carry over. Don’t report payment success from returning or opening the URL, or rerun with --yes to pay the link.

Safety Rules

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

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

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

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

  5. 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.

  6. 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:

GoalDocumentation
Find or verify a recipient when the user doesn’t provide an exact Stripe Profile handle or network IDUse Stripe Directory with AI agents
Review, send, handle approval, resume, or dry-run a transferstripe pay CLI reference
Create or manage a Stripe Profile, including a recipient’s transfer destinationStripe Profile
Set up or understand an eligible financial accountMoney Management

Handle setup errors

If stripe pay reports missing setup instead of returning a payment link, don’t continue the transfer. 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, 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:

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "stripe-pay", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools, Needs an API key

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Stripe
Publisher
Stripe (Official)
Source
stripe/ai · skills/stripe-pay · commit 38fa045
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
stripe/ai, stripe/ai, stripe/ai, stripe/ai, stripe/ai

AutoGineer is not affiliated with or endorsed by Stripe or Stripe.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download stripe-pay.zip