Stripe issues close to 20,000 vendor payments annually across more than 70 markets. Those payments traditionally ran through direct bank integrations wired into the ERP; markets without an integration required teams to key payments into bank portals by hand. Each new banking relationship carried its own technical, contractual, and security obligations, and standing up an integration for a new market took weeks. Failed payments meant operations and finance staff combing bank portals and the ERP to find the cause before resending funds.
Earlier this year Stripe began routing its own vendor payments through the product it was building for customers sending money internationally: Stripe Global Payouts, which reaches recipients in over 160 countries through a single API using local bank transfers, international wires, and stablecoins, without requiring a Stripe account on the receiving end.
By October 2026, more than $1 billion had gone to over 3,400 vendors in the US and UK via Global Payouts. Market setup time fell from as much as six weeks to one. Automated reporting and reconciliation save finance and treasury an estimated 20–30 hours per month, and payouts have held at a 99.9% success rate.
Existing Global Payouts customers include Lyft, Scale AI, BMW, and Meta, using it for marketplace earnings, freelancer payments, insurance claims, and customer reimbursements. Running vendor payments through it internally surfaced the problems businesses face when integrating and tracking payouts at scale—vendor data quality, payment visibility, and high-value transaction handling—all of which were subsequently fixed.
Phased cutover
Testing started in February 2026 with a single low-dollar ACH or wire payment through each US payment flow. A staged, four-wave rollout followed in March, with amounts increased only after nearly all eligible payouts in the preceding wave had cleared. By June, Global Payouts carried the large majority of Stripe's US domestic vendor payments by both count and value.
Findings from running our own payouts
Validate recipient data before money moves
Bank payments fail for many reasons—insufficient funds, bank limits, restricted accounts—and the old bank integrations did not always catch bad or missing information at submission. During the migration, recipient data errors accounted for the majority of failures. A trivial mistake such as an incorrect postal code could go unnoticed for days until the bank returned the payment or the vendor got in touch.
Once the common failure causes were cataloged, those checks moved earlier in the flow. The orchestration layer maps vendor and bank account records onto the recipient and payout methods Global Payouts expects, and the API verifies that required information is present and valid before funds move. Errors identify the field that needs attention, letting operations teams resolve most issues in minutes instead of tracing a failed payment days later.
Previously, payment status lived across bank portals and the ERP. On Global Payouts, each vendor payment is traceable through a single API: every payment carries a unique reference number and its invoice details as metadata, so the invoice and payment can be followed from initiation to settlement.
The vendor's bank statement, however, did not always carry the same context. Money arrived, but the recipient could not necessarily tell who sent it or which invoice it settled—traceable internally, unrecognizable to the recipient. Customizable statement descriptors were added so businesses can put recognizable information on recipients' bank statements, giving vendors enough context to match incoming funds with invoices and easing reconciliation on both sides.
Size, not just volume, defines scale
Tens of thousands of payments represented only one dimension of the load. Some vendor payments were far larger than the system was designed to handle, and anything over the existing limits had to be processed by hand. ACH and wire limits on the Outbound Payments API were raised to $100 million, bringing more high-value vendor payments into the same automated path without bypassing existing approval, ERP recording, funding, reconciliation, and reporting processes.
Next steps
Global Payouts is now generally available in the US and UK, serving thousands of businesses that pay third parties in over 160 countries, including recipients who do not use Stripe.
Stripe is working to shift more of its cross-border and cross-currency vendor payments onto the product. That covers broader recipient-country coverage, stablecoin payouts, vendors whose address and bank sit in different countries, and payments made in a currency other than the vendor's bank account currency.
The company is also developing AI-assisted payouts and recipient onboarding through Stripe's Model Context Protocol, a standard for agents to interact with Stripe. Businesses can delegate steps such as beginning recipient onboarding or initiating a payment to agents while keeping control: they choose which Stripe data an agent can reach, which actions it may take, and when a human must approve a payout.



