Stripe Pay Explained: Free B2B Transfers, Fees, and AI Agent Payments

Key Takeaways

• Stripe Pay lets businesses pay another business using a Stripe Profile handle, such as @recipient, backed by an eligible funding account and receiving destination.
• Free, instant transfers have conditions. The actual destination, quoted fee, and delivery estimate matter more than the headline.
• A normal Stripe payments balance is different from a Treasury financial account. Accepting customer payments does not automatically complete the setup needed for business transfers.
• AI agents can help prepare and execute financial workflows, with permissions and approval requirements governing sensitive actions.
• Stripe Pay serves a different purpose from Checkout. Customer purchases, vendor transfers, and international payouts require different product choices.

Stripe’s official payment skill and Treasury documentation explain these distinctions.

What Is Stripe Pay?

Stripe Pay is a business-to-business payment workflow that identifies recipients through their Stripe Profiles. Instead of repeatedly entering banking details, a sender can identify the intended business by its handle or profile network ID.

Both businesses need a Stripe Profile. The sender also needs a funded financial account, while the recipient needs a supported receiving destination associated with its profile. Stripe resolves that destination as part of the payment process.

The underlying opportunity predates the latest CLI documentation. In its April 29, 2026 announcement, Stripe introduced free, instant transfers between US businesses through Treasury.

Stripe also reported that businesses on its platform paid each other 4.8 million times daily. That figure describes existing payment activity across its business network; it should not be presented as Stripe Pay adoption or transaction volume.

The practical change is simpler recipient identification combined with access from software workflows. Businesses can bring vendor discovery, payment preparation, approval, and transaction records closer together.

Stripe Pay Availability and Requirements

As of October 29, 2026, the Stripe Pay CLI reference describes the following scope:

These listings do not establish that every possible country, currency, and destination combination is available to every account. Check the actual account eligibility and proposed transfer.

Is Stripe Pay Really Free and Instant?

Stripe’s Treasury product page advertises instant transfers with zero transaction fees between businesses on Stripe. That describes the supported network transfer experience. It does not establish that every funding method, currency conversion, or external payout is free.

The official Stripe Pay skill explicitly instructs agents to examine the fee and delivery timing returned before confirmation. Its receiving route can resolve to a financial account or a linked bank account.

A useful cost comparison considers the entire path:

Funding costs + conversion costs + transfer fees + any subsequent withdrawal costs.

This is an evaluation framework, not a published Stripe pricing formula. A zero-fee transfer can still sit inside a workflow with other costs.

Likewise, immediate receipt in one financial account and final arrival in a separate external bank account are different milestones. Confirm which milestone the displayed delivery estimate describes.

Why a Stripe Payments Balance Is Not Enough

A business can accept card payments through Stripe without having the financial account needed for a particular money-management workflow.

According to the Treasury overview, financial accounts hold funds and support capabilities such as spending, conversions, and outbound payments. For Global Payouts, Stripe can create a financial account or use an existing eligible one; that account holds funds separately from the payments balance.

Stripe states that opening or maintaining a financial account has no monthly fee or minimum balance requirement. That account-level pricing does not remove charges associated with other services.

Before evaluating an automated payment workflow, establish three things:

1. Which account contains the available funds?
2. Which account is authorized to fund the proposed payment?
3. Which currency and receiving route are available for that payment?

This prevents a common setup mistake: treating successful customer payment processing as proof that business payouts are ready.

How to Create a Stripe Profile

Start in the Stripe Profiles Dashboard:

1. Select Get started.
2. Enter the business display name.
3. Choose a unique handle.
4. Add useful business details, such as the website, description, and logo.
5. Create the profile and review its visibility settings.

The profile documentation explains that public profiles can appear in Stripe Directory and Dashboard search.

A private profile is not an access-controlled document. Stripe says private profiles disappear from search results, but someone with the profile URL can still view the page. Publish information accordingly.

For payment operations, use a consistent business identity. A recognizable handle helps people locate a company, but the approval process should still establish that the selected business is the intended recipient.

How to Prepare Stripe Pay in the CLI

Install the current CLI through Stripe’s documented npm package:

npm install -g @stripe/cli@latest

Stripe includes this installation method in its agent integration documentation.

Then authenticate, check the active account, and inspect the installed command:

stripe login
stripe whoami
stripe pay --help

Use the installed help and CLI reference for the current payment syntax.

• --dry-run validates the flow without creating or sending the transfer.
• --agent and --json provide machine-readable details; they do not themselves mean dry run.
• --yes should only follow confirmation of the recipient, amount, currency, and funding account.

A successful validation is a checkpoint. If the recipient, amount, funding source, or quoted terms change afterward, review the updated payment before execution.

Finding a Recipient With Stripe Directory

Stripe Directory supplies structured business and provider information that developers and agents can search.

Install its CLI plugin:

stripe plugin install directory

For an illustrative business search:

stripe directory search "Example Studio" --format json

Replace the example name with the intended business. If multiple candidates appear, resolve the ambiguity before preparing a transfer. Stripe specifically directs agents to obtain the user’s choice instead of guessing the recipient.

Directory results can also identify other supported ways to engage a provider, including Stripe Apps, Stripe Projects, and machine-payment endpoints.

