#dawid-w_api
icy flickerBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1380175393713029266
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
crisp hollow
Hi, I do not see a way to set that.
Let me further look
I'm asking a teammate to confirm, hang tight
Can you confirm if you're using the Create CheckoutSessions API?
If you're using Checkout Sessions, https://docs.stripe.com/payments/checkout/receipts?payment-ui=stripe-hosted#localization, there is a hiercarchy:
If a Customer is set, their preferred locale are used if available.
If a Customer is set without any preferred locales, the language setting from the Stripe Dashboard is applied.
If no Customer is set, the language defaults to the browser locale of the user opening the Checkout Session URL.If no Customer is set, the language defaults to the browser locale of the user opening the Checkout Session URL.
According to the above, we'd look at the browser locale and determine the language.
Can you share the example from this customer where the language was in English please?
grizzled igloo
Let me check and get back to you
crisp hollow
We tested this on our end, and it looks like even if you pass the locale on the CheckoutSession, it does not change the invoice locale. We're raising this issue to our product team as a next step. You can write in to us to get updates on the status of the issue, I will send instructions on how to write in to us.
icy flickerBOT
Hello @grizzled igloo, we have sent you a direct message, please check it at https://discord.com/channels/@me/1380186899519377563
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
grizzled igloo
Ok, thank you for the update
crisp hollow
Sure
icy flickerBOT
grizzled igloo
It's a requirement for us to be able to do this, because we can't rely on the browser's locale.
crisp hollow
In understand, we have raised the issue to the product owning team as a next step. Your ticket with us will help get updates.
knotty hare
For an immediate fix, you should create customers in these cases and set the customer preferred locales
But as pgskc indicates, please use the link we sent to open a case for us to use to follow up
grizzled igloo
That's what we were discussing in the team, but it's pretty big change for us.
I will create the ticket, thanks
knotty hare
That's what we were discussing in the team, but it's pretty big change for us.
I am inferring you had a code path that determines for which customers the ca-fr locale is required in order ot pass that to Checkout Session API on create. I'm suggesting that for that subset of customers only that you should create customer objects with preferred locales as a backstop.