#ivain_webhooks

1 messages ยท Page 1 of 1 (latest)

sand zenithBOT
#

๐Ÿ‘‹ 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/1422985363562958939

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

wild parcel
#

Hi there

#

Taking a look

#

Hmm what do you mean exactly by "when the charge was actually executed"?

glossy cypress
#

Should've used the proper term, sorry.

We are used to receiving charge.succeeded only when the charge is captured, but we're seeing uncaptured PaymentIntents that are firing the charge.succeeded event for the authorization, I assume

wild parcel
#

Ah okay, let me check.

#

Yeah no this has always been the behavior... we emit charge.succeeded when the authorization is successful. Then a separate charge.captured Webhook on capture. You can check older example PaymentIntents in your account to confirm.

#

Can you tell me more about what makes you think this changed?

glossy cypress
#

Recently our users started reporting payments being marked as succeeded, but no transaction was actually made

We use webhooks to change the status of the payments on our application, and there wasn't any recent change to how we handle them that could explain this symptom. I'd expect this to be happening for a long time now, but we just started seeing reports in the past couple days ๐Ÿค”

wild parcel
#

Hmmm yeah this has been the behavior on our end ~forever

#

We never waited to emit charge.succeeded

glossy cypress
#

Thanks for checking this so swiftly, I'll see what we need to adjust here on our side ty_thankyou