#tomas at amenitiz
supple kiln
gusty garden
Ah, like manually set the next_invoice_sequence at an account level?
Like you say, seems possible on customer level: https://stripe.com/docs/api/customers/update#update_customer-next_invoice_sequence
Maybe you can set this via the Dashboard actually: https://stripe.com/docs/invoicing/customize#invoice-numbering-schemes:~:text=Stripe automatically assigns,longer in use.
Hmm, screenshots aren't working. This is the Dashboard link: https://dashboard.stripe.com/settings/billing/invoice
gusty garden
Yeah, looks that way
main cliff
That still would allow me to change just the prefix, no? For the next_invoice_sequence I have. no way of doing it for account level, either via api or the dashboard?
gusty garden
No, you can explicitly set the next number in the sequence
For some reason I can't upload screenshots to show 🤦♂️
half cape
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!
main cliff
Hey! So basically from my screenshots; I don't see a way to change the next_invoice_sequence at the acount level.
half cape
it's basically https://dashboard.stripe.com/settings/billing/invoice
main cliff
While it's pretty clear from the docs how to do it on a customer level; that schema only applies to the US
main cliff
Hmm so I don't have that row
half cape
within it you have Next test invoice sequence
main cliff
Either that or I'm supper stupid
half cape
what's your account ID?
half cape
Oh I see that you are on a very old API version
main cliff
Ah yes, it could be that
So I can only have one version enabled at all times?
Would I have any major implications if I upgrade it? For instance backwards compatibility issues?
half cape
Would I have any major implications if I upgrade it? For instance backwards comp...
yes there are some major breaking changes
half cape
So I can only have one version enabled at all times?
if you want you can upgrade your API version to the latest which would make it the default for you, but then you can specify the version you want to use in your code to still take the old API version resulting in no compatibility issue with your code
main cliff
hmmm, that sounds like a good approach
so it will still leave my codebase compatible, but it will update my dashboard to match the latest API version?
half cape
half cape
so it will still leave my codebase compatible, but it will update my dashboard t...
for your codebase you need to look at this ^
you need to pass in specifically the API version in all of your projects so you wouldn't change the current behavior
I would advise you to start by doing that before upgrading to the latest API version on the dashboard
main cliff
yeah, that seems the smartest way to go about it
thanks, that seems all pretty clear
you can close the thread, I'll see into the implications of bumping the API version in the dashboard
one last question: if I created webhooks on an API Version
and then bump it
they'll stay on the api version created, or do I need to specify the version I need?
meaning, would upgrading my account api-version upgrade my webhooks api-version too? That would be really undesirable
half cape
to avoid that you can create a new webhook endpoint and choose which API version you want it to be at, and then delete the old one
half cape
you should also think about adding the versioning in the Stripe instance in your webhook endpoint too
if it's different than your app's
main cliff
I will, thanks
half cape
sure thing 🙂 let me know if you need any more help
main cliff
I don't think I need for a while, so feel free to close it
Thanks for the help and sorry for the inconvenience 😄
half cape
no worries at all, feel free to come back whenever you need anymore help.