#juraj.puchky
1 messages · Page 1 of 1 (latest)
cannot figureout how to handle these kind of hooks which are not related to payment
Can you rephrase your question? I don't quite follow
All three of these are customer.subscription.updated events. These are emitted when anything about a particular subscription changes
You can look at previous_attributes to see which attributes changed, and then compare to the new values
this evt_1OD6qWFSqUzAKAmVJJLk2AhJ has coresponding recurent payment but other once has no payment related to event
i need to capture only updates related to payments
This is filtering you'll need to do on your end. If your endpoint is configured to receive customer.subscription.updated events, we'll send all events of this type.