#draakar_unexpected
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/1301209130257743883
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Interesting, I see that there was a charge succeeded event and a payment failed event for this charge within a second of each other. Looking in to what exactly happened here. Can you tell me more about the "payment intent requires a payment intent. Id" issue? I am seeing an error related to payment intent state in your logs but not payment intent ID https://dashboard.stripe.com/logs/req_TGh6IPy4Bh8Z75
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Hello the id is pi_3QFbzqGOs2bxG0Rw1sUkjycs
Right, I see that intent and I linked to a request related to it, I am more curious about what you mean by "payment intent requires a payment intent. Id" specifically. I don't see anything in your logs that I can immediately connect to that
Sorry I misstyped it it was missing payment method
The PaymentIntent requires a payment method
Ah gotcha, that is likely from the payment failing. When a payment fails it is expected for an intent to go back to its default status which is requires_payment_method. Still looking in to why you got the success and failure at the same time
yeah, that's it the customer was able to go trough the happy path and we recieved the webhook saying the payment was ready to be collected
Apologies for the delay, still looking in to this. It looks like internally there was an error about the payment method already being consumed, but that doesn't make sense because this was a payment where the customer input their info through an elements page. I am reaching out to my colleagues for help and will get back with what we can find
Thank you so much, take your time
It looks like this was a bug on our side. Your code looks to be doing what it should. I am escalating this internally so we can identify and address the bug. If you haven't already you can have your customer retry the payment and it should succeed
Thank you, we already asked the customer to re-do the order
Good to hear, I think we are good on our side for info to investigate this with. Anything else I can help with at the moment?
That's all thank you for your support
Of course, and thank you for your patience on this!