#some1ataplace_api

1 messages ¡ Page 1 of 1 (latest)

compact sableBOT
#

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

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

brisk roost
#

hi, are you referring to identity verification for connected accounts?

cyan sage
#

No, but that also sounds interesting to me. I have not heard about that. I am concerned about the new UK Online Safety Act and how to identify underage users.

brisk roost
#

ah, so identity verification for your customers. yes, you should be able to test that without uploading real IDs. if you're using it in test mode there should be a dropdown selector which lets you test various scenarios like verification failure, consent declined, etc

cyan sage
#

I was hoping in test mode or sandbox mode I wouldn't have to upload anything about myself.

brisk roost
#

ah, yes, you'll need to verify your own identity in your dashboard before the feature becomes available

cyan sage
#

That is crazy, I am not willing to do that until I actually start my business. Tell me what the identify connect users is about.

brisk roost
#

Connect is a feature for if your business is a platform for other businesses, such as a marketplace. identity verification is used in that context to onboard other businesses to use your platform

cyan sage
#

So instead of verifying a user's age you are verifying another business or a connect account user?

brisk roost
#

yes

cyan sage
#

Geez is that a requirement?

brisk roost
cyan sage
#

Unreal. So I have to lookup the IP of each user then determine via the API whether they need to be ID verified or not?

#

Is Stripe Connect ID Verification available to test or do I still need to upload my own personal government ID to test Connect Verification?

brisk roost
#

if I recall correctly you don't need to do ID verification to get started with Connect. at least if you're doing it in test mode

cyan sage
#

It has been a while since I last looked at Connect. But is there a way in the API to say or require the user to provide identity? They fill out a date of birth field for example and the API handles the verification process? Any word on me needing to lookup the IP to determine the country?

brisk roost
#

I'm not aware of needing to verify the IP address yourself, are you seeing that in a doc someplace?

cyan sage
#

No, I just assumed that in order to determine a user's country you need to determine their IP address or location.

brisk roost
#

when you say user, are you referring to customers or the connected account business?

cyan sage
#

Connect account. I originally wanted my Connect users to be just about anybody, people or businesses.

#

But now with these new laws it seems like it changes things...

compact sableBOT
brisk roost
#

the platform isn't responsible for collecting verification for connected accounts, our onboarding UI has the user indicate which country they're from

cyan sage
#

Okay so you guys do it automatically? They fill out the country and you automatically ask them for ID? Do I need to configure anything on the API side?

modern sun
#

Hi there. I'll be taking over for denton, who needed to step away

#

You're referring to connected account onboarding, correct?

cyan sage
#

Yes for now

modern sun
#

If so, then if you're using Stripe-hosted onboarding, then, yes, Stripe decides what requirements are required and collects them.

I'd really recommend giving this guide a read:

https://docs.stripe.com/connect/onboarding

#

After reading the thread, however, I'd like to clarify that Connect is for people you are paying money out to. For example, a platform like Doordash accepts a payment which is split between the delivery driver and the restaurant

cyan sage
#

Thanks I will look afterwards. Yes, I have setup the Connect API already but I thought it recently changed due to the new UK Online Safety Act which required me to do some sort of age verification for Connect.

#

Out of curiosity, for non-connect Identity API what if my verification fails for some reason? Will I not be permitted to use that API or do I have another chance to upload an ID document? I assume my Stripe account details must match the ID details?

modern sun
#

Stripe Identity (separate from Connect verification) verifies documents; it gives you results about what Stripe thinks the validity of the documents are. What you do with that information in the context of your application is up to you.

cyan sage
#

Like what happens if my verification fails? Do I get another chance? Must my ID match my stripe account settings?

modern sun
#

I'm not familiar with the process of signing up for Stripe identity in the dashboard. If you have questions about that, you can reach out to my colleagues in Support.

https://support.stripe.com/