Stripe Lets Businesses Pay by Handle as AI Agents Take on Finance Tasks

Stripe Pay lets businesses send money to a public handle using typed commands. It requires a funded sender account and an eligible receiving destination linked to the recipient’s profile. Stripe Pay

Stripe introduced Treasury for agents on October 21, extending assistants’ access to company money. Its customer example puts a founder in charge of approving payments. Treasury announcement

For a business giving an AI assistant financial access, these products cover several decisions: finding a payee, choosing an account, authorizing an expense and receiving payment. An owner can grant access to account information while reserving decisions that move money for human approval.

A public handle becomes a business address

Stripe profiles give businesses a unique handle, a public page and space for a description, logo, website and contact details. Public profiles appear in Stripe’s Directory, Dashboard search and Stripe-generated invoices. The Directory can be accessed through Stripe’s command-line tool without signing in, allowing software to discover businesses before a payment starts. Profile guide

A profile can also carry an eligible Payment Link, offering a browser-based payment route. Stripe requires that link to be active and let customers choose the amount. Profiles are unavailable in India, and making a profile private removes it from search while leaving its direct address viewable. These choices affect who can find a business and how they reach it. Profile guide

For a company receiving payment, the immediate change is simpler addressing. A buyer can identify a business by a handle rather than treating an invoice, a website and an account number as unrelated identifiers. That is a practical improvement for repeat business payments. It leaves the commercial agreement, amount owed and approval process to the parties.

The account behind the handle still matters

The sender needs a funded financial account; recipient eligibility depends on the destination linked to its Stripe profile. Stripe’s guide calls for confirming the payee, amount, currency and funding account before sending. Transfer guide

Treasury’s account documentation shows why eligibility requires a separate check. It lists public previews in the United States and United Kingdom, with Australia in private preview. Financial accounts can hold balances such as dollars, euros and pounds; eligible businesses can also hold supported stablecoins. Those account capabilities do not supply a complete list of routes or currencies available through Stripe Pay. Treasury documentation

Stripe says opening and maintaining a financial account has no monthly fee or minimum balance requirement. Its Stripe Pay guide describes instant transfers but publishes no universal transfer price, currency table or amount ceiling. Businesses evaluating it still need the terms for their actual account and transfer, including any conversion charges and destination restrictions. Account terms Transfer guide

A founder approves what his agent prepares

Kubrio, a children’s creative-learning platform, supplies a concrete example in Stripe’s October announcement. Founder Vlad Stan uses a Grok agent called Stash to check balances, subscription changes, failed payments and refunds each morning. Stan reads its report and intervenes when needed. Stripe says he plans to add transfers and contractor payments, with every payment approved by him. Kubrio account

The current Treasury agent guide describes a default requirement to review and approve live money movement. Its tools separate reading balances, setting up recipients, sending money and converting currencies, with different account permissions for each. Stripe’s authorization screen lets users select live accounts or sandboxes and set different permissions for each. Owners can therefore connect an assistant for financial reporting without granting every available action. Agent permissions

Consumer payments show another approach. Stripe launched Link’s agent wallet in April, letting a user approve a spending request before an assistant receives a one-time card or Shared Payment Token. The token represents permission to charge an underlying payment method without exposing its original credentials. Stripe describes controls for merchant, amount and currency. Link announcement

Developers seeking their own wallet experience can instead use Stripe Issuing’s underlying tools. Stripe describes card-level permissions, transaction monitoring and controls applied when a charge is authorized. Those capabilities serve developers building a financial product; Link packages an approval flow for consumers who want an assistant to make a purchase using an existing wallet. Issuing and Link

Meta’s Muse added Link integration in September for U.S. consumers. Stripe says users approve each purchase total in the chat interface. Where a seller accepts Link, Muse uses the saved payment method; elsewhere, Link can provide a single-use virtual card scoped to that purchase. This reaches ordinary online stores while keeping authorization attached to a particular transaction. Muse integration

Standards carry the payment and its permission

For services designed to sell directly to software, Stripe and Tempo introduced the Machine Payments Protocol in March. A service responds to an agent’s request with a payment request; the agent authorizes payment and receives the resource. Stripe identifies Browserbase’s browser sessions and Parallel’s paid web access as early uses. Protocol announcement

Payments accepted through that protocol enter a Stripe business’s existing balance and follow its standard payout schedule, according to Stripe. A fast purchase or transfer instruction therefore cannot be assumed to mean immediate arrival in every seller’s bank account. The receiving product and payout arrangement determine that part of the transaction. Settlement description

Google’s Agent Payments Protocol addresses authorization explicitly. Its developer guide describes signed mandates that record a buyer’s intent and bind permission to a cart and amount. Approved merchants, expiration and approval requirements can be recorded as part of that process. Google distinguishes this from the Universal Commerce Protocol, which organizes shopping and checkout. Google guide

In Google’s example, an intent mandate names permitted merchants and records when permission expires. A payment mandate then ties authorization to a specific order and total; a receipt records what happened. The guide labels its signature example as simulated and describes AP2 as version 0.1, with its types distributed separately from Google’s Agent Development Kit. A developer still has to implement the protocol’s checks. Authorization example

Access can also outlast an individual task. Stripe’s guide distinguishes sessions acting for a user from agent keys intended for independent, persistent access. Revoking a session affects only the account or organization and environment being viewed; the same session can remain active for other accounts. A company withdrawing an agent’s authority must therefore check which accounts its action actually covers. Access and revocation