Adds the ability to update shipping options, consent collection, and future usage support on Payment Links
What’s new
Adds support for three additional parameters when updating a Payment Link:
- shipping_options: Accepts an array of up to five shipping rate objects, each with a
shipping_rateID corresponding to an existing Shipping Rate. Pass an empty array to remove all shipping options from a Payment Link. - consent_collection: Lets you update the following consent collection settings on an existing Payment Link:
- consent_collection.payment_method_reuse_agreement.position : Controls where the payment method reuse agreement is displayed.
- consent_collection.promotions : Controls whether to display a checkbox for promotional communications consent.
- consent_collection.terms_of_service : Controls whether to display a checkbox for terms of service acceptance.
- payment_intent_data.setup_future_usage: Set to
on_sessionoroff_sessionto indicate how you intend to reuse the payment method collected during the Checkout Session. Previously, API requests that included this parameter returned a400error.
Previously, these parameters were only configurable through the Dashboard.
Impact
You can now programmatically manage shipping options, consent collection, and future payment usage on existing Payment Links without using the Dashboard. Together, these additions make it possible to use the API to build automated workflows that update Payment Link configuration in response to changes in your business logic including recurring payment setups, shipping rate changes, and consent policy updates.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| setup_future_usage | Added | PaymentLink#update. payment_intent_data |
| shipping_options | Added | PaymentLink#update |
| consent_collection | Added | PaymentLink#update |
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-07-29. 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 the ability to indicate that you don’t intend to reuse Samsung Pay and the related setting payment method types
- Adds customer and payment method details to the Refunds API
- Adds support for new banks to FPX payments
- Adds the related setting as a supported network for funding instructions
- Adds the allowed payment method types parameter to Payment Intents and Setup Intents
- Adds MB WAY support to the hosted invoice page
- Adds card network details to the Dispute object
- Adds the ability to list Payment Records
