#nicolas-fernandez-falco_webhooks

1 messages ¡ Page 1 of 1 (latest)

tired trellisBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1376964417639678043

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

wary gull
#

Hi!

silver comet
#

Hi! I'm not sure I understand your question about "the gap?"

wary gull
#

Okay no worries. I'll explain it

#

So I have the following problem at least in Sandbox and I just want to make sure this is not going to be an issue in Live mode

#

So I performed a refund

#

As stripe process successfully the refund it triggers two events

#

charge.refunded and charge.refund.updated

#

Our API listen to both events and handle them correctly in the sense that we are checking if that refund was already proceessed to avoid processing the refund succeeded twice.

#

Seems that in Sandbox both events were triggered almost with the exact same timestamp. So probably when the API performed the evaluation if the refund was processed already for both was false and I had a refund duplicated

#

So I wanted to understand how those events behave in live mode

silver comet