#liz_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1333560035732619385
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
we sometimes see logs in the stripe dashboard. Other times we do not
Do you mean that sometimes you see a Charge object in the Dashboard but not always?
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
That is a case where we see the logs
In our system we logged 402 failures for this customer: https://dashboard.stripe.com/customers/cus_LnNvH5QCIiMWpD
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
but I don't see any logs for them
Did your system log recent failures (within the last 30 days) for cus_LnNvH5QCIiMWpD?
yes let me get those
On this date: "2025-01-24 02:05:19.149105" the customer's payment was declined
They also had declined payments on 2024-12-23 04:27:46.493814, 2024-12-23 07:05:35.450413, 2024-12-23 07:06:18.008395, 2025-01-23 05:59:53.546417
Hm, you might be looking at the wrong customer
oh! I have a request id for the most recent one too: req_K90CQgztPnWlmp
Yep, that's the request I'm looking at too
oh
There's a different customer in the request: https://dashboard.stripe.com/customers/cus_MeVks0L8ntskkT
and logs for this customer do include the 402 on 2025-01-24 02:05:19
ah ok you're right. That solves that. Is there any more information we can get around the reason the 402 is happening? Or that's just something that you get from the bank and then propogate back to us?
It sounds like you just send it right back. It's happening for one specific bank a lot https://www.anz.com.au/
Attaching a PaymentMethod to a customer triggers an authorization charge with the bank. In this case, the issuing bank is the one returning that decline
We usually advise merchants to ask customers to contact their issuinb bank for any do_not_honor codes
Makes sense. Ok thanks