#ben-clum_api
tardy monolithBOT
đ 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/1508833660638597354
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
tardy monolithBOT
burnt rose
hi there, looking into this now
tribal needle
here's the latest API attempt: req_j1kPbH6eqWPPPk
burnt rose
it looks like the /pay endpoint was called on this invoice a bunch, which caused the internal Payment Intent to be canceled automatically due to too many confirmation attempts (we document this a bit here). best way to re-charge the user would be to void this invoice and create a new one
tribal needle
shouldn't stripe be voiding the invoice if that happens? it seems like if an invoice is open and the dashboard allows you to attempt a retry, that's misleading UI at the very least right?
burnt rose
that definitely does seem like misleading UI if the dashboard is still allowing you to attempt payments, but my team isn't very familiar with the dashboard. I think recreating the invoice is the best way to get unblocked, but you might consider writing into support to see if a more dashboard-focused team can take a look at this https://support.stripe.com/?contact=true