For AI agents and LLMs: a structured documentation index is available at /llms.txt. Every page has a Markdown sibling — append .md to any URL.

Skip to content
Docs

Subscription resumed scenario

Simulates all events that occur when a paused subscription is resumed.

Customize simulation reference

Adjust the options below to see which webhook events occur.

What the outcome of the payment should be when the simulated subscription is resumed.

  1. Subscription resumed

    subscription.updatedThe subscription and its items are updated with new previously_billed_at and next_billed_at dates, and the current_billing_period is updated. If there was a scheduled change to resume, this is set to null.
    subscription.resumedOccurs because a subscription is resumed after being paused.
    transaction.createdPaddle creates a transaction for recurring items on the subscription. Its status is billed, meaning no changes can be made to the transaction. Its origin is subscription_recurring.
    transaction.billedOccurs because the transaction status changes to billed.

  2. Payment is successfully collected

    transaction.updatedThe transaction status changes to paid now that the customer has paid successfully. The transaction is updated with information about the successful payment.
    transaction.paidOccurs because the transaction status changes to paid.
    transaction.updatedAn invoice number is assigned to the transaction. Its status changes to completed as Paddle has finished processing it.
    transaction.completedOccurs because the transaction status changes to completed.

  3. Subscription is activated

    subscription.updatedThe subscription status changes to active now that the transaction is completed. The subscription can now be considered active so you can handle access provisioning.
    subscription.activatedOccurs because the subscription status changes to active.

Was this page helpful?