How does a merchant follow subscription changes in its own systems?
Through webhooks. A signed subscription webhook is sent at every status change, whether it comes from the API, the console, the payment page or the engine itself, with the new and previous status, the next rebill and the overdue counters.
In detail
Through webhooks. A signed subscription webhook is sent at every status change, whether it comes from the API, the console, the payment page or the engine itself, with the new and previous status, the next rebill and the overdue counters.
One event for every status change
The webhook carries the subscription event type and fires for every move between created, incomplete, started, active, past due, paused, canceled and completed. It is signed like every other webhook of the platform.
What each event contains
- The new and previous status, with the date of the change.
- The next rebill: date, amount and currency.
- The overdue flag and the number of unpaid rebills.
- The offer, its version and the subscriber.
- The order and transaction behind the change, and the retry attempt when there is one.
Payments in the same stream
Transaction webhooks of subscription payments also say whether a payment is a retry, so the merchant's systems reconcile rebills, retries and one-off charges from one source.