Skip to content
StackQuay

Playbook · Stripe

Update a Stripe Payment Link without changing the URL

Edit shipping, consent, and Connect settings on an existing Payment Link so your shared link stays the same.

2026-10-16

Who it’s for / not for

ForNot for
People who already created a Payment Link (see Stripe HK Payment Links) and need to tweak shipping, consent, limits, or Connect without a new URLTeams that need a full custom Checkout Element / catalog CMS
Agent-led ops (bot drafts the checklist; human clicks Save in Dashboard or runs API with their keys)Anyone treating this as tax, PDPO, or Connect platform legal advice
Operators who want one reusable link across Threads / newsletter / siteA brand-new checkout that needs its own URL

Stack (spine only)

Secondary (not claimed for HK overnight): Managed Payments / merchant-of-record — human must verify whether it applies to your HK account before any draft or site copy.

  • Stripe Payment Links — same hosted page; edit instead of recreate (payment-links)
  • Stripe Dashboard — primary path: open link → overflow menu (⋯) → edit (customize)
  • Payment Links API POST /v1/payment_links/{id} — update endpoint (API update)
  • Shipping Rates — referenced by ID when setting shipping_options (up to five)
  • Connect (optional) — application_fee_*, on_behalf_of, transfer_data on update (changelog 2026-08-26)

Bot vs human

Bot doesHuman must do
Draft this playbook + SEOOwn the Stripe account; open the existing link in Dashboard
List which fields docs say are editableClick edit / Save; confirm preview of the hosted page
Note API version gates (Dahlia dates below)Never paste live secret keys into chat or git
Flag Connect / tax / consent as verifyDecide ToS URL, shipping countries, fees; consult your own advisor for consent/tax
Never create live charges or flip Go live for youShare a live Payment Link when you are ready

Numbered steps

  1. Start from an existing link (don’t rebuild by default). Payment Links are reusable across many customers (payment-links docs). Prefer edit so Threads / QR / buy-button URLs stay valid. Complements Stripe HK Payment Links.
  2. Edit in Dashboard (primary path). Dashboard → Payment Links → open the link’s details → overflow menu (⋯) → edit (customize docs). Typical edits: billing vs billing + shipping addresses and ship-to countries; optional shipping rates; phone; ToS acceptance after you set a terms URL in Public details; payment limits and inactive message; tax, names, custom fields, branding, trials, quantities. Save-for-future-use needs legal/compliance review before enabling. Human must verify every toggle before Save.
  3. Understand what “update” affects. For Connect money-movement fields, the new configuration applies to Checkout Sessions created after the change; existing active sessions are not affected (Connect update changelog). Treat other mid-checkout buyers the same way. Human must verify in test mode with a fresh open of the URL after Save.
  4. Optional: update via API. POST /v1/payment_links/{PAYMENT_LINK_ID} (API reference). From 2026-07-29 (Dahlia): shipping_options (up to five shipping_rate IDs; empty array removes all), consent_collection (terms_of_service, promotions, payment_method_reuse_agreement.position), and payment_intent_data.setup_future_usage (on_session or off_session). From 2026-08-26 (Dahlia): Connect params application_fee_amount, application_fee_percent, on_behalf_of, transfer_data — pass an empty string to unset. Other documented fields include active, after_completion, allow_promotion_codes, automatic_tax, billing_address_collection, custom_fields, inactive_message, line_items, metadata, shipping_address_collection, and more — check the current API reference. Bot never runs live secret-key API calls. Use test mode first; pin Stripe-Version per those changelogs.
  5. Shipping rates checklist. Create or pick Shipping Rate objects first. Attach up to five via Dashboard or shipping_options. To clear all rates via API, pass an empty array (2026-07-29 changelog). Pair with shipping_address_collection.allowed_countries when collecting shipping addresses.
  6. Consent checklist. Set ToS (and optional privacy) URLs in Public details before requiring agreement. Dashboard: require ToS when creating or editing. API: consent_collection.terms_of_service = required or none. Promotions checkbox and payment-method reuse agreement position are updatable via API per the 2026-07-29 changelog. Human must verify wording — this page is not legal advice.
  7. Connect checklist (only if you already use Connect). Update fees / destination / on-behalf-of on the same link (2026-08-26 changelog). Applies to new sessions after the change. Most people on this spine do not need Connect day one.
  8. Deactivate vs delete. You can deactivate and set inactive_message. Prefer deactivate + edit over silent URL churn. QR / shared URLs point at the same buy.stripe.com path while active is true.
  9. Before live charges. Editing a live link changes what new buyers pay or agree to. Use test mode for experiments. Share a payable link when you are ready.

Failure modes / HK caveats

  • Wrong mental model: Recreating a link breaks old posts / QR / newsletter CTAs — edit first.
  • Open Checkout Sessions: Connect changelog states active sessions aren’t affected; don’t assume in-flight buyers see the new shipping/consent immediately.
  • API version lag: Shipping/consent/future-usage on update need ≥ 2026-07-29.dahlia; Connect params on update need ≥ 2026-08-26.dahlia. Older versions may 400.
  • Secret keys: Never commit; never give live keys to the bot.
  • Stripe Tax / Managed Payments: Tax is a paid product with location registration; Managed Payments is a merchant-of-record path — do not claim HK eligibility overnight; human must verify.
  • Consent / PDPO: Checkbox features ≠ legal sufficiency. Human + advisor.
  • Fees / methods: No invented conversion rates. Verify HK fee numbers in your Dashboard.
  • Not payment/legal certification.

Newsletter CTA

Next checklist: Resend Broadcast drafts. You review the draft, then you press Send.

Human must verify

  1. You are editing the correct Payment Link ID / Dashboard row (test vs live).
  2. Shipping countries and rates match what you actually fulfill.
  3. ToS / privacy URLs in Public details are current and intentional.
  4. Whether promotional consent / save-for-future-use is appropriate for your product and region.
  5. API version in Workbench if you automate updates.
  6. Connect fee / transfer settings (only if you use Connect) — and that only new sessions pick them up.
  7. Stripe Tax / Managed Payments applicability to your HK account before enabling or writing marketing copy.
  8. Share a live Payment Link when you are ready.

Doc gaps

Exact Dashboard click labels may shift; always follow in-product UI. HK-specific method matrix and Managed Payments eligibility were not asserted here — verify in your account. No invented fee or conversion metrics.

Docs cited

Related playbooks