#david44357
restive aspen
twilit aurora
Hello! Any of those might be appropriate, it depends on your use case, desired payment flow, and overall business model. What does the ideal payment flow and customer experience look like?
steady pasture
User signs a contract when they create an account that explains the 36 month payment plan. When they go to the "Billing" section, it says $### total bill: $### per-month for 36 months". The user should be able to click the "Start Payments" button to reach something that asks for their credit card info, then starts the payment schedule.
twilit aurora
It sounds like you want to control the UI for this? Or do you want to send them to a Stripe-hosted page to collect their payment info?
steady pasture
Stripe-hosted would probably be easier if it can be done that way.
twilit aurora
Do you want to accept a payment when they provide payment details, or only collect the payment details without a payment at that time?
steady pasture
Their first scheduled payment would go through at the time they click start monthly payments.
twilit aurora
Okay, so the flow would be 1) click start payments 2) they get redirected to a page at Stripe where they can provide card details 3) after that's done they're redirected back to your site and you attempt to process the payment 4) you show success or failure details. Is that what you want to build?
steady pasture
It would have to be: (1) Clicks start payments (2) app launches browser URL and passes price information (3) Stripe website sets up 36 monthly payments based on the price the app passed to it.
However, I didn't think the Stripe-hosted options would let you pass a dynamic price or quantity. Each user would have a different price.
twilit aurora
The Stripe website (Checkout) would not be able to set up the Subscription Schedule you're describing. That's something you would need to do on your end, on your server.
The dynamic price and quanity is no problem, the issue is the Subscription Schedule.
What you might want to do, though, is use Stripe Checkout to create a Subscription, then after that you can attach a Subscription Schedule to the Subscription created by Checkout.
You can use price_data to specify ad-hoc/dynamic pricing info for each Checkout Session as you create them: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-line_items-price_data
steady pasture
Are you thinking:
/v1/subscriptions or
/v1/checkout/sessions
twilit aurora
The latter.
steady pasture
kk thanks! I'll take a shot at it
twilit aurora
You would create the Checkout Session, send your customer to it, then when Checkout succeeds and the Subscription is created you can then add a Subscription Schedule to it so it ends in 36 months.
Will that approach work for you?
steady pasture
Yah, that should work. I'm working on it now. Thanks so much!!