Skip to main content

Subscription reactivation

A canceled subscription can be reactivated. Reactivation is modelled as a separate resource — it has its own ID and its own properties — and reverses a cancellation.

For the cancellation flow itself, see Subscription cancellations.

Endpoint​

curl -i -X POST \
  'https://staging-api.payments.ai/v1/public-api/organizations/:organizationId/subscription-reactivations' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: ApiKey <keyValue>' \
  -d '{
    "subscriptionId": "ord_xxx",
    "description":    "Customer changed their mind"
  }'

The description field records the reason for reactivation. There is no list of canonical values — use a short free-text reason.

Available operations​

MethodPath
POST/.../subscription-reactivations (create)
GET/.../subscription-reactivations[/{id}] (list and read)

Reactivations cannot be updated or deleted — they are recorded as historical events.

After reactivation​

The subscription returns to active and continues on its original payment instrument. Confirm the resulting state and next renewal date in the API response.

If the reactivation endpoint returns an error, the subscription is no longer in a reactivable state — create a new subscription instead.