#Centro-invalid-tax-id

1 messages · Page 1 of 1 (latest)

keen prawn
#

Hi there, hmm I'm not familiar with this new formatting enforcement. Let me do some digging

#

Are you talking about the eu_oss_vat type that was recently added?

rare spoke
#

hi, i don't believe that it's the eu_oss_vat. we received the below email from stripe about a change to german tax id verification on the /v1/accounts endpoint, which will go into effect on July 11.


We’re writing to let you know about a change we’re making to the Stripe API that will enforce correct formatting for German company tax IDs (Handelsregisternummer) created via the /v1/accounts creation and update endpoints.

Until now, we haven’t been validating German company tax IDs. Without a correctly formatted company tax ID, we’re not able to programmatically verify the ID or the business and instead need to conduct a manual review, leading to longer verification wait times. By validating the company tax ID during account creation and updates, we aim to reduce the time you need to wait for a tax ID to be verified.

From July 11, 2022, you will receive an error with status code 400 and error code ‘invalid_tax_id’ if you attempt to create (or update) a German connected account with an invalid company tax ID.```
keen prawn
#

Ah okay that is helpful

#

So that piece at the bottom discusses the error a bit.

#

Can you clarify what info you are looking for exactly?

rare spoke
#

sure - we have the following questions:

  1. will the error raised be an InvalidRequestError?
  2. what will the message on the error be?
  3. will this error be raised on Stripe::Account.create and Stripe::Account.update? are there any other stripe endpoints where we'll need to check for it?
keen prawn
#

Thanks, let me check on those.

rare spoke
#

thank you!

keen prawn
#

Okay!

  1. Yes invalid_request_error
  2. 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."
  3. Yes both create and update. Don't think it would be thrown on any other endpoint.
rare spoke
#

thanks so much! i have one other question - do you know if there is any way for us to trigger this error in test mode before stripe releases it on July 11th?

keen prawn
#

I believe you can trigger this in test mode already actually.