#emd-schedules-checkout
silk walrus
depends a bit what you're trying to do exactly. They are the most common ones yes
pulsar vine
we are setting up Ramadan donations, and there's a focus on the last 10 days of ramadan. So people can come to our site at any time during ramadan to set up donations for the last 10 days
if they come in with < 10 days left then it's only for the remaining time
it's a perfect use case for Subscription Schedules, but we use Checkout exclusively (and frickin' love it!!)
silk walrus
can you outline what you're trying to do more specifically? Because you know if there's more or less than 10 days
pulsar vine
which part isn't clear?
we want to set up donations that recur daily, for the last 10 days of ramadan
silk walrus
ah you didn't say "recur daily" so that's the part
pulsar vine
oops, sorry
silk walrus
like I don't get what you're trying to set up and why schedules are needed
can you give me an example payment schedule?
pulsar vine
haha ya, sorry
what do you mean?
the payments will be daily, like a price w/ a recurrence of 1 day, and a value of $1, so they can choose the quantity
so on each of the last x days of ramadan (10 if they set this up before then, x when they do it x days before the end)
silk walrus
so why is it a schedule exactly?
usually a schedule is something like "$100 a month for 3months and the $600 a year for 3 years"
but it seems you do "no payment until the last 10 days then charge $1 daily then cancel after 10 days" right?
pulsar vine
because it needs to start in the future and end at a specific time
pulsar vine
but it seems you do "no payment until the last 10 days then charge $1 daily then...
yes
afaik, you can't start a subscription the future, without using a trial
(or a schedule)
silk walrus
yeah but mostly trial makes sense in that case to me
but I think I'm just "too used" to using the trial "hack" 😅
pulsar vine
ya, going to play with both to see which feels better. Too bad checkout session doesn't s upport the schedule stuff, would be so simple
silk walrus
yeah but schedules are really complex 😅
your use-case is definitely an easier one "start in the future with a real end date"
but it's hard to do "phases" cleanly in the API for Checkout that is trying to be simple
pulsar vine
ya I can understand that, but you can make them on the front end
instead of passing a subscription object to the create session, pass a schedule object
you already have to pass all the subscription info, add a 'phase' array and DO IT!! lol
silk walrus
but you don't really pass a subscription to the session, you pass line items
pulsar vine
I believe in the stripe engineers, they can do it
silk walrus
so now Checkout needs to understand the concept of a subscription schedule with staggered line items, without making it extremely confusing for 99.9% of users
LOL
that;s fair 😂
I think what you want is instead a start/end date for your subscription without having to go through a schedule :p
silk walrus
yeah exactly. One day!
pulsar vine
TOMORROW
silk walrus
loooooool
I'll be honest, unlikely to happen this year so the trial part is your best trick :p
but this is a great example of what we could build so I'm sharing it with the team now
pulsar vine
or the webhook/future stuff
trials mean message get sent etc, we don't really want that
silk walrus
yeah the problem with future stuff is that you don't clearly show how much you're going to charge which is also a bit annoying, but it does work
pulsar vine
and we don't want folks to be able to cancel etc
pulsar vine
yeah the problem with future stuff is that you don't clearly show how much you'r...
oh, ya that's just what I was going to test and check
pulsar vine
but this is a great example of what we could build so I'm sharing it with the te...
yup, adding the start would be the easiest all around, I think
silk walrus
agreed, just shared that with the team but it's unlikely to happen soon at least!
silk walrus
😂
pulsar vine
thanks for you help
silk walrus
@pulsar vine do you have a website we can look at or want to share your account id in private?
Helps tracking requests when it's tied to an account (in case we were to build this one day)
pulsar vine
tied to a stripe account you mean?
silk walrus
yeah
silk walrus
any Checkout Session id cs_test_123 is enough
pulsar vine
in here?
silk walrus
yeah it's fine it's mostly an object id no one can do anything with, but you can DM me too!
pulsar vine
cs_test_c1kfvZzp9yEs5olLHBbylgo0tQUgbzzIfKaYJ4unXCHeDqLH4qZ5udk6Xs
just did that one (trying out the "future" workflow)
silk walrus
perfect thanks a lot!
pulsar vine
tell they can relax, Wednesday would be fine
no need to work on the weekend
lastly, how do set a subscription END in a checkout session?
silk walrus
you can't either 😦
you have to set it after creation. Easiest is to turn the subscription in a Schedule and set the number of iterations. You can also use cancel_at but you have to make sure you set the right timestamp so that you don't get invalid proration
pulsar vine
so you can't do the trial either
silk walrus
you create a Subscription with a trial period and you say $1/day and you don't show the cancelation date but you say it after session completion
pulsar vine
so we need a webhook for this one too, to get the new subscription and cancel at the end of ramadan
silk walrus
you can do this on session completion really but mostly yes
pulsar vine
sure, whatever
still a webhook
those are two not great options, unfortunately. One way has no information in the checkout (setup) and the other has confusing messaging (trial, no end date etc).
silk walrus
agreed for your use-case it's not the best experience unfortunately