Skip to main content

subscription.amount_changed

Generated from COPE public event contracts. Do not edit this page by hand.
Use this event to mirror a repriced subscription into your own billing records. The change is applied in place with no proration, so nothing is charged when it happens: the new amount bills at the existing cycle boundary. effective_at is when we expect that to be — it is derived from the subscription’s next payment date at the moment of the change, and a cycle that later moves for an unrelated reason leaves it stale, so treat it as a prediction and take the charge itself as the confirmation. old_recurring_amount_cents and new_recurring_amount_cents are what the buyer is billed, quantity included, in currency. The body names the business, the order, the line item and the subscription, each as object and id; store subscription.id to match later events on the same subscription, and read everything else about them through the API.

Delivery Contract

Payload Fields

Example delivery

Compatibility

Fields may be added within the same major version. Removing or changing the meaning of a documented field requires a new event version.