sebastian_webhooks | Stripe Developers | Page 1

uneven depotBOT Apr 13, 2026, 8:58 PM

#

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

📝 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.

sebastian_stripejs-breaking, 5 days ago, 18 messages

#

hushed vault Apr 13, 2026, 9:02 PM

#

👋 taking a look

#

Where are you seeing the same ID being re-used at currently?

spark isle Apr 13, 2026, 9:13 PM

#

Can I share links from the stripe dashboard? The event_id I shared is an automatic charge for the same invoice, one of 5 charge attempts for the same invoice that have the same charge_id

hushed vault Apr 13, 2026, 9:13 PM

#

My understanding is that each retry should be it's own charge. Wondering if you have an example that's counter to my expectation there.

spark isle Apr 13, 2026, 9:15 PM

#

I also ran a sigma query today so I could get an idea how often each scenario occurs on our account

hushed vault Apr 13, 2026, 9:15 PM

#

Taking a look at in_1TEITqCMpnBh61hXSek4Utx9

#

Below are the 5 invoice.payment_failed events related to invoice: in_1TEITqCMpnBh61hXSek4Utx9

I'm seeing a new charge associated with each event in the event data.

evt_1TGqmBCMpnBh61hXYVxZtGTM -> charge: ch_3TEJQpCMpnBh61hX1pcKwCaS
evt_1TGUIcCMpnBh61hXgAdXK4Eh -> charge: ch_3TEJQpCMpnBh61hX1ekpKc18
evt_1TFnDWCMpnBh61hXLznrvfFS -> charge: ch_3TEJQpCMpnBh61hX14YE7LhJ
evt_1TF2OFCMpnBh61hXoDH194ni -> charge: ch_3TEJQpCMpnBh61hX1kuxyrJq
evt_1TEJQwCMpnBh61hXR1Mt4YL0 -> charge: ch_3TEJQpCMpnBh61hX17LBhNSP

#

So it looks like we're getting a unique charge id for every attempt which is inline with my understanding. Maybe we could walk through how you're determining if a charge is being re-used.?

spark isle Apr 13, 2026, 9:58 PM

#

Hi Mossy, sorry I shared you an example where the charge_id is different.

I found one where the automatic transaction attempts are for the same invoice, with the same charge_id evt_1SSC3TCMpnBh61hXi13QViFj

All of these for Nov 4th - Nov 11th 2025 show charge id "ch_3SPudMCMpnBh61hX0Spxc1hv"

hushed vault Apr 13, 2026, 10:10 PM

#

Where are you seeing that charge ID? We don't keep event log data past 30 days so it's not as easy to investigate this example since all the events are more than 30 days ago.

spark isle Apr 13, 2026, 10:12 PM

#

I can find a more recent event, will take me a moment

uneven depotBOT Apr 13, 2026, 10:16 PM

#

spark isle Apr 13, 2026, 11:16 PM

#

sorry got caught up with a separate task. I will be ready to share something maybe in the next 15 minutes

crisp heron Apr 13, 2026, 11:16 PM

#

Okay! mossy had to step away but I'm here

spark isle Apr 13, 2026, 11:37 PM

#

Hi @crisp heron I found one with 2 of the same charge_id for the same invoice within the past few days on this invoice:
in_1TKsH6CMpnBh61hXQ3m9Lgfv

Evt evt_1TLZN0CMpnBh61hXhqtfhfuJ

#

Looking for a recent one with more automatic charge attempts...

crisp heron Apr 13, 2026, 11:45 PM

#

There are times when a bank declines a charge and tells us that we are not allowed to retry. In these cases the automatic retry system stays in place and we emit webhook events and it sort of looks like the charges are retried but we don't actually send the attempts to the network

#

And I don't think we create a new Charge in that circumstance

spark isle Apr 13, 2026, 11:49 PM

#

Hmm I see, so the reason the same charge id is shown, is because Stripe's automatic retry system is trying to attempt another automatic payment, but the bank has blocked it already, so it will emit the same charge id in the webhook?

Would you still like me to find another recent invoice with the same charge_id for automatic charge attempts?

crisp heron Apr 13, 2026, 11:50 PM

#

If you like, but it is quite likely to be the same scenario

spark isle Apr 13, 2026, 11:52 PM

#

All good, that answers my question!

#sebastian_webhooks