#rovarma_api
mystic vaporBOT
👋 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/1375099838802170021
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tired quiver
I can see that the update endpoint indeed has a days_until_due parameter, but we have never set that, and it has worked fine for years. The docs also don't mention anything about it being required when collection method is send_invoice
tender crescent
Do you have an example of a previous request like that that worked? Looking in your API logs, the recent examples I see of updating subscriptions all use collection_method=charge_automatically, like this one: https://dashboard.stripe.com/logs/req_Ka3erbJdZkDB4r
If an invoice is sent via email it needs to carry a due date, set either using days_until_due or you can use due_date I believe. It can be immediate / zero days if you want it due right away.
But yes, this is tied to using send_invoice
tired quiver
Thanks, good point. I see that we set collection_method to be whatever the collection method is set on the subscription, which for this subscription (sub_1PQmtqBy4su9ppSN3EtOjuYn) is somehow set to Send invoice according to the dashboard. However, we don't specify this ourselves -- the subscriptions are created through Stripe Checkout
Any idea how a subscription could end up in a state where its collection_method is send_invoice?
Just sampling other subscriptions, they're all set to charge_automaticallyas I'd expect
tender crescent
Someone on your team updated it via the Dashboard in January: https://dashboard.stripe.com/logs/req_9Ox0jjSh0uu43I
tired quiver
Hm yes, I do recall that, but that wasn't a direct change: they were having problems with paying through their card back then, so I updated the subscription manually through the dashboard to add a seat with an invoice for a one time change, but apparently that changed the collection method on the subscription for all future invoices as well?
I guess that explains it.
though it is a bit unexpected behavior
we can fix this on our end to deal with this case, though as mentioned, the docs aren't very clear about this being needed
(days_until_due having to be set if method is send_invoice)
tender crescent
Yep, or you can set it back to charge automatically in the update if you want