#kaizen_best-practices

1 messages ¡ Page 1 of 1 (latest)

haughty parrotBOT
#

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

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

frank glade
#

latest_payment_error in payment_intent.payment_failed should be sufficient

timber frost
#

Got it. Thank you!

#

I have one more question. So, one of my product managers reached out to you guys and get to know about this webhook event - customer.source.contact_cardholder, which can tell us whether the customer's card is lost or stolen and we can convey the same to the customer. I tried to find the response structure for this in the docs but couldn't find there. Can you let me know if this webhook event is valid and can be used in production and if yes then what is the response structure for the same?

frank glade
#

Where did you get customer.source.contact_cardholder event information from? I don't see this being discussed in this channel. Do you have an example event ID (evt_xxx) that I can look into?

timber frost
#

No, I don't have any example event ID for this. I just got to know about this from my product manager. Do we have any webhook event that can tell us if a customer card is stolen/lost?

frank glade
#

I'm afraid there is no event sent for such situation. However, when there is any payment attempt on the stolen/lost card, such error will be returned

timber frost
#

Got it. Thank you for the clarification!