#mp_api
patent spearBOT
👋 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/1427279149076189266
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mp_api, 4 days ago, 18 messages
cerulean cave
hey there 👋 this proration adjustment was created in response to this Update Subscription API request:
https://dashboard.stripe.com/acct_1CaQ5rJqE5f9ucQh/logs/req_jmedX80j1TrGiu
that request didn't change the price or quantity, but made an adjustment to the billing cycle by setting billing_cycle_anchor: 'now'
https://docs.stripe.com/api/subscriptions/update#update_subscription-billing_cycle_anchor
this link contains more context around how proration is handled for this type of subscription update:
https://docs.stripe.com/billing/subscriptions/billing-cycle#reset-the-billing-period-to-the-current-time
patent spearBOT
kindred stratus
ANd then he was charged again? https://dashboard.stripe.com/acct_1CaQ5rJqE5f9ucQh/logs/req_ltlpEnmwR5SfDr
merry badger
Yes, that request changed the subscription from a basic plan to a pro plan and passed proration_behavior: 'always_invoice'
In the first request, the API call cut a subscription cycle short, so we credited them for the time they already paid. In the second call, the user's subscription was upgraded to a more expensive plan, so we charged them for the difference. So both of those are expected behavior when telling us to prorate a subscription change. Does that help, or is there a specific thing you are trying to figure out about what happened here?
kindred stratus
https://dashboard.stripe.com/acct_1CaQ5rJqE5f9ucQh/invoices/in_1RtUZ4JqE5f9ucQhlGd0f9AN -> he paid for a yearly plan with quantity 2
https://dashboard.stripe.com/acct_1CaQ5rJqE5f9ucQh/invoices/in_1SG08NJqE5f9ucQhM5KcdVaj -> just changed the billing cycle. How is that possible?