#ecila_vip
1 messages · Page 1 of 1 (latest)
What do you mean by "billing_cycle go wrong" ?
Tell me what you expect vs what you actualy got
See evt_1NzXRIJrgt3ZD9jfd27guFbw
The billing_cycle for this Subscription was specified as 10/10 to 11/1 and 11/1 to 12/1, on the 1st of each month.
However, the billing_cycle_anchor is updated when I set cancel_at!
Canceling "Cancel "Subscription"" from the dashboard will leave the billing cycle out of whack.
Ok, that's because you set the cancel_at (1697511600
2023-10-17 03:00:00 UTC
,) before the previous current_period_end (1698796800)
Which means that the subscription will be cancelled before the peroid end, and that's why the billing_anchor is updated
Does that mean I should not cancel the "Cancel Subscription" from the dashboard?
(I know I can solve this by doing everything manually from the API).
I don't see a problem here really. Maybe I'm missing something, can you tell me what problem you are trying to resolve?
Ok
First, the exact menu names may be different since we are doing this in the Japanese version of the language.
You can choose "immediate", "end of current period", or "custom date" when canceling Subscription. Currently, another non-engineering team is performing the cancellation operation from the dashboard, choosing from these three options as appropriate.
However, if "custom date" is specified, the billing_cycle_anchor, which we do not want to be changed, will also be changed, which may create unexpected changes (like the cancellation of a subscription cancellation).
If this is correct, I assume that as an operation we need to prohibit cancellations on "custom dates".
As I explained before, the billing_cycle_anchor is updated because of the cancel_at, and this is the same behaviour whether you do it from Dashboard or through API
Yes. So you are saying that to avoid this, we should not do cancellations with "custom date"?
That means you can't schedule a future cancellation schedule except at the change of PERIOD, right?
I don't see a reason why you want to avoid it. Or can you tell me what you want to achieve here?
We don't want the billing_cycle_anchor to change no matter what.
At any rate, I understand the specifications. Thank you very much.
No it's not possible.
Sure, how can I help
We always try to make the first day of the month the payment date when using Stripe.
Even if we sign up in the middle of the month, the system requires immediate full payment (we are happy with backdate_start_date for this).
However, it appears that this fixed payment date rule is not a good fit with Stripe.
Would it be more Stripe-Way to allow flexible payment dates?
What make you think "fixed payment date rule is not a good fit with Stripe." ?
Which means that the subscription will be cancelled before the peroid end, and that's why the billing_anchor is updated
This is because of this rule.
The mechanism by which the billing_anchor is updated on its own is not kind to fixed payment dates.
I still don't see why it's a problem. Can you tell me why you think an updated billing_anchor will impact your application?
This is because we want to make the payment on the 1st. That's what billing_anchor is for, right?
But there's no payment after the subscription is cancelled, isn't it?
However, if you cancel the cancel subscription, the subscription will resume with a wrong billing_cycle.
That's the problem right there.
Cancellation is a terminal state, you can't resume a subscription once it's cancelled.
And I know it is difficult to backtrack a billing_cycle_anchor once it has been shortened. So if that is the spec, we need to make sure it does not happen.
Cancellation is a terminal state, you can't resume a subscription once it's cancelled.
I see? There may be a discrepancy in language.
I said "cancel the cancel subscription" for this action.
I'm afraid that I can't read this language.
Anyway, let me summarize. You can't resume a subscription once it's cancelled, and the updated billing_anchor won't afffect your subscription since there's no recurring payments after cancellation