adam_webhooks | Stripe Developers | Page 1

mortal cipherBOT Aug 6, 2025, 9:52 AM

#

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

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

#

indigo orbit Aug 6, 2025, 9:56 AM

#

hi there!

#

a refund can first susceed, then fail later. so you need to listen to refund.updated to keep track of status changes.

mortal cipherBOT Aug 6, 2025, 9:58 AM

#

indigo orbit Aug 6, 2025, 9:59 AM

#

so to summarize:

listen to charge.refunded and mark the refund as successful on your end
listen to charge.refund.updated and update the refund status accordingly

tribal lily Aug 6, 2025, 10:01 AM

#

We listen to refund.updated and event. When refund is failed the statuses in the upcoming refund.updated events are still succeeded.
Please check events produced for this refund re_3Rsgxu4efDnlSD781A8P29Br and the object itself. There is no single event that has failed status and the refund is failed

full patio Aug 6, 2025, 10:07 AM

#

refund.failed: https://dashboard.stripe.com/test/events/evt_3Rsgxu4efDnlSD781AewBrbI

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

tribal lily Aug 6, 2025, 10:09 AM

#

Please check shared images.
The status in the refund is failed but there is no single event with such status.

full patio Aug 6, 2025, 10:11 AM

#

That has to be a Dashboard bug then. I'm looking at the event payload and clearly status: 'failed':

payment_intent: "pi_3Rsgxu4efDnlSD781sc6iGB3",
    reason: null,
    receipt_number: null,
    source_transfer_reversal: null,
    status: "failed",
    transfer_reversal: null
  },
  previous_attributes: {
    status: "succeeded",
    failure_balance_transaction: null,
    failure_reason: null
  }```

#

You don't even have a webhook setup to receive refund.failed events?

#adam_webhooks