#yurtdweller_annual-invoice-upcoming
finite nexusBOT
👋 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/1470463957163577547
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
heavy hornet
Hello 👋
The webhook events you provided are both invoice.upcoming. When this event is triggered is managed by your Subscription settings, not by Stripe. An invoice is not created. What you see in the webhook event is a preview of the upcoming invoice (if no changes are made).
In our API refererence we point out
Occurs X number of days before a subscription is scheduled to create an invoice that is automatically charged—where X is determined by your subscriptions settings. Note: The received Invoice object will not have an invoice ID.
rare oriole
I don't expect for the invoice.upcoming to have been triggered by the subscriptions that we created:
evt_1Qk9hpEXjRBPmDmBBuH4OzmW
These are set to 1 year interval
heavy hornet
As I said, this is controlled by your subscription settings (which I can't see). If you go to your /settings/billing/subscription page in the dashboard and look at the "Upcoming renewal events" setting, what is the time period specified there?
rare oriole
My concern is that we sent an API request to set up the subscription to renew within 1 year, and instead it renewed within 1 hour. I am trying to understand why this has happened, as it has resulted in 2 customers having this issue, and disputes being raised against our account.
I do not see where the error is in our use of the subscription API.
heavy hornet
Those events do not indicate anything has happened. They are intended to provide notice that something will happen. Do you have examples of actual invoices that were sent to these customers?
Okay, I was able to find one example Subscription sub_1QnPpEEXjRBPmDmBznrLhOQM.
I'm looking at the history of this Invoice and I see one invoice.paid occurring on 2025-01-31 and the next one at 2026-01-31. That seems to fit the expected behavior
rare oriole
OK I am looking at the invoices and realize now that the dates are confusing because it is missing the year in the dashboard for this current year.
heavy hornet
Ugh. Okay that's a Dashboard style issue. I think they omit the year for any dates in the current year. But I can flag this is confusing for users with annual subscriptions and maybe they will rethink this approach
rare oriole
I think that would be helpful for sure
heavy hornet
Okay I can see that this feedback has already been filed. I added this as another example to help increase the importance
rare oriole
Thanks for helping me sort this out!
heavy hornet
Sure thing! Happy to shed what 💡 I can 🙂