#Gkiokan-hi

1 messages · Page 1 of 1 (latest)

paper iron
#

Hi there! What is your question?

#

@boreal timber please write your question in this thread.

boreal timber
#

Oh sorry mate. I just wrote the question on a new message. My bad.

paper iron
#

No worries, I adding it to the thread here:

Yesterday I got a strange bug that resolved in a customer_tax_location_invalid. Apperently I was using all kind of addresses and they worked. I reworked my code to create first the Customer on registration process with Stripe and use a 0 euro subscription on registration.

Since then It throw me the customer_tax_location_invalid and couldn't locate the tax country automatically.

Even real addresses where rejected. Now I have changed my create stripe customer parameter with country => 'DE' to enforce that.

Is this a bug or what is fully here? As I said, I used any kind of addresses before and they worked. This confuses me why it is not working partially now.

#

can you share the request ID where you see that error?

boreal timber
#

lemme check

#

req_LKlOps0Wi5MpQ3

#

take this as example

#

this was the last one i guess

#

req_Iw0FUDxcNUIGDE

This one is working but this has the country => 'DE' as appended hardcoded parameter.

#

Do you need my account id or something so you can see all other logs, too?

paper iron
#

Thanks! Give me a few minutes to look into this.

boreal timber
#

For the error this is the request for the user that has been created req_u7Ao5yz5hA9iAZ

The customer creation doesn't return the tax location error. The subscription does it.

#

Sure take your time. It drove me nuts all the night yesterday

paper iron
boreal timber
#

lemme check

boreal timber
#

On customer creation I have this one "tax_exempt": "none",

#

Is there a way to check the location verification on it's own?

paper iron
#

But this worked for the last months. Only now after I change the code flow to create the customer on registration instead of the subscription time this happend.
Could you share an ID where this worked?
Is there a way to check the location verification on it's own?
I recommend using what I mentioned earlier: tax.automatic_tax on the customer. Note that you won't see this field by default, you need to expand it https://stripe.com/docs/expand

boreal timber
#

Unfortunatelly I deleted all test data to see how it would work out on a clean fresh production env

#

Sure. Lemme modify the code I will check and reply to you afterwards

boreal timber
#

Interesting

#

can you check this out

#

I just dleeted all customers again and migrated a fresh db

#

Customer create with hardcoded country worked.

But If I update only the street parameter it then again throws out the country value and says "tax country not set"

#

cus_Ln2OoeYD9rqpMb

#

But the Address is legit itself

vague lodge
#

again throws out the country value and says "tax country not set"
where does that happen/where do you see that exactly?

boreal timber
#

On the Stripe Dashboard on the customer itself

#

this part here

Status des Steuerstandorts
Nicht erkannter Standort

#

Lemme set the country code for the customer on update hardcoded I guess it should automatically find it

vague lodge
#

please don't

#

just stop and let me look at the customer in its current state

boreal timber
#

The thign is. This was never an issue before. Seems to be something with my config after I deleted the test data

#

ok

#

i wait

#

This is the customer ID cus_Ln2OoeYD9rqpMb

vague lodge
#

I know yep

#

so I mean this seems normal to me, the address you provided is missing the country component so that's not a complete address.

You say that it used to work, which maybe is possible(it's entirely possible we have started being more strict about this), hard to say without a previous example. Either way the path forward is clear, just collect the country in whatever method you have to get the customer's address.

boreal timber
#

On the documentation for the tax location it says it is strict for the US but for example the EU it is enough if you provide street and city or postalcode

vague lodge
#

can you link me to that documentation?

boreal timber
#

Yea the only workaround I could do now is to set the country code hardcoded for now as we will only deploy in germany

#

Sure

boreal timber
#

Below the tap "Everywhre else"

#

ouh, all of them to have country code. But this doesn't explain why the location recognition worked before

vague lodge
#

interesting; like I said it's possible we changed this and haven't updated the docs yet

boreal timber
#

I see

#

Do I have somewhere in Stripe a global config to set a default country?

#

So I could omit the country part

vague lodge
#

I'd just do what you said above

#

hardcode it if you need to, it doesn't seem very hard

boreal timber
#

Yea it seems to work with it for now. I will investigate in the location issue once we deploy out of EU

#

For now this must be enough