#nasty_subscription-promotioncode
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1304474243177775115
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- lil_subscription-coupon, 21 hours ago, 14 messages
- lil-nasty_api, 1 day ago, 12 messages
Hi, are you able to share the subscription update request id with me? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
req_G1QvIOlRiPimce
Taking a look here
When I create the subscription with seemingly consistent params it doesn't include a discount in the discounts array, but in the latest_invoice there is a discount. This can be seen in req_EPYHPf6SYhe95y
I'm asking help from a teammate as I can't find any limitation that would prevent the discount applying. Hang tight.
Ok, thanks! I'm going to try applying the update via the items array instead of directly adding it to discounts, but this seems like a bug to me
That didn't do the trick either
Docs do specify that promotion_code field on the sub is deprecated and to use discounts, so this is almost certainly a bug
Ah, I missed something here. I was able to confirm that the discount would apply at the next renewal.
You can use Test Clocks: https://docs.stripe.com/billing/testing/test-clocks
This makes sens as updating the subscription should not change the latest invoice. Rather, it would apply on the renewal.
Can you try that?
That doesn't seem like the proper behavior. If I update sub before payment is collected it should apply any discount to the initial payment.
We need the discount to apply to the initial payment, so I suppose I'll have to just cancel the subscription and create a new one with the promo code.
Use the Test Clock, and make the same requests as above and move the Test Clock to the next cycle?
Then, you would want to pass the discount when you create the subscription
Our discount is a first time only kind of discount. So the user gets a discount on their first subscription payment and then pays reg price thereafter. So I suppose I'll just have to cancel then create with the promo code
This does seem like more of a bug than a feature to me, but at least there's a workaround
For that use case, you can use our subscription schedules API: https://docs.stripe.com/billing/subscriptions/subscription-schedules/use-cases#upgrade-downgrade-coupons
You can create two phases, one phase would have the discount and the next phase you would remove the discount. This way, the coupon is only applied on the first month
The above guide exactly addresses your use case
It will be simpler to just delete the sub and create with the coupon code. The coupon code already has the desired behavior w/o using schedules... don't want to complicate the process any further
This handles it not applying after the first payment