#varchar-subscriptions
jagged sandal
Hello! Can you share a Subscription ID here and clarify what behavior you expected to see instead?
fallow flax
yes, thanks for the help. I've been trying to debug this for a few days now
subscription_id: sub_1LKY9ICQoxfYDatTQ5OFXaZR
I singed up (quantity 1) with a promo code for a free year of the subscription, normally $250.
I immediately changed the quanity (via the api) to 2, which should charge the customer an additional $200 for the second quantity
what actually happened though was the customer was charged $450, the full price of the subscription with a quanity of 2 even though the user had just purchased a full year of the subscription (quanity 1)
still with me?
fallow flax
np, thanks for the help!!
jagged sandal
Ah, this is happening because you're using a one-time coupon. The coupon is applied only once when the subscription is created, and then the next time you go to to update the subscription there is no coupon to apply, so we charge the full $450. You'll probably want to change your coupon to be repeating and set duration_in_months: 12 (https://stripe.com/docs/api/coupons/create#create_coupon-duration_in_months) so that it's applied to the full year
fallow flax
ok, I want to make sure that the coupon won't work for their second year. We only give the discount the first year. You think it's safe to set it as repeating?
what is confusing to me, is why am I creating a new subscription? I"m only updating the quantity.
jagged sandal
I don't believe you're creating a new subscription - the updates are creating new invoice items that reflect the prorations, not a new subscription.
fallow flax
I tried setting the proration_behavior to none and to create_prorations but nothing changed the behavior
so you don't think this is an issue with proration?
I think this was working appropriately very recently but I'm afraid a proration behavior was changed somewhere on the dashboard
jagged sandal
No, it's not an issue with proration - you should continue to either set create_prorations or always_invoice (if you want to invoice for the changes immediately)
The issue here is the coupon
fallow flax
got it. I'll make that change. Thanks so much for the help!
I'm sorry, I don't think I can create a coupon that's always valid for the first 12 months after it's used
I can only set the end that the coupon can be accepted, that that end date would need to be dynamic per user.
jagged sandal
Can you give me some more details? I'm not fully following what you mean by the end date would need to be dynamic per user - do some of your users need to have coupons that are shorter than 12 months?
fallow flax
in the dashboard, on the coupon creation form. I can set the redeem by on the coupon and the expires_at on the promo code. That isn't what I want
these codes will be used in perpetuity, but they should only apply to each customer's first year of the subscription
If I set the expires_at or the redeem_by, then these codes will cease to work for anyone after a year, which isn't what I need
jagged sandal
Ah, you're creating this through the dashboard - you want to click the "Duration" drop down and then an additional text box should appear allowing you to set how long the coupon should last
fallow flax
oh, I need to set the duration to "multiple months" and set it to 12 in my case it seems
does that sound correct?
jagged sandal
yup!
fallow flax
Just wanted to check back in and let you know your suggestion worked perfectly. Thanks so much for the help!!