#konrad_docs
slate kestrelBOT
👋 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/1231954811453309019
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
nocturne capeBOT
outer ravine
My country has their own tax id registry and their own API (https://api.stat.gov.pl/Home/RegonApi)
And I don't want to force my customers to register in VIES as well
dense pumice
Hi there 👋 trying to wrap my head around this. What is VIES?
outer ravine
it's like a VAT number registry for all european countries
e.g. PL1234567890
but not all businesses are registered in it but they're registered with local registries instead
so stripe will validate it using VIES api and say its incorrect but it's correct in my country
its fine but question is if billing /charging will continue to work
I have my own tax id validation in my frontend
dense pumice
My suspicion is yes, but it may depend on how exactly you're using these Tax IDs.
When you use our special testmode Tax IDs that either fail verification or remain verifying indefinitely:
https://docs.stripe.com/billing/customer/tax-ids#customer-tax-id-verfication
does it prevent your flows from being able to proceed?
outer ravine
no i just fill them in customer objects
stripe will say they're incorrect
but using my country's official gov api they are correct
i just hope that even if its incorrect checkout will still work fine
I will actually test
if 111111111 will still work
dense pumice
Yup, that's my suggestion. I'm pretty sure they will, but there are a lot of different ways to accept payments through Stripe so testing the flow you've built using those test values is likely the fastest way to check.
outer ravine
I just create checkout session with pre-filled customer id with invalid tax I will check it in a moment
const session = await stripe.checkout.sessions.create({
mode: 'subscription',
yeah it worked, payment successfully completed even if tax id validation failed
so if it works in test mode it will behave the same in production as well right?
dense pumice
Yup, I would expect so.
outer ravine
aight thank you