nerder_error

[opal sundial]

👋 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/1400169034149789760

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[calm pagoda]

I believe we'd need to pick a next best option for payment_behavior in this case.

[teal drum]

you mean default_incomplete ?

[calm pagoda]

or 'allow_incomplete'

[teal drum]

Ok probably best to simply skip the upgrade and schedule the update on next billing date?

with proration_behavior: 'none'?

I feel like upgrade with a pending prorated amount is always weird with this delayed payment methods

and the sub will go to past due until the payment settle, in like 3-7 days

what do you think?

or another option is to change the proration_behaviour: 'create_prorations' in this case?

Not sure what that will do tbh

[calm pagoda]

How close to the billing cycle is it? The proration might be minimal if most of the cycle has compelted

[teal drum]

I can't say

this functionality is intended to be used for gym memberships

so a user will be able to upgrade at any time to a more expensive price

even if it's few bucks we still need to charge it

There are only 2 realistical options in my head:

1. Skip the instant upgrade entirely, and treat it as a downgrade by scheduling the update for next month
2. Update the subscription immediately calculating the proration and then placing it in the next invoice instead of attempting to charge it immediately (not sure if this is what proration_behaviour: 'create_prorations' does

[calm pagoda]

While create prorations is the default, if say a prior call was made for prorations to be none, this could be used to unset that behavior.

Option 2 seems to be the most viable unless you want to give the gym member the remainder of the month the upgraded status at the old price.

[teal drum]

Ok understood

so based on the default payment method of the sub I decide which proration_behaviour to use

if it's card (and card-like), then I use always_invoice

if it's bank debit I use create_prorations

[calm pagoda]

Yeah, this would allow you to retain the idealized behavior where you can.