#jarehec - Connect Verification

1 messages · Page 1 of 1 (latest)

digital pulsar
#

Do you have an account ID for the test account?

azure agate
#

Is this the id you need? acct_1KbCQD2c6q9oA1YE

digital pulsar
#

Yeah it looks like you need to provide individual.verification.proof_of_liveness

azure agate
#

What api can I use to send that data?

digital pulsar
#

That I am looking into

#

Okay this is a new additional requirement that necessitates the use of Connect Onboarding.

azure agate
#

I see, we'll have to integrate with Connect Onboarding. Thanks

digital pulsar
#

You're welcome 🙂
And I would try out that tool, it's kinda neat

digital pulsar
#

@azure agate I have unarchived this thread

#

Please ask your questions in here so we keep the context together

azure agate
#

Ok

#

Why can we only use connect onboarding for the verification?

digital pulsar
#

You can use the API

azure agate
#

That helps a lot, thanks

digital pulsar
azure agate
#

Is there an example of how to use it in test mode to verify an onboard?

digital pulsar
#

I don't have a simple example ready to hand. I would use the code snippets in the doc above to create a basic flow and see how it works.

azure agate
#

Ok, will do

rustic cipher
#

Hello! What's up?

azure agate
#

Hey, we just wanted to know how/if stripe supported Singapore before the identity apis

rustic cipher