#ecila_vip
wicked lynx
I found the request made by the dashboard. req_w9evfZ4EYh2N04
Does initial_billing_cycle_anchor sound like a good idea?
sharp cedar
The request here is Stripe internal's API. initial_billing_cycle_anchor isn't available in public Subscription Schedule API
You can create a Subscription Schedule to start a future date: https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#start-subscription-future
In the phase 0, phases.billing_cycle_anchor can be set to the 1st of the next month
wicked lynx
In the phase 0, phases.billing_cycle_anchor can be set to the 1st of the next month
Cannot pass date to phases.billing_cycle_anchor
sharp cedar
What's the error you're facing? Can you share the request ID (req_xxx)? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
wicked lynx
Ok, wait a minute.
req_cq8Nhjdzn4UeLp
invalid_request_error - phases[0][billing_cycle_anchor]
Invalid phases[0][billing_cycle_anchor]: must be one of phase_start or automatic
wicked solsticeBOT
sharp cedar
Can you try creating two phases and end the first phase with phases.end_date to the 1st of the next month. In the second first, have phases.billing_cycle_anchor to be phase_start?
wicked lynx
That would make it feasible, but wouldn't there be a fee even for phase 0?
austere sequoia
👋 catching up
What do you mean a fee?
I think it's about setting up first phase as half a month and next phase and full month, and you can control it by the timestamp you set for phases
(Recommend playing with the API in test mode, with Test clock to test out your setup)
wicked lynx
Hi!
It's lunch time and I'll reply later.
wicked lynx
Returned.
That would make the billing run in the first phase.
The goal of what you want to do is the same as using initial_billing_cycle_anchor.
austere sequoia
initial_billing_cycle_anchor is not available via Public API, sorry
wicked lynx
Does this mean that the same behavior is not possible from the API?
austere sequoia
Can you describe again which behavior you are looking for? As my colleague stated, you can configure the Subscription Schedule phases at specific day in the future
wicked lynx
What we want to do:
I want to create a SubscriptionSchedule with a 9/16 start, ANCHOR is 10/1, and PRORATION is off.
Since proration is off, the first billing should be on 10/1, but internally the Subscription will start on 9/16.
The reason I want to do it that way is because that is how Subscription works.
For example, if we move the date in the previous example up one month:
Create a Subscription that starts 8/16 with an anchor of 9/1 and proration off. The first billing for this will be on 9/1, but internally the Subscription can start on 8/16 (today).
To align with this behavior, I want to accomplish the first "what we want to do".
I'm not mainly English, so I'll explain again if it's not clear.
austere sequoia
Sure, no worry. And we believe you can implement it by using Subscription Schedule. Can you continue to try my colleague advices above?
wicked lynx
Okay, whatever it is, I'll control it in Schedule and share the results.
Done
cus_OSXMqGhSMgWRZv
req_WyhNmQe5jom38u
As I said, the billing is occurring in the first phase. We do not want this.
austere sequoia
Okie, by do not want the billing is occurring, do you mean the shouldn't be any Subscription at all in the first place?
wicked lynx
Yes.
I would like the first day of the next month to be the first billing date for all timings. This fits with Subscription and proration_behavior = none.
wicked lynx
at phase 1?
or phase 0?
austere sequoia
It's outside of phases field. See the example code in the Doc!
wicked lynx
ah, ok
https://dashboard.stripe.com/test/logs/req_9tBTKGJSojqkQ8
invalid_request_error
Each phase must be at minimum 1 second long. Phase 0 has the same start_date and end_date of 1693526400.
To add, this test clock is at 7/16, and I am making a Schedule that starts on 8/16 and puts the ANCHOR on 9/1.
austere sequoia
- Set start date at Sep1
- Remove phase 1
- Remove phase 0's
end_date
wicked lynx
Wouldn't that make it a 9/1 start?
austere sequoia
Yes
wicked lynx
We would like to make the actual start on 8/16.
It is getting a little long. We have limited time to investigate.
If we can't do the equivalent of initial_billing_cycle_anchor, we give up.
austere sequoia
Sorry I don't follow your requirements, taking a step back and looking at https://dashboard.stripe.com/test/logs/req_w9evfZ4EYh2N04
To get the same behavior as this response to start at Sep 15, and first billing cycle to Oct 1, set a Subscription Schedule where
- start_date set to Step 15
- phase 0 end_date to Oct 1
- phase 1 without any end_date
wicked lynx
Again, that would result in a bill for the first 9/15 through 10/1. Therefore, it is not SAME behavior.
austere sequoia
On phase 0, can you also set trial to True?