#tavana_unexpected

1 messages ¡ Page 1 of 1 (latest)

river cloudBOT
#

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

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

lyric jungle
#

Hello! Can you give me the ID of the Payment Intent in question so I can take a look?

mossy rivet
#

pi_3Q5Ze3FEVywGTFh70k7oIsEM

lyric jungle
#

When you created this Payment Intent you specified an existing Payment Method, so there was no need for the Payment Intent to go into the requires_payment_method state; it already had one.

#

It also succeeded immediately because, when you created it, you told it to also immediately attempt to confirm itself.

#

Can you tell me more about what you're trying to do?

mossy rivet
#

So for this duplicate payment intent ( pi_3Q5ZdyFEVywGTFh71fhQhfvH ), it went to requires_payment_method because I didn't provide an existing method? The underlying problem I'm trying to solve is to understand why our system issued 2 duplicate charges when it should've been one.

lyric jungle