#manuel_api
reef starBOT
👋 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/1275043330262040616
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
jolly wagon
hi! yes that seems expected I think (it's a bit of an edge case we're aware of when you use confirm:true). The best way to handle this is to not look at the actual webhook, just treat it as a notification that you need to call the retrieve PaymentIntent API and then react to that (the current state of the object), that applies to all webhook events
reef starBOT
bright geyser
Thank you for the answer!
Is that the only approach we can take for now? Would not marking confirm:true solve the edge case?
tranquil flicker
Hmm, not necessarily. Omitting that would mean you'd need to make an additional API call from your integration to confirm the intent. The advice above is our official recommendation in these scenarios
bright geyser
Ok! Thank you for your help, have a great week 😃