#pedro_subschedules-metered-future
1 messages ยท Page 1 of 1 (latest)
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.
- pedro_schedule-settings, 1 day ago, 6 messages
- pedro-lara_api, 3 days ago, 9 messages
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1261366159219884112
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
on event details it says it bills on jan 1
on upcoming invoice it says it will be billed on dec 1
Hi, we don't support Dashboard functionality in this chat. I would recommend reaching out to support instead: https://support.stripe.com/contact
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
in short, what i need is to the the bill monthly starting to bet set at api level
Which field in the create subscription schedule object is equivalent to the "bill monthly starting" timestamp field at the dashboard?
That's the billing cycle anchor
i want to set a specific day
which param in the subscriptionSchedule.create api is the equivalent in timestamp format to this field in the dashboard?
Hi ๐
I'm stepping in as my colleague needs to go
You said you are using the Subscription Schedule, right?
And your goal is to start a subscription in the future? Or set the billing cycle anchor to the first of the month?
both
duration is defined by start_date
"bill month starting" is defined by which field in the subscriptionSchedule.create api
Sorry can you be more clear? When you say "both" do you mean you want a Customer to be able to sign up now for a Subscription that will start in the future, as in the first of the next month?
I want the duration to start on dec 1 and the first billing to be on jan 1
those fields are manageable through the ui on "Duration" and "Bill monthly starting"
i want to set them using the subscriptionSchedule.create api
but it's quite confusing since
it says "bills on jan 1"
an then it says "will be billed on dec 1"
in short, the sub will start on dec 1, the first bill will be on jan 1
next month, basically
from the next year in this case
The duration is a period of time, not a specific date, so I find your wording confusing here. I think there is also confusion with the way our recurring prices work as well.
Most of our recurring price models bill users up front.
It sounds like you are looking for a model that bills in arrears or at the end of the cycle
this is how it is
this is how i want it to be
just tell me which field does this
in the api
Sorry those pictures don't help me much. Have you created any test subscriptions that behave how you want? If so, can you share the IDs?
no i haven't
not through the api
sub_sched_1PbSuVAYpd6nUFB4dQYO0Ugi
but manually
i don't get it, there's a field that can be manually changed in the ui, i want to change that with the api
It's not like there is a 1 to 1 mapping between options the Dashboard and the API. In some cases there are number of custom methods built into the Dashboard to make it behave the way it does. That is why I'm trying to review your actual subscription schedule and ignoring your screenshots
seems like there's a field called initial_billing_cycle_anchor in the body of the update requests of that sub in the logs session
can it be set through the api?
I still think you are a ways away from achieving what you want.
I'm looking at the price associated with the schedule you shared
Okay well the good news is this is a metered price
and that does bill at the end of the cycle
yeah, so the usage will be calculated from the starting point up until the billing date
the starting point is set, i need to set the billing date
the starting point will be 3 months from now, the billing date needs to be 4 months from now
The billing date is determined by the combination of the Subscription start date and the billing interval.
In your case the interval is "month" so the billing date occurs at the end of a monthly cycle
right, but
i have set the start date to be dec 1
the billing date on the ui is also dec 1
except when it says it is jan 1
quite confusing
starts: dec 1
next invoice: dec 1
bills on: jan 1
will be billed: dec 1
This the dashboard. This isn't something we know a whole lot about here. I recommend you actually create all of this in Test mode and use our Test Clocks to simulate time advancing. This will let you test out this behavior.
https://docs.stripe.com/billing/testing/test-clocks
In this case I think the part about billing on Dec 1 is wrong but I recommend you test it yourself.
Is there anyone i can talk to about this issue?
You are
Cause coming up to my boss and telling him to just ignore what the ui says and trust my test isn't gonna work
So i need to know exactly what all those dates in the ui mean
And my advice to you is to build your entire subscription flow in Test mode and run through it end to end, checking when each event occurs exactly.
Ok. Is there anyone i can talk to about this issue in the ui? Like, what each date is supposed to mean, cause even if it works the way i intend for this specific case, it still confuses me if i need to change something in the future
For that you would need to reach out to Support. They have much more expertise on the Dashboard UI components. And it's a good way to raise feedback about changes you would like to make it less confusing.
Ok thank you, sorry to be a bother but my boss won't accept something that 'works on tests i made'
Last time i talked to support they literally lied about being able to support the billing portal on iframes :/ so not the best experience, but thanks
Yeah, I can understand that. And I'm sorry you go incorrect information about the billing portal!
Thank you, bye
I hope it helps ๐