#Zhili
1 messages · Page 1 of 1 (latest)
Hello! It would probably be best to implement that as a coupon on your end, then create a Subscription Schedule with phases that made those changes over time: https://stripe.com/docs/billing/subscriptions/subscription-schedules
If my backend for Checkout relies heavily on stripe.Subscription.create, which takes coupon as a string obj, there isn't a way to simply just apply 2 coupons codes, right?
Correct, only one Coupon can be applied at a time.
Also, for better-tracking purposes (easier to track how many "Bundles" I sell), I also attempted to create a product D named "Bundle", which costs $20.00 per month, with a "-$15.00" coupon to bring first month's payment down to $5.00. However, I ran into some conflict issues when I try to code the backend with the following logic:
User Selects and Subs Product D =>
User's Payment Method is Validated =>
Product D status becomes ACTIVE =>
Opens up access to Product A, B, C
I don't see any error generated, but during QA, users lose access to all products they've subscribed, even if they concurrently subscribed all products A-D. Does this mean Stripe's price IDs and product access on my server have to remain a strict 1-to-1 relationship?
I'm not sure I understand what you mean when you say they need a strict 1-to-1 relationship, can you provide more details about that part?
What are some of the approaches when Stripe users want to promote a bundle product that sells a lower price, comparing to subscribing products individually?
I think the most common approach is probably to have Products A, B, and C, and then each of those Products has two Prices: the normal Price and a bundle Price.
Just to make the math simple, let's assume the normal Price for each of those Products is $10 and the bundle price is $8. For normal Subscriptions to individual Products you use the $10 Price. When you create a Subscription for all three Products you use the three $8 bundle Prices, which means the total is $24 instead of $30.