#appien-identity-person
gaunt dirge
@dawn geyser hello! I'm not entirely sure waht you're asking "real test document" exactly and what "Person object" has to do with it. Can you provide more context, especially some code and the exact doc you are following?
dawn geyser
Im starting a verification session using the Java API. With that I start a verifaction for the Person object of that account. I click on the link provided by Stripe.. and select: "use test data". But the persons keeps unverified
and hello! @gaunt dirge 🙂
gaunt dirge
With that I start a verifaction for the Person object of that account.
What does that mean? Can you explain your exact code and the exact doc you are following so that I can help you?
dawn geyser
Like this
gaunt dirge
appien-identity-person
dawn geyser
VerificationSessionCreateParams params = VerificationSessionCreateParams.builder()
.setType(VerificationSessionCreateParams.Type.DOCUMENT)
.putMetadata("user_id", person.getId())
.setReturnUrl(returnUrl)
.build();
VerificationSession verificationSession = VerificationSession.create(params);
gaunt dirge
okay so here, this is purely a "metadata". There's no link between the VerificationSession and the real Person object in the API right?
dawn geyser
except for the person.getid(), no
gaunt dirge
Yeah so our API has no way to know any of this. There's no "link" so your Person object will never be updated. You aren't supposed to use the Identity API at all for this.
You likely want to read https://stripe.com/docs/connect/identity-verification-api instead
dawn geyser
so what am i excatly creating when i create a verificationsessions object?
gaunt dirge
The better question is why are you creating one? It's a completely separate product and irrelevant to identity verification for Connect accounts
dawn geyser
thats indeed a better question 🙂
I thought this is the way to do person verification
gaunt dirge
yeah that is not. I mean it is but as a standalone product to verify someone's identity for example ahead of a payment and such.
you need to carefully read the doc I shared above
I assume you're using Custom accounts?
dawn geyser
thats right
im not using it as a sepearte product. i already have a custom account... where a Person object is added. This person requires document verification
gaunt dirge
Sure but you are just misunderstanding things. The Identity product is a standalone separate product and it's not what you need here
My advice: Don't do this yourself and use our Connect Onboarding UI flow: https://stripe.com/docs/connect/custom/hosted-onboarding
dawn geyser
the thing is... i already use this flow.. however when i start it.... there is no windows which says i need to upload a id document
so for my customer that would be very unclear
gaunt dirge
That means id document is not required at this time and might be later. We're back to reading carefully the doc I shared earlier end to end. But really you have no reason to use VerificationSession and you can drop this entirely
dawn geyser
Okay, tnx. I will get back to the drawing board
just to be sure...
when i start the hosted onboarding.. and finish it
there is no sign i would require a ddocument upload
gaunt dirge
because it's not required upfront. Document collection is often optional as DoB and SSN are enough
dawn geyser
i understand... but when it is required.. It is somehow not clearly visible in the UI of stripe?
gaunt dirge
I'm sorry I am struggling to follow what you mean here. If a document is required then we clearly ask for it during onboarding
dawn geyser
mm thats odd
okay, i will get my originally situation restored
and try to reproduce it
and will probably get back to you 😄
tnx so far koopajah!
gaunt dirge
sure!
dawn geyser
this is a person i just created called: "sfds sdfs".. It doesnt require document verifdication now.. but it does later!
Also on the second screen, no indication it is required
gaunt dirge
I'm really sorry those are just pictures and saying it doesn't work. There's no information for me to look at or help yet. You say "but it does later" without more info. And you put all fake data
Can you try and make a clear summary of your issue, share exact object ids (acct_123, person_123), explain what you see in the requirements array before you send them to hosted onboarding and then what's not working?
dawn geyser
im sorry for the confusion
its account id: acct_1OC5xiQhWrG6OqGM
person: person_1OC5yQQhWrG6OqGMvxRzwnrJ
steep valeBOT
craggy lotus
👋 stepping in as koopajah needs to step away
dawn geyser
the account link i got is: https://connect.stripe.com/setup/c/acct_1OC5xiQhWrG6OqGM/XfcJprvok3RM
ah cool
craggy lotus
It still may not require the ID document immediately just fyi
But you do want to use that param to request everything required
dawn geyser
i will check this now
craggy lotus
The person verification is first attempted based on the input info, then documents are requested if necessary.