#smitit1999_unexpected
candid geodeBOT
👋 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/1311254876298280991
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
zinc trench
Hi, let me help you with this.
I see the update request was sent on 2024-09-22, but the Invoice is created on 2024-09-01, which explains why it wasn't voided.
summer osprey
@zinc trench the request was sent on 22-09-2023 right which is before when the invoice was created 🤔
zinc trench
Oh, right, sorry, it's 2023...
Ok, by looking at it now, I see that the requests to finalize and pay were made by your own backend:
summer osprey
Got it, so our workflow is that we listen to the subscription renewal webhook on Stripe subscription.updated webhook and then finalize and attempt the payment. Shouldn't the invoice automatically come in the voided state when the webhook is received 🤔 . If not, then when does it get voided?
zinc trench
You shouldn't need to make those calls explicitly, Stripe Billing will do it automatically, if needed. Generally, when a Subscription is running, you don't need to do anything at all. This also includes if the collection is paused and the Invoice is void, Stripe will not attempt to pay the Invoice.
If you didn't explicitly call the finalize and pay methods, the Invoice would remain in status=void.
summer osprey
got it, thanks Vanya!