Subscription resumed scenario

Simulates all events that occur when a subscription is resumed.

Subscription resumes

`subscription.updated`	The subscription and its items are updated with new billing dates. If there was a scheduled change to resume, this is set to `null`.
`subscription.resumed`	Occurs because the subscription resumed.
`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_updated`.
`transaction.billed`	Occurs because the transaction status changes to `billed`.

Payment collected successfully

`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`.

If collection is unsuccessful, a subscription becomes past due and dunning starts.

Related pages

Pause or resume a subscription

Test webhooks