#Ragnar-subscriptions
1 messages Β· Page 1 of 1 (latest)
Take your time, im heading to lunch right now π
would be happy to continue chatting about this when you do come back
I am, did you find out anything?
subscription schedules is a good start
Ok, do you have any tips where I can find more information apart from the docs?
if you have specific questions I could help you out
I have read trough the docs about the topic jet im not quite sure how subscription schedules work towards my goal, only that they could be useful. How do they work together with the checkout page? Are there any more docs but the plain REST-API definitions?
the user will be forced to subscribe for the first 12 months at least
when you say this, Stripe doesn't really have the ability to control subscription cancellation, this is a logic that you need to handle in your code's logic
But then the user could just enter the stripe dashboard and cancel anyway?
they don't have access to your Stripe Dashboard
Yes, but they have their own subscription panel or did I unterstand this wrong?!
are you using Customer Portal(https://stripe.com/docs/billing/subscriptions/integrating-customer-portal)?
But i could, once the user requests to cancel create a phase to cancel the subscription after the subscription period end?!
π¦
are you using Customer Portal(https://stripe.com/docs/billing/subscriptions/integrating-customer-portal )?
nvm
We actually plan on using the protal - probably. Right now we want to get to know the boundaries of stripes capabilities to have a good base for planing our integration.
it is, i had to change the languaga to view the page π
no worries
AFAIK when a user cancels a subscription it will still be available until the end of the billing period
honestly I'm not sure if it's possible or not to do the minimum cycles
I will have to look at this
it might take a while, sorry for the inconvenience
So if we opt to not use the protal a user will only be able to cancel via our code?!
No problem, this is by far the best support i had in a while!
yes
Well, that is good to know, so we could just ignore the customer panel and implement our own 'panel' for viewing and canceling subscriptions within our app.
it would be good to take a look if Stripe provides an option for that, but I'll need to dig in a bit and try to ask some colleagues about it
that would be great.
unfortunately, I don't think we support this use-case out of the box
On the other hand
Customers canβt cancel subscriptions that are attached to schedules.
https://stripe.com/docs/billing/subscriptions/integrating-customer-portal?platform=billing#limitations
It sounds like this would serve our use/case exactly. Thank you very much for your help!! I think I can continue on my own from here. If not, i will check back! π
please let me know if you need any more help
so I'm back with an update
You can use the Customer Portal for the Subscription managed by a Schedule, you can't cancel it but the user might be able to upgrade or change their payment method
Ok, thank you again, we will discuss this with our customer, they have quite strict rules for what sould be allowed and what not
let me know if you need any more help
I will, thank you π
hi, what's up
Or anyone else if tarzan is currently not available. π For legal reasons we have to display additional information during checkout. Is there any way to provide additional text information when creating a checkout session, that is displayed on the checkout screen (ideally right above the checkout button)? So far the only option I can see is to create a custom checkout page with Stripe Elements, but I'd like to avoid this since our schedule is already really tight.
Hi, thank you for reopening.
that's not possible no
common feature request and we might support it one day but nothing available today
you could show the info before the redirect to Checkout perhaps
The reason why im asking: as I explained to tarzan, our customer wishes minimum subscription periods like: pay monthly but cant cancel within the first 12 months. At least in Germany its mandatory to show such information beneath the checkout button for legal reasons. As far as I know it is not sufficient to tell the customer before redirecting to checkout.
So it sounds like im bound to implementing a custom checkout page with stripe elements?
if that's a hard requirement then yes
Ok, thank you for your help.
Unfortunately it is. π¦
if you think our Checkout solution is not in line with a local requirement please write to https://support.stripe.com/?contact=true with the details of the relevant law etc so we can escalate to the product team, or let me know
Ok, but I think the problem is more about the very special requirements of our customer, that in turn lead to a very special legal situation that is hard to capture with the general checkout page.