#thefyrewire_api
weary wingBOT
👋 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/1263131462111068191
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
late locust
It is possible that Stripe was unable to resolve location for the IP address when validating the location..
Have you tried using a different IP address?
@stoic finch
stoic finch
Have you tried using a different IP address?
Hello! Yes, it seems to work for other IP addresses, it seems to be related to my account, but I'm not sure why
Can IP addresses just not resolve in some cases? It would be good to know how to handle this
late locust
Yeah it is possible that geolocation fails for some IP addresses
weary wingBOT
stoic finch
What is the best course of action in those cases, to still accurately determine the correct tax?
We'd like to avoid collecting addresses 😦
Or at least, full addresses
vivid girder
According to our docs, there are situations where you can collect just country and postal code, but that does restrict where you can properly calculate tax quite a bit:
We recommend against relying on a postal code alone in the following states: Arizona, Colorado, Oklahoma, Alabama, Missouri, Texas, Illinois, Washington, Kansas, New Mexico, Louisiana, Arkansas, California, Alaska, South Dakota, North Dakota, Utah, Nebraska, and West Virginia.
https://docs.stripe.com/tax/customer-locations#supported-formats
https://docs.stripe.com/tax/customer-locations#us-postal-codes