#bensif88
1 messages · Page 1 of 1 (latest)
Hello bensif88, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• https://discord.com/channels/841573134531821608/1163885377510187108, 0 days ago, 47 messages
Hello 👋
Not sure what you mean by that. Can you elaborate?
Subscriptions Schedules can't be created directly with Checkout if that's what you're asking
that is what I am asking, yes. I want my customer to be able to purchase a 2 part plan; they pay £100 now for 2 months and then it switches to a recurring £75pm plan
I know I can achieve this with a sub schedule, but currently we generate checkout sessions to do this
Do I have to generate a session for the one time payment, then on redirect go and create the schedule?
You can create a subscription using the Checkout Session and then create a schedule for that subscription by calling the API
https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#existing-subscription
hmm i was unaware of this
The other option I can think of is,
- Charge customer $100 upfront as one-time payment
- Create a subscription for $75pm plan and add 2 months trial
if I did this, would they get 2 invoices?
They would see $0 invoices for the two months trial, yes
As I have 2 scenarios here that I am sturggling to solve;
-
one time payment for a defined period where your access (sub) will end after that time
-
upfront payment for a product that moves to a recurring plan afterwards
OK so they would get an invoice for $100 and also an invoice for $0?
So for scenario one, I could basically generate a checkout session for payment, take the payment then on redirect create a subscription with a trial period equal to the plan period paid for and set the cancels_at field?
or even on the hook for charge succeeded
So for scenario one, I could basically generate a checkout session for payment, take the payment then on redirect create a subscription with a trial period equal to the plan period paid for and set the cancels_at field?
yes, would recommend testing it out
ok, and what about scerario 2?
upfront payment for a product that moves to a recurring plan afterwards
What I recommended above, One-time payment + Subscription with trial
ok interadestering
would you recommend to generate the schedule or sub on redirect or on webhook?
Yeah I think that should be fine, again would recommend testing it all out in test mode
to be certain
yeah that would be my intention
but are you recommending we create teh subscription or schedule upon success payment and redirect, or upon receipet of a webhook from the checkout?
For which scenario?
both
It depends on your usecase and preference. I have seen merchants implement this on checkout.sessions.completed events as well as some implement it on invoice.paid event etc.
Totally fine to base it on webhook delivery
ok thanks Hanzo, you the person!