#jmontydesign-custom-verification

1 messages · Page 1 of 1 (latest)

gusty loom
#

Hi there! Taking a look, give me a sec!

#

So these verification updates are asynchronous and do take a second, even in testmode. You want to be listening for the account.updated webhook to verify when your Accounts are active.

#

For instance, I can see that the above account is fully verified, and was verified very shortly after you made that update.

#

Do you have a request ID for where you are seeing that error?

steep heath
#

I have webhooks implented for account.updated and I cannot get a "verified" status. Here is my latest attempt at updating an account event id: evt_1KW686QhQX0ElSYFJf3eaHCn

split root
#

catching up here one sec

steep heath
#

Am I looking in the wrong spot? I am looking at the account object under individual.verification.status?

#

or event.object.individual.verification.status

#

Here is the account id: acct_1KW67tQhQX0ElSYF

split root
#

checking one sec

#

so you entered the 1901-01-01 Date of birth

#

which should lead to successful verification

#

checking what's missing on the Person

#

ah

#

the ID number passed was not 0000

#

it was something else

#

so your code did not pass 0000 on Person creation (though I know you sent a snippet that had that)

#

try with the 0000 number again

steep heath
#

You mean the ssn last 4?

split root
#

yes

steep heath
#

Am I looking for the verification status in the right spot? individual.verification.status

#

Once the state is "unverifed", you can't ever get it to be "verified"?

split root
#

you can, sorry we're jumping past some things

#

my point is, your Person did NOT pass the "magic" 0000 SSN

#

in test mode

steep heath
#

I've been working on this for two days now. How can I get it to be verified?

split root
#

you didn't pass the magic 0000 value

steep heath
#

So if you dont' do that at account creation, you can't update it to a status of "verified"

split root
#

you can

#

here

#

your requirements hash has

          "individual.verification.document"
        ],```
#

you'll need to upload an ID document since the SSN check didn't verify

#

that would have made the account verified (assuming that ID document chekc worked)

steep heath
#

We will not be using any document verification in our flow. We need a flow that just uses the last 4 of the ssn. So if the user is "unverified" after the initial creation, We can't update the account, we have to create an new account?

split root
#

We will not be using any document verification in our flow
well what if a Connect account enters the wrong SSN by mistake?

#

you CAN update the account

#

that is what I'm repeating

#

the scenario you've run into is that your user entered the wrong SSN in which case the requirements hash already tells you what you need to collect

steep heath
#

How come I am passing in the "0000" for the last 4 of the SSN and my individual.verification.status is still "unverified"?

split root
#

because you are not passing 0000 atleast on the account you sent me (from what I can tell) - you passed some other 4 digits

steep heath
#

acct_1KW67tQhQX0ElSYF

#

evt_1KW6v6QhQX0ElSYFHO9kz05Q

split root
#

that is the account I looked up

#

everything I said was about that account

steep heath
#

In the "individual" section it says "unverified" , bottom of picture, this is from the update event.

split root
#

sorry @steep heath I think we're talking past each other

#

like I said earlier, I have seen that view

#

on my end

#

for that same account

#

I think you haven't understood what I've been telling you multiple times, I'm trying to figure out how to align on that

steep heath
#

I am updating the account with :

#

first_name: "John",
last_name: "Montgomery",
dateOfBirth: "1901-01-01",
ssn_last_4: "0000",

split root
#

yes I understood that part too, but on that account, your code did not pass 0000

steep heath
#

You can see the ssn_last_4 is "0000", but the account is still "unverified"

split root
#

actualy

#

no

#

ok we're talking past each other still, let's align

#

you are saying "your code" passes that

I'm saying your code did not

#

your code passed the first name: jm for that account

#

not John

#

and the SSN was NOT 0000

#

please try this

#

create a NEW Custom account

#

onboard it but make sure you pass the 0000 SSN

#

log it out in your code too

steep heath
#

ok