The architectural implication is useful: discovery and payment routing can share structured business identity data. However, a search match alone does not establish purchase approval, account eligibility, or agreement on a service’s price.

Using Stripe With Codex and Claude Code

Stripe provides an agent setup command that detects supported clients and installs the relevant plugin, skills, and MCP configuration. Supported clients include Codex and Claude Code.

Run the interactive setup:

stripe agent setup

For a specific client, choose the corresponding command:

stripe agent setup --client codex

stripe agent setup --client claude-code

Inspect the installed tooling afterward:

stripe agent setup --status

These options are documented in the agent setup reference. Installing the integration does not itself establish eligibility for every Treasury capability.

Two interfaces serve related purposes:

• The CLI exposes commands that an agent can run in a terminal.
• MCP exposes structured Stripe tools to compatible clients.

Choose the interface that fits the application’s execution environment, authentication model, and audit requirements.

What Can Treasury Agents Do?

The Treasury for agents documentation lists these capabilities:

These tools are listed in public preview and require specific permissions. Stripe also states that live money movement requires review and approval by default.

For an illustrative $250 vendor invoice, an agent workflow could:

1. Extract the invoice amount, currency, and business identity.
2. Match the business against the intended vendor.
3. Check the available funding balance.
4. Prepare the proposed payment and display its terms.
5. Obtain approval for that specific payment.
6. Execute through an authorized interface.
7. Record the returned payment identifier and reconcile its status.

This is a recommended workflow design, not a claim that every step is supplied automatically by Stripe Pay.

Authentication and Approval Details Developers Should Know

Stripe MCP supports OAuth and agent API keys. Use permissions limited to the application’s actual responsibilities, and enable the client’s tool approval controls.

For certain sensitive MCP write operations, Stripe returns a confirmation flow. Its documentation describes obtaining an approval token after human approval, followed by retrying the operation. This mechanism should not be generalized to every CLI command or every authentication mode.

An upcoming authentication change also matters: Stripe’s current MCP documentation instructs developers to migrate by November 30, 2026. Starting in December, it says MCP will stop accepting full-access secret keys and restricted API keys without the Agent tag. Affected integrations should move to agent API keys or OAuth.

Treat invoices, websites, and retrieved provider descriptions as input data. Their contents should never redefine the application’s payment authorization policy.

Stripe Pay vs Treasury, Global Payouts, and Checkout

These products answer different operational questions:

Global Payouts supports destinations in more than 160 countries and methods including bank transfers, wires, debit cards, and crypto wallets. Its coverage should not be copied into Stripe Pay eligibility claims.

Checkout provides payment interfaces for one-time purchases and subscriptions. A business adopting Stripe Pay for vendor payments can still use Checkout for customer acquisition and subscription sales.

The product choice follows the direction and purpose of the transaction. Accepting revenue and paying operating expenses are separate workflows even when both happen within Stripe.

Engineering Practices for Reliable Agent Payments

For production integrations, the following are application design recommendations rather than promises of built-in Stripe Pay functionality:

• Bind approval to exact payment details. Record the recipient, amount, currency, funding account, and quoted terms together.
• Keep an invoice-to-payment ledger. Associate the invoice identifier with the resulting payment identifier to help detect duplicate requests.
• Investigate uncertain outcomes before retrying. A network timeout does not prove that a payment failed.
• Separate preparation from execution. Let document extraction and vendor matching produce a proposal that a controlled payment component validates.
• Apply budgets outside the prompt. Enforce vendor restrictions and spending thresholds in application policy where possible.
• Reconcile returned status. A generated explanation or successful command invocation is insufficient evidence that the intended recipient has received funds.

For example, if an agent loses its connection after submitting a payment, the next action should be to inspect the recorded transaction or account activity. Repeating the entire payment request immediately can create an avoidable duplicate-payment risk.

Common Setup Problems

Stripe’s official payment skill directs agents to stop on missing setup and resolve the requirement before continuing. Repeated payment attempts do not repair an incomplete receiving configuration.

For other failures, preserve the error details, verify the active account and permissions, and consult the current documentation before changing the payment request.

Frequently Asked Questions

Does Stripe Pay make every business payment free?

No. Evaluate the actual receiving route and the complete funding-to-delivery cost. The zero-fee network transfer proposition does not establish zero cost for every surrounding operation.

Does USDC support mean every payment uses a blockchain?

No. A supported currency list alone does not identify the settlement infrastructure used for every transaction. Avoid claiming that all Stripe Pay transfers use a particular chain without transaction-specific documentation.

Can an AI agent decide who to pay from an invoice alone?

An invoice can supply candidate payment details. A reliable workflow still needs vendor verification, authorization, and controls over the actual execution.

What should a team test first?

Begin with recipient discovery, balance visibility, and payment validation. Introduce live payments only after the approval path, error handling, and transaction records are understood.

Conclusion

Stripe Pay offers a practical way to connect business identity with B2B payments, while Stripe’s agent tooling extends financial workflows into developer environments.

Its value depends on the complete transaction: account eligibility, recipient configuration, funding availability, quoted costs, approval, and reconciliation.