chrisagross_error

[agile cedar]

👋 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/1327064135522979844

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[cold tulip]

Some additional context here.... We create a connected account in Test with the EIN of 111111112. We wait for the error to appear: verification_failed_tax_id_not_issued and then we attempt to update to EIN 000000000. We use VGS for all of the calls.

[nova star]

hello 👋 can you explain what you mean by "re-record API"? also can you share an example request ID where you received this error?

[cold tulip]

These are all test cassettes generated by the VCR Ruby gem. When upgrading the Stripe API version, we delete the cassettes so that they get regenerated.

Request ID: req_z1H1bIhbYp0IXF This is in Test mode.

We aren't doing any changes to a TIN, so the error is bizarre to us. This is the exact payload for the token generated for the account update:

      string: account%5Bcompany%5D%5Baddress%5D%5Bcity%5D=San%20Francisco&account%5Bcompany%5D%5Baddress%5D%5Bline1%5D=120%20Kearny%20st&account%5Bcompany%5D%5Baddress%5D%5Bline2%5D=6th%20floor&account%5Bcompany%5D%5Baddress%5D%5Bpostal_code%5D=94017&account%5Bcompany%5D%5Baddress%5D%5Bstate%5D=CA&account%5Bcompany%5D%5Bname%5D=Goyette%20and%20Sons&account%5Bcompany%5D%5Bphone%5D=%28319%29%20406-7205&account%5Bcompany%5D%5Btax_id%5D=000000000

This doesn't happen in production, so we believe there is a configuration problem on our Test environment

I should have just given the request ID for the token generated that is passed in the update req_puDz3LkiVkHsea

[harsh plover]

Hi 👋

The error is a bit confusing because you're not passing in a tax ID but the tax ID provided is invalid, as you mentioned above, so that is causing an error

Furthermore, in the request that is throwing the error https://dashboard.stripe.com/test/logs/req_z1H1bIhbYp0IXF, you are providing the settings.card_issuing.tos_acceptance parameter

But you already provided this information when you created Connected Account acct_1QfVQLQqEEciSUV5 in this request: https://dashboard.stripe.com/test/logs/req_glcVpmPKD1TGdp

[cold tulip]

We are not passing an invalid tax ID. All 0's is a successful Tax ID according to your documentation https://docs.stripe.com/connect/testing#test-business-tax-ids

[harsh plover]

What was this in reference to?

We create a connected account in Test with the EIN of 111111112. We wait for the error to appear: verification_failed_tax_id_not_issued and then we attempt to update to EIN 000000000

[cold tulip]

That was just me explaining what we were doing

[cold tulip]

We did try doing this. It had the same TIN error. Let me find an example request.

[harsh plover]

There is a currently existing error for this account:
code: verification_failed_tax_id_not_issued

message: Employer Identification Number (EIN) hasn't been issued by the IRS. Provide an issued Employer Identification Number or contact the IRS.

[cold tulip]

Yes, that's expected. The test we're running is that the user can update the EIN to fix it.

Token request without TOS acceptance: req_rY5KDQ2YuzyAib
Failed update request using the created token: req_b1NmaKXzQJr18t

I might have pinpointed something. I was able to get the update to succeed by not passing the tos_acceptance during the create and only passing it in the update. This is a problem, because not every account will need an update.

[harsh plover]

Hmmm... can you share the successful request? I want to compare internal logs of each

[cold tulip]

Request ID for generating the token for create: req_LZfaqScLYNP8qv
Request ID for creating the account: req_G85DmHj8c6Wpnb
Request ID for generating the token for update: req_ZNBbhfLLKmXQhb
Request ID for updating the account: req_iHMFgXGvZcTmdM

[cold tulip]

This was the request ID for the create on this one which was still passing in the tos acceptance data req_RFYVs9aAU5Cgxh

[harsh plover]

interesting. I am seeing the same internal error pertaining to incorrect EIN numbers but it's not blocking this request

possible 🔴 🐟

[cold tulip]

Yes, the incorrect EIN is expected after the create and then not expected after the update. I can look at the last account example where the update succeeded and see that it no longer has that EIN error. We're using the Testing mode EINs to trigger specific scenarios.

[cold tulip]

So, this may be impacting us in production as well. I found a request ID: req_bqvRkLRul0ADKy