#bubba_paymentintent-connect
restive robinBOT
đ 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. Thank you for your patience!
âąď¸ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.
đ 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/1214279469523804243
đ Have more to share? You can add more detail below, including code, screenshots, videos, etc.
blazing swallowBOT
twilit venture
99% of the time you are mixing up where you create the PaymentIntent server-side versus where you confirm it client-side
bubba_paymentintent-connect
rough crag
Hmm, can you elaborate? Are you saying that it might be possible that when we're creating the paymentIntent, we're using a different account from the one we're verifying on the frontend? The weird behavior is also that when I refresh the page, the error goes away. So I'm wondering if there's some stale client secret being used perhaps.
How can I check what account a client secret is associated with?
twilit venture
It's really hard to say with so little information unfortunately.
In theory you as the developer know which account a given PaymentIntent is associated with since you created it
There's no way to check after the fact. If you give me a PaymentIntent id I can tell you
rough crag
I think I found the issue. Thanks for your help!