#beast_subscription-retry
craggy remnantBOT
👋 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/1300846473453375579
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- beastboy_best-practices, 17 hours ago, 8 messages
normal mountain
For building our failed payment system, I plan on just listening to invoice.payment_failed. When we receive an event, I save the invoice ID and will just attempt to programatically pay this over a course of time. Are there any implications you forsee me doing this?
chrome forge
Hi 👋 yes, that is correct. You can use Test Clocks to test this scenario in testmode and ensure the behavior you see matches what you're expecting though:
https://docs.stripe.com/billing/testing/test-clocks
craggy remnantBOT
marsh jungle
beast_subscription-retry
normal mountain
Is it okay to only listen to payment failures via invoice.payment_failed?
marsh jungle
@normal mountain yes that is the most common approach
normal mountain
and I just need to store the invoice id and just call stripe.invoices.pay to attempt to pay it everytime?
marsh jungle
yes