#shooter_connect-verification-requirements

1 messages · Page 1 of 1 (latest)

coral yarrowBOT
#

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

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

dawn panther
#

Hello, do you have the Id of an account that this happened for within the last 30 days? (acct_1234)

plush phoenix
#

Okay let me grab one, before I provide the account id let me mention, if I put the 9 digit SSN from the stripe dashboard, then it is submitted and account is approved, but if 4 digits are send via API then 4 digits are saved in the connected account, but after a while is fails the activation.

#

account id for which I just tried is >> acct_1QRgd8GgjEyb3s8I

#

do I need to show you full code? right now the development is using sandbox, so I can share the code example if needed, I am stuck on this point for last 2 days, not good for me reputation in front of my client.

dawn panther
#

That ID should be good for now, looking in to this. Will let you know what I can find

#

Are you still seeing the SSN as not provided in some way for that account?

plush phoenix
#

I just created a new account for checking the log, the account id is >> acct_1QSPysGbF0Fer1N9

#

Wee are sending the SSN last 4 degits in post request,

image.png
#

account is also showing that the SSN is in review state:

image.png
#

That mean out SSN is reaching in it's right target, am I correct?

#

Now after some time it is show that SSN is not provided >>

image.png
dawn panther
#

Interesting. Not sure what the difference may have been, looking in to this account

plush phoenix
#

Yes, please I have checked the Documentations and AI help as well, but still stuck on this particular point, waiting for your reply,

dawn panther
#

Can you send me the ID of the request from that first screenshot? (req_123)

plush phoenix
#

here it is >> req_trLSZ9FvDn8OkH

dawn panther
#

To clarify, is the account in the screenshot acct_1QRgd8GgjEyb3s8I or acct_1QSPysGbF0Fer1N9, and do you still see that SSN is missing in the dashboard? This may be the UI acting strangely or being slightly out of sync

plush phoenix
#

her is the full screenshot >>

image.png
dawn panther
plush phoenix
#

I already tried passing full 9 digit SSN but it gives the error >> Error: Invalid SSN last 4. SSN last 4 must be exactly four digits

dawn panther
#

To be clear, basing that off of the requirements hash in the latest account.updated event on that account. I see that DOB is also showing up as an issue, if you are not already, you can provide 1901-01-01 for DOB and we should accept that in test mode,

        alternatives: [],
        currently_due: [
          "dob.day",
          "dob.month",
          "dob.year",
          "id_number"
        ],
        errors: [
          {
            code: "invalid_dob_age_over_maximum",
            reason: "Date of birth must be within the past 120 years.",
            requirement: "dob.day"
          },
          {
            code: "invalid_dob_age_over_maximum",
            reason: "Date of birth must be within the past 120 years.",
            requirement: "dob.month"
          },
          {
            code: "invalid_dob_age_over_maximum",
            reason: "Date of birth must be within the past 120 years.",
            requirement: "dob.year"
          }
        ],
        eventually_due: [
          "dob.day",
          "dob.month",
          "dob.year",
          "id_number",
          "verification.document"
        ],```
https://dashboard.stripe.com/test/events/evt_1QSQ4iGbF0Fer1N97VVpwzXN
#

This is a separate field than ssn_last4, which is where you have been setting it in the calls that I have seen so far

plush phoenix
#

I think we are mixing up account in communication, shall i delete all the account and should check this issue on one remaining? what you think?

dawn panther
#

For either of them, I think this issue should go away if you make an update that sets individual.id_number and individual.dob.*

#

So no need to delete or create a new account, I think we can confirm this with the existing ones

plush phoenix
#

Okay, I am not from USA but my client is from USA, I don't know if there is any difference in the SSN and id_number. Do you think these are 2 different things?

dawn panther
#

They are the same number in this case. I am not sure why they are separate fields here. It is possible that id_number can set last 4 but not the other way around. I can test that on my side

#

Yep, providing the full SSN to individual.id_number satisfies the last 4 requirement

#

So if you try that on the existing accounts or a new one that should satisfy the requirement

plush phoenix
#

okay trying now, actually this is something that client is not allowing us to collect so we just need to get last 4 digit from user. But as per solution that you are telling now, we can collect the SSN in the form and then can send straight to stripe without saving it in out database, I will discuss this with client in morning, but let me check if this work from my side,

plush phoenix
#

Great, this worked,

#

amazing support,

#

thank you, sir, I have a couple of questions (not issues) relating to the connected accounts but I will ask tomorrow, right now I am already too late, this is end of my day.

#

🙂