#Ji_net-subscription-events

1 messages · Page 1 of 1 (latest)

indigo bobcat
#

Hi there 👋 the customer.subscription.updated event is right to monitor for a subscription becoming incomplete. If you want to know if a subscription is created in an incomplete state (rather than being updated to it) then you'll also want to listen for customer.subscription.created.

Bear with me while I double check about incomplete_expired, since this is a terminal state I need to confirm whether it will trigger an update or delete event.

vocal coyote
#

mmm ok, in my case if the customer's first payment failed due to card declined, I'll need to catch the customer.subscription.created event, right!

indigo bobcat
#

Yeah, but a lot of things can happen quickly at the time of creation. We also can't guarantee that webhook events will get delivered in the correct order. So I'd recommend that you use the events as a trigger, but that you retrieve the subscription via the API to ensure you have the most recent status for it.

vocal coyote
#

mmm ok

indigo bobcat
#

Thanks for your patience, just found an expired sub in my test account and it fired a customer.subscription.updated event when it went from incomplete to incomplete_expired.

vocal coyote
#

Got it, thanks for your help