November 5, 2026 · Muhammad Umar · More by Muhammad Umar
Stripe's New Payout Intents and Outbound Payments
Stripe's Money Management v2 adds Payout Intents, Outbound Payments, and Recipient Verification APIs — what each one does and doesn't do yet.
On October 28, 2026 — the first release of the API's "Endive" version family (2026-10-28) — Stripe shipped three new endpoints under its Money Management v2 surface: Payout Intents, Outbound Payments, and Recipient Verifications. For platforms and marketplaces that move money out to sellers, creators, or vendors rather than just taking payments in, this is a materially different way to do it: FX quoting, payee verification, and payout scheduling are built into the API itself, instead of stitched together from older Treasury and payout primitives.
Two New Objects for Moving Money Out
PayoutIntent and OutboundPayment are separate objects with separate status lifecycles. A PayoutIntent starts pending — if you set schedule_options.execute_on, Stripe labels it Scheduled and doesn't hold funds until that date — then moves through processing, requires_action, posted, or canceled. An OutboundPayment, which represents the underlying money movement, has its own five statuses: processing, failed, canceled, posted, and returned. A payout Stripe is reviewing sits in processing with status_details.processing.reason: under_review; Stripe says these reviews typically take up to 2 business days.
Verifying the Recipient Before You Send
RecipientVerification checks a payee before money moves, supporting two distinct flows: Confirmation of Payee (CoP, used in the UK) and Verification of Payee (VoP, used intra-EU, which expires 5 minutes after creation). The match comes back as one of four results — match, close_match, no_match, or unavailable — and Stripe is explicit that anything short of a clean match still lets you send funds, provided you explicitly acknowledge the result first.
Cross-Border Payments Need a Fresh Quote Every Time
Same-country, same-currency payouts auto-select the local rail — ACH for USD, FPS for GBP, SEPA for EUR — and need no special handling. Crossing currencies is different: you first create an OutboundPaymentQuote, which returns the FX rate and a fee breakdown, but that quote is only valid for 5 minutes. Let it expire before creating the OutboundPayment and you need a new quote; there's no grace period documented.
What's Still Gated Behind Contacting Stripe
This is additive, not a replacement — standard domestic payout rails work today without any of this. But several pieces of the new surface require reaching out to Stripe directly: cross-border Outbound Payments to external bank accounts need access granted via treasury-support@stripe.com (transfers between financial accounts you already own are enabled by default), and payout scheduling — sending a payout up to 180 days ahead without Stripe holding the funds in the meantime — also requires contacting support to turn on.
Reversibility is also narrower than you might expect: Stripe documents US domestic ACH and Fedwire payouts as reversible within 24 hours, but UK FPS payouts and cross-border payouts generally are not reversible once posted. For a marketplace or payroll product built on this surface, that makes recipient verification worth taking seriously up front — a close_match or no_match result is the system telling you to double-check before you send money you likely can't get back.