Subscription resumed scenario

Simulates all events that occur when a subscription is resumed.

Configure which webhooks send when simulating a resumed subscription
Success
  1. Subscription resumed

    subscription.updated

    The 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.resumed

    Occurs because a subscription is resumed after being paused.

    transaction.created

    Paddle 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.billed

    Occurs because the transaction status changes to billed.

  2. Payment is successfully collected

    transaction.updated

    The transaction status changes to paid now that the customer has paid successfully. The transaction is updated with information about the successful payment.

    transaction.paid

    Occurs because the transaction status changes to paid.

    transaction.updated

    An invoice number is assigned to the transaction. Its status changes to completed as Paddle has finished processing it.

    transaction.completed

    Occurs because the transaction status changes to completed.

  3. Subscription is activated

    subscription.updated

    The 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.activated

    Occurs because the subscription status changes to active.

Related pages