#mo223-german-tax-id
1 messages ยท Page 1 of 1 (latest)
Hi ๐ I was helping bismark look into this yesterday, when I tested this I used the value TEST123, but I wouldn't expect this to be value dependent.
I was able to trigger the error without making any changes to my account.
hi ๐ hmm ok thanks. i'll try TEST123 just in case. do you think there is anything about req_QZ4AacTv6du2jr which would make the error not return? country value is 'DE' and tax_id value is '1111', which i thought would have been enough to trigger it.
Let me pull up my request from yesterday and compare them.
ok thanks!
btw - i just tried with TEST123 and still didn't get the error. req_NNGUPC8QJpVrHs
It looks like we're using the same fields, so I don't think this is dependent on the data that is being passed in but by a system configuration of some sort.
do you mean like something on our platform account that we need to configure differently?
No, I don't think so, I suspect it has to do with how the change is being rolled out, but that's outside of my area of expertise so I'm not certain on that.
ah ok... do you have any suggestions for other ways that we could validate our integration before the rollout on July 11? is there a similar error we could trigger during account create/update?
The only thing that comes to mind is to fake the response from the requests, i.e. make a request to a function that you write, and have that function respond with the error. This is the content of the response that I received that you can use:
error: {
code: "tax_id_invalid",
doc_url: "https://stripe.com/docs/error-codes/tax-id-invalid",
message: "The provided Handelsregisternummer `TEST123` does not appear to be valid. Handelsregisternummer start with a capitalized 2 to 3 character register type, followed by a 2 to 10 digit individual number with an optional 1 to 2 character suffix. For example: HRB 1234, HRA 58343 FL, or PR 345.",
param: "company[tax_id]",
type: "invalid_request_error"
}
}```