when a new user is paying for a subscription, webhook is giving me double events, one subscription.active and one subscription.renewed - an earlier conversation I will reference below tells me this appears to be by design - so my question is will I always receive subscription.renewed event, even if a first time user is subscribing to my product?
#Duplicate events firing to WebHook on subscription
cursive gull
rustic sorrelBOT
when a new user is paying for a subscription, webhook is giving me double events...
Yes, based on the information provided, it appears that receiving both subscription.active and subscription.renewed events when a new user subscribes to your product is by design. This means that even for a first-time subscription, you will receive a subscription.renewed event alongside the subscription.active event.
The subscription.active event indicates that the subscription is now active and recurring charges are scheduled, while the subscription.renewed event signifies that the subscription has been successfully renewed for the next billing period. It seems that the subscription.renewed event is triggered even at the initial subscription to confirm the setup of the recurring billing cycle.
If this behavior is consistent with the design of Dodo Payments, you should expect to receive both events for new subscriptions. If you have any concerns or need further clarification, it might be helpful to reach out to Dodo Payments support for confirmation and additional details on handling these events in your application.
Disclaimer: I am a bot and I may make mistakes. Always refer to the documentation. Here are some of the relevant links that I found regarding your query. [1] [2] [3]
cursive gull
#1366698436635787305 message
this is the earlier message I wanted to reference. The bot provided the wrong answer in the previous conversation, so would prefer to verify from a human
cursive gull
when a new user is paying for a subscription, webhook is giving me double events...
if this is the case, can handle subscription payments through subscription.renewed and keep subscription.active for a different use case I guess? but would be amazing if this could be confirmed before I proceed
west heart
subscription.active will be fire when mandate is created for a payment. this will be fired once.
subscription.renew will be fired every time payment is deducted, even for the first time
hope this clears
cursive gull
as a best practice, do you guys advise using .active for the first time and .renewed thereafter or using .renewed consistently to track payments?
thank you for the prompt response
west heart
use .renew even for the first time