#xiaowo_webhooks

1 messages · Page 1 of 1 (latest)

upper galeBOT
#

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

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

west prairie
#

You would want to call Retrieve PaymentIntent API, passing in the Payment Intent Id (pi_xxx) from the webhook event you received

deep orbit
#

this is the result i cal the paymentIntent api

#

i can not figure out where is the error msg

west prairie
#

okie can you pass expand: ['latest_charge']?

#

when call Retrieve PaymentIntent

deep orbit
#

ok, let me try this right now

#

hi, this this the retrieve PaymentIntent result, which field this represent the reason, please figure me out ☺️

#

hi~

west prairie
#

Let's take a step back

#

Can you directly call Retrieve Charge API on the charge Id here? ch_3QMAAEIC1xDAOwlv04e4FKUv

#

Btw this Invoice in_1QMAACIC1xDAOwlvQ4R58bWO failed, but later it succeeded and there was another succeeded Charge

deep orbit
#

when another charge is succeed, wethere a new webhook will be send ?

#

after call Retrieve Charge Api, i find out the fail reason of ch_3QMAAEIC1xDAOwlv04e4FKUv is card_declined.

#

if another Charge is succeed, will be send the new webhook ?

deep orbit
west prairie
#

Yes you had evt_1QNKHKIC1xDAOwlvWJ9k1HU9 for the latter invoice.payment_succeeded

deep orbit
#

no, in our log, i did not receive this

#

for example, eventId: evt_1QN0bxIC1xDAOwlvADDgnM6k , i can search the logs

#

but the eventId: evt_1QNKHKIC1xDAOwlvWJ9k1HU9, is nothing

west prairie
#

Your endpoint seems not listening to invoice.payment_succeeded

#

I see it does listen to invoice.paid though evt_1QNKHKIC1xDAOwlv6AYmN8a2

#

This invoice.paid can also indicate that the Invoice is paid successfully

deep orbit
#

so what you mean is, listen to invoice.paid is not enough, if i want to proccess this problem correct, i also must to need listen to invoice.payment_succedded?

west prairie
#

Nope I mean invoice.paid is also good enough. When you received it, you can consider the Invoice is done