#neatfastro-connect
1 messages ยท Page 1 of 1 (latest)
instead of the whole onboarding we just want to delegate the verification part to be handled by stripe
I thought I read something about this but now can't find it
you would use Custom accounts https://stripe.com/docs/connect/custom-accounts
you can control the entire PII collection and just leave verification to us
I obviously stronglyrecommend not doing that, it's weeks and weeks of work to build this yourself end to end. I've helped hundreds of devs at this point work through many of the kinks
but up to you, we do support it
We are only targeting a single country (Netherlands) so it's not that complicated
do you have a list of pitfalls that I should look out for?
btw I have already integrated the stripe connect custom the only thing that's remaining is to improve the verification ux
Even with one country, it's weeks of work. Also it's permanent work, rules and regulations change over the years and you need to constantly upgrade your integration to collect the new information
honestly, trust me, though I'm just a stranger on the internet, I've worked at Stripe for years and seen hundreds of devs try this and move to our hosted flows ๐
But overall https://stripe.com/docs/connect/required-verification-information covers all that's needed per country
and it's all available in our API so you can start testing and decide for yourself!
I think I can trust you seeing your "admin" badge/role
yeah but I mean I work for Stripe so I'm biased with our product ๐
I think you two might be talking past each other... I think @timber badge wants to use Custom Accounts, but wants Stripe to "do" the onboarding... which is what @pearl sundial is saying
possibly but the sentence
Instead of the whole onboarding we just want to delegate the verification part to be handled by stripe
reads differently to me. I read it as "instead of delegating onboarding to stripe, we want to do it all ourselves and Stripe verifies the information only"
@timber badge ? Are you asking to collect the information yourself, and have Stripe verify the collected information - or are you asking if Stripe can collect and verify the information?
(aren't languages fun?)
I'm asking we can let stripe take care of the onboarding of accounts but we don't want to do that because we want to provide custom experience, but when it comes to the verification part of the onboarding we do want Stripe to do it for us, I remember reading something about that, that stripe also has a hosted verification where we can redirect our users to verify themselves
or I may be trippin
hum I am confused you said both "we want Stripe to take care of it" and "we want to do t ourselves" ๐
If you want us to do it for you, that's my recommendation: https://stripe.com/docs/connect/connect-onboarding
If you want to own the entire UI/collection flow on your own website, then you build your own UI/code and you use our API to pass all information (and we still do the verification of the info for you)
ah I see where the confusion is coming from...
(Noting for completeness - Stripe legally has to verify the submitted info, for their protection.)
by verification I mean the process of uploading images of docs etc
Whose UI would be used to do such uploads? If it's Stripe's, wouldn't that sort of defeat the purpose of a "customized UI"?
I mean we have thought about a product that's like Elements but for Connect
but okay sorry I'm still unclear what you need
lol it would but I thought there was something already in existence like it
Do we Stripe control the UI or do you on yourwebsite?
We want to control the onboarding ourselves but not the not part where users upload the docs etc
is this clear?
not really
I think @sand stirrup got my question?
๐
Either you want us (Stripe) to collect the details, so it has to be on a Stripe owned website/URL with a full page redirect
or you control it
noting for clarity: I'm not with Stripe; I'm just a lurker - so there's no "back-channel" communication here... ๐
...and @pearl sundial 's last answer really make the extra Dev effort point clear: if you don't use at least part of Stripe's UI, you take on a swirling world of changing requirements and regulations - and if you do "let Stripe do (the boring bits)", you've exposed Stripe to your customers anyway. So why not make all the rigorous onboarding and collection their "problem"?
tell this to my client and PM
All the day-to-day interactions remain on your website. You get associated with the "cool" parts of your product; Stripe gets associated with the "boring" parts of the process (no insult intended, @pearl sundial )