crawl_customer-portal-cancel-button

[distant spade]

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

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

[deft skiff]

hi! looking at this now

hmm, off the top of my head i don't think this is possible but let me dig a bit to see if i can find anything

[bold elk]

that would be nice

currently the settings consider that both buttons are the same

but this is 2 diff flow

would be nice to separate it in the settings

or via api

[deft skiff]

ok yeah, the same setting applies to both and i can't find a way to separate them

can you share more about your use case? do you want to handle cancellation via API but then allow people to stop cancellation via the portal?

right now the best i can think of is creating 2 different configurations, one with cancellation enabled and another without, and conditionally deciding which configuration to use when creating a session

[bold elk]

yeah, we want to handle the cancelation, to gather feedback
and we have a ai agent, that discuss this feedback in real time with the user

but for the "dont cancel anymore" flow, would be nice if we dont have to duplicate this

when a user change is mind

[bold elk]

the stripe button is perfect, for the dont cancel

how do we create the 2 diffenrent config ?
and use them on the api ?

[deft skiff]

this API can be used to create portal configurations, and then those configurations can be passed in when creating sessions via this parameter

so you would create one config with features.subscription_cancel.enabled: true and one with features.subscription_cancel.enabled: false

[bold elk]

do I need to create the portal config ?

or I can just pass the param directly ? when creating a session ?

I dont see a need for the config, if I can create each session dynamically with a params

[deft skiff]

no, there's no parameter for directly passing portal session options when creating the session, you need to pass a config