#yes_api
tiny impBOT
👋 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/1399764123117555877
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
merry hemlock
hi there, when you say "invoice", are you referring to something on your system, or a Stripe Invoice (https://docs.stripe.com/api/invoices/object)
merry hemlock
no worries! I just wanted to make sure. I think the easiest way to do this would be to track invoice creation on your backend, and every time you create a Payment Intent for an invoice, you store its ID associated with that invoice
then you can do a check of your DB to see if an invoice already has a Payment Intent before creating one
hexed tartan
I do some checks on my end. I just like redundancy, especially when it comes to managing user's payments, and was hoping there was an extra possible layer of protection through the API. Thanks for the fast response and the suggestion! 🙂