#fwdawid_code
1 messages ยท Page 1 of 1 (latest)
๐ 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/1440708092953362553
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- fwdawid_error, 3 hours ago, 14 messages
Just changing language in browser changes select input values
We got reports from CN/TW/JP countries for now.
We basically do not allow non latin characters in our checkout, and above results with addresses that have invalid value without option for our customers to edit those.
Hi there ๐ can you tell me a bit more about where in your flow problems occur, so I can think through how much flexibility there is at that point?
Is it client-side code that you have that is struggliing to handle the non-latin characters, or is it more in the backend/order fulfillment side of things?
it's more backend/order fulfillment side (at least reason why we block it on FE lies there)
95% of our providers do not support non latin characters
Gotcha, I don't think it can be blocked there, at least not directly.
The only thing coming to mind is to use allowedCountries when creating the Address Element to provide a list of countries where you can support the characters they use for addresses.
https://docs.stripe.com/js/elements_object/create_address_element#address_element_create-options-allowedCountries
We still ship if its correctly filled (sometimes it went through if someone used Apple/Google expresses etc), so changing allowedCountries is some sort of revenue loss for us.
We will now disable Stripe AE for these countries.
Also can we request feature for that? Is there official way of doing it? We can also give some additional feedback.
Totally understand, it's why I was hesitant to suggest that solution, but it was the only thing coming to mind.
I'll make sure to file your feedback for this with the appropriate team!
Btw. we would love to have global feature that forces latin chars only ๐
Currently we are forced to show error bellow rendered Stripe AE like this: