#gewibu_unexpected
pale canopyBOT
đ 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/1430565940998832168
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sudden pasture
then a few hours later attempted to charge them via payment intent api
I recommend logging payment intent id
Because if there's no record of the payment intent in the request log, then something likely broke down in your code prior to making the request
But yeah if you share the payment method id i can at least look
wheat mist
`then a few hours later attempted to charge them via payment intent api`
I recom...
yeah this new type of unexpected error will result in us beefing up our server-side logs to include that
pm_1SIcg2LqwvUucnvfD8AKpvkx
sudden pasture
Yeah I don't see any requests to us that attempt to charge that
wheat mist
Ok, can I ask you to double check this other payment method this customer has on their account. I want to know if they tried to charge this card in the past day: pm_1SKhFiLqwvUucnvfTJIczr0y
wheat mist
cool, likely some manner of issue on our side. Thanks for confirming!
sudden pasture
Yeah I just recommend increasing that logging
wheat mist
so payment intent id, and any other stripe data that would be helpful for us to log?