#jaylathiya-0103_webhooks

1 messages · Page 1 of 1 (latest)

rotund etherBOT
#

👋 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/1410154348511625248

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

#

We wish we could help, but you need to talk to Stripe support

We can only help on Discord if all of the following are true:

  • 🧑‍💻 You must be a developer
  • 🛠️ Your question must be about building a Stripe integration
  • ⚙️ Your question must be technical/developer focused
  • ⏱️ You must be available to respond in realtime
  • 👥 You must be comfortable receiving help in public (this is a public server)

If any of those aren't true please contact Stripe support.

If all of those are true we may have misunderstood your question; please provide more details below.

Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.

terse thistle
#

@rotund ether
Hi, I am integrating dispute handling in my payment system.
I’m using the charge.dispute.closed event to update the status of disputes (won, lost, or expired).

I noticed that for a single dispute, Stripe delivered the same event twice at exactly the same time before my endpoint could respond with a 2xx status.
Is this expected behavior, or is there any configuration that could cause duplicate webhook deliveries for the same event?

outer nacelle
terse thistle
#

@outer nacelle
I am already handling retries from my end. However, I noticed that for some events, Stripe delivered the webhook only once, while for others (like charge.dispute.closed), Stripe delivered the same event twice at the exact same time before receiving my 2xx response.

Could this difference in delivery behavior be because my server took longer to respond with the 2xx code?

Here is an example event where Stripe delivered it only once at the same time:
evt_1Rva0FF2Yo6qjyLan8brgSju

outer nacelle
#

I don't think this is because of the delay in returning the 2xx. Do you have an idea of how many events have had duplicate events?

terse thistle
#

Let me check

#

@outer nacelle
I have check my system log ad stripe dashboard log and I got to know that
Since 20th August 2025, I’ve noticed a change in Stripe’s webhook delivery behavior.

Additionally, I have multiple webhook endpoints configured. For the endpoints where I don’t need to handle a particular event, I simply return a 2xx response to acknowledge and ignore it.

outer nacelle
#

Since 20th August 2025, I’ve noticed a change in Stripe’s webhook delivery behavior.
Could you provide more details on what the changes are or is it the duplicate events?

terse thistle
#

@outer nacelle
It happening only for charge.dispute.closed event (duplicate event)
It is duplicate event.
I made change that I have additionly added code to transfer counter dispute fee to my master account from connect account for my dispute lost statu since stripe charging counter dispute fee.

rotund etherBOT
golden quail
#

You've only shared 1 (?) event so far where duplicates were sent. Are there others?

terse thistle
#

Yes there are other also,
Let me share it with you.

golden quail
#

I'd probably recommend writing in to our team and we can invesitgate the cause further. In the meantime, you should guard against potential dupes as outlined on that link