#rian_subscription-updates-pause
1 messages ยท Page 1 of 1 (latest)
๐ 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/1403031310078967881
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi, where do you see that the invoice was voided? Can you share the request id here? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
the invoice was not voided
it should have been
req_xHiwVbd6Z6lzQV
they paused before the draft invoice was generated
You made that request, https://dashboard.stripe.com/logs/req_xHiwVbd6Z6lzQV at 2025-08-05 17:09:35 UTC and passed resumes_at: '1757096062' which is in a month. You then made another request, https://dashboard.stripe.com/logs/req_G0i3fxtOApqSFn to unset the pause collection: https://dashboard.stripe.com/logs/req_G0i3fxtOApqSFn at 2025-08-05 18:32:36 UTC setting billing_cycle_anchor: "now". Which invoice did you expect to be voided?
the invoice generated at 18:14 in_1RspNuFqArqfkwbMlZbufWKs
His billing cycle end date is 18:14, so if he is paused before 18:14 comes to pass his invoice should be voided
I see what you mean here, further looking
ty
๐ @fathom burrow looks like you unset pause_collection just after: https://dashboard.stripe.com/logs/req_G0i3fxtOApqSFn
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
This was after that Invoice was created but before it finalized.
That is why it was paid on finalization as opposed to voided.
yeah but shouldnt the state of the invoice be determined by their billing cycle? If a user pauses before their billing cycle ends and unpauses after their billing cycle ends then the expected outcome of their invoice should be based on the pause configuration
i dont understand why finalization of an invoice can take hours
While I understand your perspective, that's just not how it works. Automatic finalization takes 1 hour and at the time of finalization the state of the Subscription is checked for what should happen after finalization.
i currently do not do anything with draft invoices, can i just auto advance them automatically so i dont run into this issue?
Yes you can finalize them immediately using https://docs.stripe.com/api/invoices/finalize?api-version=2025-06-30.basil if you so desire
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
In that case you may just want to attempt payment immediately using https://docs.stripe.com/api/invoices/pay?api-version=2025-06-30.basil which both finalizes and attempts to charge.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
is there normally a delay between finalization and payment? i mostly just want to make sure that the invoice is immediately voided if the collection is paused
so if finalizing it will do that then i think ill just stick with that option for now
One second, let me check on something.
ok thanks
Okay @fathom burrow sorry for the delay
So we did some testing and it seems that finalizing it yourself moves the Invoice to open but doesn't void the Invoice. Though we are testing with a test clock and it is possible that is just a quirk of using a test clock... I would expect it to be voided here.
I can file some feedback about that internally. For now, your best bet is likely to check if there are any draft Invoices for the Subscription when you resume collection.
If you don't want those to be paid then you could explicitly finalize/void that Invoice.
ok thanks for checking, i will check for old invoices then, i definitely wouldnt want an auto advanced invoice to behave differently than how the subscription is set
unless explicitly stated in the api call