Adds support for recurring payments with Satispay
What’s new
The setup_future_usage parameter is now supported on PaymentIntents and SetupIntents for Satispay, enabling both on-session and off-session payment flows.
Satispay is also now a supported payment method type for Subscriptions and Invoices. Include satispay in the payment_method_types parameter of the payment settings for both resources.
Impact
You can now accept Satispay payments on a recurring basis, including for subscriptions and invoices.
To save a Satispay payment method for future use, set setup_future_usage to off_session or on_session when creating a PaymentIntent or SetupIntent. To enable Satispay for subscriptions or invoices, add satispay to the payment_method_types parameter in your Subscription or Invoice payment settings. For full implementation details, see Accept a Satispay payment and Set up future payments.
Changes
Upgrade
- View your current API version in Workbench.
- If you use an SDK, upgrade to the corresponding SDK version for this API version.
- If you don’t use an SDK, update your API requests to include Stripe-Version: 2026-06-24. dahlia
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.
Related changes
- Adds buyer ID support for Bizum payments
- Enables manual capture for Sunbit payments
- Adds buyer ID support for the related setting payments
- Adds a fingerprint to Pix payment method details
- Adds transaction link ID to card payment method details for Mastercard and Maestro transactions
- Adds payment method options for Sunbit in Checkout Sessions
- Adds support for the Sui network and USDsui token for crypto payments
- Adds support for Mastercard compliance disputes