Santos

[haughty olive]

Hello! No, not really. By definition setting billing_cycle_anchor to now is you specifically telling us that we need to create an Invoice right now. What behavior do you want?

[wary maple]

I would like the customer to be billed at a later date and not on the one when the subscription was first created.

So let's say the subscription is created on Feb 9, 2023. But we make a modification to reset the billing cycle anchor to now and it's March 3, 2023, I would like the next invoice to be for March 3, 2024.

[haughty olive]

In that case you should set billing_cycle_anchor to March 3, 2024, not now.

[wary maple]

Can we modify the billing cycle anchor on an existing sub?

The documentation states that we can only use two enums:

Either now or unchanged.

[haughty olive]

No, you can't. You would need to set it when creating the Subscription.

Can you tell me more about your use case and what's motivating you to make this change?

[wary maple]

We have a feature that subscription A gets created, coupon gets generated and customer A gets charged.

Customer B could then "redeem" this coupon and we create subscription B for them but they don't pay for it; however, this doesn't have to happen right away.

There could be a time difference of weeks or months between subscription A getting created and subscription B getting created.

The use case would be getting the billing cycle anchor of A to match with the billing cycle of B.

[haughty olive]

I recommend setting billing_cycle_anchor to now when the other Subscription's new period begins.

[wary maple]

And there's no way to prevent customer A getting invoiced when setting billing_cycle_anchor to now?

[haughty olive]

No.

[wary maple]

Thanks for confirming.