#volksman-python-schedules
viscid oak
gaunt echo
the response has "proration_behavior": "create_prorations",
I see no way to send the default proration behaviour with that
which should be none
swift elm
Hey. You can set the proration behavior with this parameter: https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-phases-proration_behavior
gaunt echo
but then I have to define the phases.items when from_sub is supposed to be doing that for me
swift elm
So, there really isn't a "default" proration per-se. Prorations are specified on a per-request basis. So if you issue a subscription update request and specify a proration, that proration is only applying for that update. It won't be set as the default.
atomic thistleBOT
This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact
viscid oak
@gaunt echo reopened your thread!
eager haven
Question for context:
gah..my thread has been archived and I can't respond...My issue is that if I create a schedule "from_subscription" a proration is created immediately...even if I modify that subscription a second later with proration_behvior set to none the proration is already created and on a pending invoice
Do you have a request ID (req_123) from when you did made this call?
gaunt echo
req_yqfDQYg2OVUa2l
eager haven
Thank you, checking in to that request...
gaunt echo
thanks!
eager haven
Of course. I see create a proration but also seems to have given them equal and opposite credit so it all cancelled out. A little unclear on that behavior at the moment but if it always does that, it should be easy enough to work around.
gaunt echo
I don't see it cancel out but I do see a draft invoice on that client account for the prorated amount, indicating to me that they will be given that prorated amount
am I missing something?
eager haven
So it turns out the proration was created because of one of the subsequent updates to the subscription schedule
Specifically this call as it only had one plan in the first phase when there were previously two https://dashboard.stripe.com/logs/req_baVv11IaW0OvUu
If you want to make that change without a proration, you will also need to pass in none to the top level proration_behavior parameter https://stripe.com/docs/api/subscription_schedules/update#update_subscription_schedule-proration_behavior
gaunt echo
that is super frustrating as the response says nothing about a proration being created or not and the phase items are all defined with proration_behavior set to none
I've updated my code to always pass a none at the top level now but hope you can see the issue with docs and response object
not sure how to fix the docs because the info is in there but it's counter intuitive...assigning additional proration_behavior doesn't see needed since we define them per phase...
anyways..thanks for the help! never would have figure that out on my own.
eager haven
Glad we can help! And I will see what we can do to make that clearer.
gaunt echo
even just a key on the response data would help....thanks again...all the best! 🙂