jbwyme_error

[weary oxide]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247959735203004450

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

[pale panther]

Hello! Do you have a request ID I can take a look at?

[unkempt tartan]

Yes, one second

req_zPwe8lfE8zlfbB - This is the request that fails when trying to set TIN

req_vqhOj9KNezvoIG - This request fails when trying to update capabilities

Ultimately, my goal is to onboard a US C-Corp where an owner does not have a US TIN yet.

[real root]

Taking a look into this now

[real root]

So it looks like this is definitely an issue on our side. We're looking into it internally now

[real root]

@unkempt tartan can you explain a bit about what you're trying to do with these Account update requests?

Do you always pair updates to the Person and Account simultaneously?

[unkempt tartan]

So we do the entire KYC/KYB data collection ourselves. Once a customer has filled out our form, we try to do the entire Stripe Connected Account registration which looks like:

1. Create connected account
2. Create all Persons
3. Mark all Persons as added + request appropriate features (treasury, issuing, etc) in one call.

      email: validRepresentative.workEmail,
      company: {
        owners_provided: true,
        directors_provided: true,
        executives_provided: true,
        phone: companyPhoneNumber,
      },
      capabilities: {
        card_issuing: {
          requested: true,
        },
        us_bank_account_ach_payments: {
          requested: true,
        },
        treasury: {
          requested: true,
        },
      },
    });

Now, this has worked great if all owners have a US tin but we've recently started accepting US C-Corps with owners who don't have US tin yet. When I tried to specify a non-US tin when creating a Person, it fails validation saying a US tin must be 9 digits.

So after talking to support, there is no way via the API to specify the country that a tin belongs to. They recommended doing it through the Stripe Dashboard. So I changed the create Person call to exclude the TIN if the TIN is non-US and I will just manually add it after the above flow is complete.

Ideally, I can just specify id_number_country on the create Person call and everything works as is.

[real root]

Okay, thanks for that. Will come back if I have additional questions/updates