#jinmatt
shy muskBOT
Hello jinmatt, we'll be with you shortly! 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.
• https://discord.com/channels/841573134531821608/1163968325886414919, 0 days ago, 14 messages
• https://discord.com/channels/841573134531821608/1163961893929615360, 1 days ago, 4 messages
• https://discord.com/channels/841573134531821608/1162106366236835920, 6 days ago, 4 messages
somber flower
hi there, can you share the request id [0]? it'd look like req_xxx
celest axle
@somber flower req_YhwiajwDeNlKRx
@somber flower btw I'm testing this in test mode now, so the request_id is not in live mode
somber flower
that request id you provided doesn't show that error message you mentioned
can you check again and share the request id where you're seeing billing_cycle_anchor cannot be later than next natural billing date (1700272444) for plan
celest axle
@somber flower can you check the log? https://dashboard.stripe.com/test/logs/req_z9isrQQAVGGBH0?t=1697594044
sorry, the previous req id was wrong
this is the correct one req_z9isrQQAVGGBH0
somber flower
like what the error message mentions, you can't set the billing_cycle_anchor later than the next billing date. The billing cycle anchor is to set the date/time to bill the customer every month. So for your use case, you can set it to the datetime you want the customer to be billed every month (but make sure that you set it before the next natural billing date), then apply the coupon to ensure the customer doesn't have to pay till e.g. 2 months later
celest axle
so do I have to change the proration behavior in this case?
somber flower
i don't think so, but you should test it to make sure it works as expected