Summary
In its 2026-07-29 API release, Stripe extended Shared Payment Tokens, the credential agents use to pay on a customer's behalf, with a new redirect_to_url next action and a use_stripe_sdk parameter. Setting use_stripe_sdk to false and providing a return_url lets integrations complete 3D Secure authentication via redirect instead of a Stripe SDK, broadening how agent-driven checkouts clear bank authentication. Integrations that only handle use_stripe_sdk must update their logic.
What changed
Shared Payment Tokens' next_action can now return redirect_to_url in addition to use_stripe_sdk. A new use_stripe_sdk boolean was added to the Create SharedPaymentToken and Confirm Delegated Checkout Session endpoints and the token object. Setting it false with a return_url triggers a redirect-based 3DS flow. This is a breaking change for code that only handles use_stripe_sdk.
Why it matters
3D Secure is where many agent purchases fail, since bank step-up assumes a human in a browser. Supporting a redirect flow makes it easier to complete authenticated, high-value agent payments across web contexts without embedding Stripe's SDK, a concrete step toward production-grade agentic checkout rather than demos.
Evidence excerpt
Adds redirect_to_url as a new next action type for Shared Payment Tokens, alongside the existing use_stripe_sdk option. If your integration validates or switches on next_action.type and only handles use_stripe_sdk, you must update your logic.