Change Plan
Modify an existing subscription’s plan, enabling both upgrades and downgrades to different pricing tiers.
Note: By default this uses the customer’s existing payment information. Set collect_via_payment_link to charge via a hosted checkout page instead.
Scheduled Plan Changes
Use theeffective_at parameter to control when the plan change takes effect:
Payment Failure Handling
Use theon_payment_failure parameter to control what happens when the plan change payment fails:
on_payment_failure is not specified, the behavior defaults to your business-level setting configured in the dashboard.Collecting via Payment Link
Setcollect_via_payment_link to true to send the customer to a hosted checkout page instead of charging their saved payment method. The response then includes payment_id, payment_link, client_secret, and expires_on — redirect the customer to payment_link to complete the payment.
This requires:
422. While the link is unpaid, the subscription stays on its current plan and a further change-plan request returns 409, unless you set cancel_older_payment_link.
Redirecting After Payment
Setreturn_url to send the customer back to your site after they pay the link. The redirect adds subscription_id, payment_id, and status as query parameters.
statusis the status of the plan-change payment, not the status of the subscription.- When the payment fails, the subscription stays active on its current plan. To try again, call
change-planagain to get a new link. - The new plan can apply shortly after the redirect, when the payment webhook arrives.
return_url needs collect_via_payment_link: true. Without it, the request returns 422.
Replacing a Pending Payment Link
If the customer leaves the checkout without paying, setcancel_older_payment_link to true on the next change-plan request. Dodo Payments cancels the unpaid link, and the new plan change replaces the pending one. The cancelled link no longer accepts a payment.
The request is validated before the link is cancelled, so an invalid request keeps the customer’s link. The link is cancelled only if the customer has not started to pay:
change-plan request issues its own invoice. The replaced plan change and its invoice are cancelled.
Discount Codes
You can apply one or more stacked discount codes when changing plans by passing thediscount_codes array (max 20 entries, applied in array order). The singular discount_code field is deprecated but still works for existing integrations; it cannot be combined with discount_codes in the same request.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Subscription Id
Body
Unique identifier of the product to subscribe to
Proration Billing Mode
prorated_immediately, full_immediately, difference_immediately, do_not_bill Number of units to subscribe for. Must be at least 1.
x >= 0Whether adaptive currency fees should be included in the price (true) or added on top (false). If not specified, uses the subscription's stored setting.
Addons for the new plan. Note : Leaving this empty would remove any existing addons
Cancel the payment link of a pending plan change, so that this change can replace it.
The link is cancelled only if the customer has not started to pay. A
paid or in-progress payment gives a 409. A failed cancel gives a
503, and a retry is safe.
The request is validated before the cancel. A later failure, for example an amount below the minimum, leaves the subscription on its current plan with no open link. A retry is safe.
The preview route shares this request body and ignores this field.
Replace a scheduled plan change with this one.
The scheduled change is cancelled by the transaction that applies this change. A change that never applies leaves the schedule in place.
effective_at: next_billing_date is allowed. The new schedule then
replaces the old one in the request transaction.
A pending plan change still gets a 409. This field does not affect it.
The preview route shares this request body, so a preview that sets this
field also passes the scheduled-change 409.
Collect the plan-change amount with a payment link. The customer then pays on a checkout page.
The business needs the allow_plan_change_via_payment_link capability.
The request needs effective_at: immediately. The request also needs
on_payment_failure: prevent_change.
The preview route shares this request body and ignores this field.
DEPRECATED: Use discount_codes instead. Cannot be used together with discount_codes.
Stacked discount codes to apply to the new plan. Max 20. Cannot be used together with discount_code. If provided, replaces any existing discount codes. Empty array removes all discounts. If not provided (None), existing discounts with preserve_on_plan_change=true are preserved.
When to apply the plan change.
immediately(default): Apply the plan change right awaynext_billing_date: Schedule the change for the next billing date
immediately, next_billing_date Metadata for the payment. If not passed, the metadata of the subscription will be taken
Controls behavior when the plan change payment fails.
prevent_change: Keep subscription on current plan until payment succeedsapply_change(default): Apply plan change immediately regardless of payment outcome
If not specified, uses the business-level default setting.
prevent_change, apply_change The URL that receives the customer after they pay the payment link.
Needs collect_via_payment_link: true. Without it, the request gets a
422. A change that collects no money issues no link and does not use
the URL. The preview route validates this field but does not use it.
The redirect adds subscription_id, payment_id and status. The
status value is the status of the plan-change payment. It is not the
status of the subscription. When that payment fails, the subscription
stays active on its current plan. To try again, call this endpoint
again to get a new link. The new plan can apply after the redirect,
when the payment webhook arrives.
Response
Subscription plan changed. A link request can return checkout details. A pending plan change applies after payment succeeds.
Handles for a hosted checkout page that settles a plan change.
The four fields repeat UpdatePaymentMethodResponse and a subset of
CreateSubscriptionResponse. A shared type would rename the generated SDK
types for all three routes, so each route keeps its own.