#eoghanobrien_webhooks

1 messages ¡ Page 1 of 1 (latest)

fierce ravineBOT
#

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

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

dusty fog
#

Hi there

arctic geode
#

Correct

#

I'm wondering if I can always rely on the charge.failed being triggered

#

or can I always rely on the payment_intent.canceled being triggered

#

or do I have to listen for both?

#

I've seen that I can get payment_intent.canceled in test mode without charge.failed

#

but I don't know if that's the same in live

dusty fog
#

If your goal is to be notified whenever any charge fails, listening to charge.failed is appropriate. This will always be triggered for any failed payment.

arctic geode
#

Okay, that's very helpful, one issue I have in test mode is when a payment intent is canceled as part of an subscription price change then I don't get charge.failed at all and I don't understand why not

dusty fog
#

Can you share the PaymentIntent ID for this payment?

arctic geode
#

pi_3Q30mDE3c9sWyeru1IXMljRY

#

It's a test pi

dusty fog
#

Ah, I see. The reason there is no charge.failed event in this case is because a charge wasn't attemped at all

arctic geode
#

got it, that makes sense

dusty fog
#

The Customer tied to this Subscription doesn't have a default payment method

arctic geode
#

ah yeah, that I can handle via another webhook

fierce ravineBOT