hugo_docs

[winged zealot]

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

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

[minor atlas]

Hello! I don't think what you want is possible with the Portal, but let me double-check...

[coral cloak]

Sure!

If turns out it's not possible to do that with the Portal, could you give me a workaround to achieve this ?

It should be possible to achieve these 2 simple rules without having to re-create a whole custom subscription management UI.

[minor atlas]

Yeah, I think what you'd need is an additional option here that would be something like increasing_item_amount which doesn't exist: https://docs.stripe.com/api/customer_portal/configurations/create#create_portal_configuration-features-subscription_update-schedule_at_period_end-conditions-type

The workaround would be to not use the Portal.

I can flag this as a feature request internally, but I can't say when or if this would ever be implemented.

[coral cloak]

okay, thanks for your time, though!

[minor atlas]

Yep! Let me check one more thing before you go...

[coral cloak]

Thanks flagging this, it's almost a bug that it's not possible...

[coral cloak]

Maybe it's possible to use my own proration amount when creating the portal, so I keep the proration setting ON, while it will be set to always paying the full price ?

[tight plume]

fyi i'm stepping in for rubeus on this! i'm checking with other colleagues about the portal's behavior to make sure that behavior isn't supported

ok yes, confirmed that unfortunately this isn't currently supported. i agree it makes sense as a feature so i'm working on filing that feedback now, but as rubeus stated above we can't make guarantees with feature requests

[coral cloak]

Gotcha, thanks for your time.

[tight plume]

can you explain what you mean by using your own proration amount in the portal? what API / param does that correspond to? a step by step example of what you're thinking might be helpful

[coral cloak]

I mean, when creating the portal, passing a parameter to use a custom proration amount. to be used in case of an upgrade

In my case I’d pass 0, so the customer always paying the full price. But one might calculate his own proration amount (based on credits consumption or anything) rather than time.

So this would fill many use-cases.

If that makes sense…

[tight plume]

ahhhh ok, i think i understand what you mean, but i don't think that's possible with the portal either. the sessions and portal config objects are pretty simple and mostly just allow for turning features on and off - i think if you wanted to do what you're looking for you'd need to be updating the subscription object directly
https://docs.stripe.com/api/customer_portal/sessions/object
https://docs.stripe.com/api/customer_portal/configurations/object

[coral cloak]

Yes. It was just a suggestion