#veesh_api
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/1337343541705441321
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! Usage based billing doesn't support proration, so what you want to do is unlikely to work : https://docs.stripe.com/billing/subscriptions/prorations#when-prorations-are-applied
let me think if there's a way to achieve what you want
i just wanna backdate the upgrade
am i able to add a subscription item backdated + cancel the usage for the first item?
Depends when the meter events were created as they're immutable after 24 hours. You'd need to create a negative event to offset the usage you want to 'cancel'
This should all be explained here I think: https://docs.stripe.com/billing/subscriptions/usage-based/manage-billing-setup
okay, i can do the negative event thing
i see that i can backdate a subscription and it'll pick up the usage, but can you backdate a subscription item?
i sure hope rate cards makes this easier to deal with
You'd use proration_date in the update call: https://docs.stripe.com/billing/subscriptions/backdating#backdating-update
and that would work to pick up the usage?
I don't think so:
On future invoices, we reflect only usage that occurs after the update. For example, say you have a monthly subscription that you switch from price A to price B on 16 January. At the end of the month, the invoice includes usage from 16 January to 31 January at price B. Usage from 1 January to 16 January isn’t billed.
I'd recommend just testing all this out. It's a pretty unique edge case that I'm not familiar with