#omarst-checkout-events
opaque quiverBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- omarst, 20 hours ago, 4 messages
crimson sable
One way to handle this would be to only process the customer.subscription.created event if the subscription doesn't already exist in your DB
Alternatively, you could re-retrieve the Subscription when you receive that event so that you can get the most accurate current state
rapid parrot
ok thanks i'll look into that. So this is the default behaviour to send the 2 events at the same time
crimson sable
For Checkout yes, the way it's implemented will result in both events being emitted when payment is successful.