Skip to main content
Answer

Duplicate webhook call

  • March 10, 2025
  • 3 replies
  • 133 views
S
Forum|alt.badge.img+2

the story: I was integrated in-app purchase directly with apple, but sometimes i got duplicate transactions, i don't know why so i switched to using RevenueCat. Below is the problem i got when using RevenueCat.

the context: customer 46611 made a purchase with package1 but the webhook was duplicated. the first webhook request was called to handle package1, the second one was called with package4 info

note: the second transaction was created before using RevenueCat SDK. my event type is Non renewing purchase

question: Why do duplicate webhooks happen, and how can I avoid them?

 

Best answer by wes_clark

You’re welcome. We do not currently have a way to stop these events for past purchases from being sent, however I would be happy to share this feature suggestion internally for the rest of the team to take a look at. 

S
This post has been closed for comments

3 replies

wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • wes_clark
  • RevenueCat Staff
  • March 12, 2025

Hi! As our documentation on historical events mentions, for non-renewable products, we send events for all purchases made within the past 30 days, so these webhook events are expected. 

S
S
Forum|alt.badge.img+2
  • sherwind
  • Author
  • New Member
  • March 13, 2025

Hi! As our documentation on historical events mentions, for non-renewable products, we send events for all purchases made within the past 30 days, so these webhook events are expected. 

Oh, thank you, but is there any way to stop calling events for the past purchases? Because the users have been topped up successfully, I don’t want to call the event twice.

wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • wes_clark
  • RevenueCat Staff
  • Answer
  • March 17, 2025

You’re welcome. We do not currently have a way to stop these events for past purchases from being sent, however I would be happy to share this feature suggestion internally for the rest of the team to take a look at. 

Terms & ConditionsCookie settingsAccessibility statement