October 5, 2026 · Muhammad Umar · More by Muhammad Umar
Stripe Global Payouts Can Reuse Existing Customer Credentials
Stripe's Accounts v2 preview lets platforms reuse a known Customer's payment credentials to create their Global Payouts recipient — no second KYC flow.
Stripe shipped a public-preview feature on April 22, 2026 that changes a specific, recurring pain point for marketplace and platform teams: a user who has already paid you — and is already a Customer object in your Stripe account — needing to re-enter their own payout details before you can pay them back.
What shipped, and how to opt in
The feature requires opting in to the Accounts v2 API and using the preview API version header, Stripe-Version: 2026-04-22.preview. Stripe's own upgrade path is explicit: check your current API version in Workbench, upgrade your SDK if you use one, upgrade the API version on your webhook endpoints, test the integration — including your Connect integration if applicable — then perform the upgrade in Workbench, with a 72-hour rollback window. No action is required for platforms that don't want to join the preview; nothing changes until you opt in.
How the credential reuse actually works
Once a platform opts in, Stripe syncs existing and new Customer objects with customer-configured Account objects. From there, Stripe can reuse eligible PaymentMethods already collected for that Customer to create a PayoutMethod for Global Payouts to the same Account — Stripe's own phrasing is that this streamlines creation of a recipient. Practically, that means a platform no longer has to run a second collection flow asking a known Customer for payout and identity details it has already collected once.
What's in scope, and what's still public preview
Initial support is scoped to two credential types: US debit cards and US bank accounts. Stripe doesn't describe this as an open-ended list, and the feature as a whole is public preview, not generally available — it affects specifically Global Payouts users who both collect payments from and send payouts to the same user.
Why this is worth wiring up for a two-sided marketplace
Global Payouts itself is built for sending funds to third parties — contractors, affiliates, creators — in their own currency, as an alternative to Stripe Connect for platforms that don't need to hold segregated balances or carry licensing. For a platform that is also the merchant of record for that same person — a creator buying their own merch, an affiliate who's also a customer — the previous requirement to collect payout and identity information twice was pure friction with no compliance benefit, since Stripe already held equivalent information on the Customer object. Teams building or maintaining that kind of dual-role onboarding flow now have a concrete reason to test the Accounts v2 preview rather than wait for general availability.