Zhili

[fleet kestrel]

Correction: by "$21.00", I actually meant "$11.00", thank you!

[thick portal]

There's a couple ways to do this:

• Offer a discount coupon/code for the first month.
• Apply a customer balance credit to discount the first month.
• Use two separate Prices and schedule the transition to the more expensive one after the initial period: https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#upgrading-subscriptions

[fleet kestrel]

I currently have products A, B and C that all charges $5.00 per month. I am now trying to create a product D called "Bundle", where users can subscribe to D and get access to A, B & C, while paying lower prices (e.g. $1.00 first month, followed with $10.00 per month). Is the first approach the most suitable one? Thank you!

[thick portal]

I'd recommend reading the documentation and decided which is more suitable for your needs

[fleet kestrel]

Thank you!

If I have a second question that is only somewhat related to the ones above, should I continue here or start a new thread? Thank you!

[thick portal]

Here is fine

[fleet kestrel]

Got it thank you.

As I've mentioned above, my app is working fine with product A, B and C, where all of them charges a fixed $X per month without any trial periods. I am now trying to create a product D on Stripe dashboard called "Bundle": if a new user subscribes D/Bundle, he or she would get access to A, B and C.

I am having trouble with the following:

1. how to handle the provisioning part under the Python/JS-heavy development, once a successful payment has been made. In other words, if users subscribes and pays for product A, they should get access to A; Sub'ing B-> Getting B, etc. But I am confused by how to make the backend to grant access to [A, B, C], when users subs and pays for D (the bundle).

My code looks very similar to the python example here: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=checkout#provision-and-monitor

2. I've already implemented the CheckOut flow in the way where users are not allowed to proceed to the payment, if they "Submit" products that they are already subscribing, not sure if that would cause a conflicts with (1) above.

Thank you!

[thick portal]

1. That's something you'd handle in your application logic, nothing inside of Stripe can be used to determine what subscribers of a certain product get access to. Do you have a specific question concerning webhooks?

2. I don't understand what you're asking me.

There's no 'bundle' concept like you describe. So you need some logic in your app that provisions the correct access to features/products according to what Stripe prod_xxx/price_xxx they're subscribed to

[fleet kestrel]

Thank you. Would you please point me to the most relevant documentation? Is there anything better than this one: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=checkout#provision-and-monitor

[thick portal]

Yeah that's probably the best reference for provisioning access. Obviously the details are specific to your application, though

[fleet kestrel]

Does my idea sound like something I can at least hard-code, somehow?

[thick portal]

Which idea?