Stripe Payment Link update accepts Connect parameters
Introduced 2026-08-26 · score 0.94
HOW TO USE IT
When updating a Payment Link used with Connect, send the supported money movement parameters to update its settings for future Checkout Sessions. Existing active sessions are unaffected.
curl https://api.stripe.com/v1/payment_links/<PAYMENT_LINK_ID> \
-u "<YOUR_SECRET_KEY>:" \
-H "Stripe-Version: 2026-08-26.dahlia" \
-d "application_fee_amount=<AMOUNT>" \
-d "application_fee_percent=<PERCENT>" \
-d "on_behalf_of=<CONNECTED_ACCOUNT_ID>" \
-d "transfer_data[destination]=<CONNECTED_ACCOUNT_ID>"curl https://api.stripe.com/v1/payment_links/<PAYMENT_LINK_ID> \
-u "<YOUR_SECRET_KEY>:" \
-H "Stripe-Version: 2026-08-26.dahlia" \
-d "application_fee_amount="WHY THIS HELPS
For a repository workflow that updates an existing Payment Link's Connect money movement configuration, modify the link and apply the updated settings to future Checkout Sessions.
BEFORE THIS CHANGE
These parameters were previously available only when creating a Payment Link.
REQUIREMENTS AND LIMITATIONS
- Version: 2026-08-26.dahlia
- <PAYMENT_LINK_ID> (required): ID of the Payment Link to update.
- application_fee_amount: Integer fee amount transferred to the application owner; only when no line item has a recurring price. Empty string unsets it.
- application_fee_percent: Non-negative percentage from 0 to 100, at most two decimals; requires at least one recurring-price line item. Empty string unsets it.
- on_behalf_of: Account on whose behalf to charge. Empty string unsets it.
- transfer_data: Object specifying the account, if any, to which payments are attributed for tax reporting and where funds are transferred. Empty string unsets it; documented subkeys not found.
- Prerequisite: The update API reference lists a Price and an existing Payment Link as prerequisite objects; create a Price and Payment Link first if they do not already exist.
- Prerequisite: The changelog says REST API requests must specify Stripe-Version: 2026-08-26.dahlia to use this API version.
- Applies to Payment Links used with Connect.
- The updated configuration affects Checkout Sessions created from the Payment Link after the change; existing active sessions are unaffected.
FIRST-PARTY EVIDENCE
- https://docs.stripe.com/changelog/dahlia/2026-08-26/adds-connect-parameters-to-the-payment-link-update-method
- https://docs.stripe.com/api/payment-link/update?api-version=2026-08-26.dahlia
Check the installed version and the source before using it. Entry JSON