#arvindkgs-backdate-sub
young sinew
Hey! 'That depends'. Have you tested it out? https://stripe.com/docs/billing/subscriptions/backdating
untold sonnet
Yes, I have. Sometimes I see a split of 2 items, sometimes a consolidated single item
young sinew
Can you share the API request(s) you're making
untold sonnet
@young sinew req_yemqE95bNmKElb to create the backdated subscription
in_1KVdbABuQq6cUmE7lGWqrkOW - initial invoice that contains a single item
Also if you notice the invoice - in_1KVdbABuQq6cUmE7lGWqrkOW you see that amount is - $120, but it should have been $100 because of the discounts added
But discounts though shown are not applied
Strangely when I am not setting billing_cycle_anchor the discounts are applied
And amount due is reduced
req_KGm6Eql2Xpdg22 - API request to update invoice to include discounts
Does adding billing_cycle_anchor mean the discounts will be added next invoice?
young sinew
Sorry, checking this now
Ok, I feel like there's a couple different questions here
Do you have an example of a request where there is multiple invoice items?
Or is that no longer an issue?
untold sonnet
@young sinew That is no longer an issue. Lets focus on the discounts not being applied
young sinew
Got it
This seems like an edge case, but my assumption is that as you're backdating the subscription start to Feb 1 and both coupons were created after (Feb 21) then they aren't applied
I guess you could test that theory by backdating to prior to the coupon creation (Feb 20)
untold sonnet
@young sinew Makes sense. By this theory I think any backdated subscription will not apply coupon, because there is no way to backdate a coupon
young sinew
I guess. Unless they were created before the backdated start date
Again, worth testing (I could be wrong and it may be something else)
untold sonnet
Okay I will test it. But this is not feasible to implement in production code. I cannot have all coupons created in advance, as this is something unique per customer and can be created dynamically
young sinew
Yeah, I get that. There's ways to workaround it. But let's confirm this is the actual issue
untold sonnet
@young sinew nope this doesn't work. subscription - sub_1KVfbxBuQq6cUmE7Plb9K1xb (req id used to create it - req_dCjgbMOqmboQvx)
invoice -in_1KVfbxBuQq6cUmE78FNgOQSv (update discounts req id - req_8E0QvenUeVceIu)
discount - nHgCXRbt
tacit panther
jumping in for ynnoj
untold sonnet
@tacit panther When I am not setting the billing_cycle_anchor I can confirm that invoice applies the discount
tacit panther
I see, seems like a bug, but it's probably a known issue unfortunately we haven't prioritised
backdate_start_date is pretty limited and it wouldn't surprise me at all if the proration items it generates don't interact properly with coupons in all cases
I'd suggest writing to https://support.stripe.com/?contact=true with a detailed description and showing two request IDs, one where the discount applies and one where it doesn't, so we can investigate and report it.
untold sonnet
Only way around it is not adding backdate_start_date and calculate and add any pending items in the past manually
@tacit panther I have already done this. Infact you are the fourth person I am talking today