#pratp

1 messages · Page 1 of 1 (latest)

blissful locustBOT
maiden basalt
#

Hi

#

for requestId - req_o4yRGR4eDLe2cj - meail was defaulted

shy plank
#

Hi, are you able to share the API reference document you're using or the request on this?

maiden basalt
#

email*

#

but for req_k74TL8O4OgfNjJ - email was not defaulted

#

so there are 2 request ids i sent you

#

one has email defaulted other doesnt

#

can you let me kno

shy plank
#

Looking at these requests

fleet flume
#

as a User: Stripe is responsible for following KYC and AML regulations. Part of those regulations is that Stripe is required to independently verify/authenticate the identity of the individual creating the account. They are not allowed to "take your word" for it; they must collect it separately. It isn't just that their code won't take the values you provide - it's that they are not allowed to take the values you provide. If you had seen values "PREFILLED" before, that was due (I guarantee) to the BROWSER caching and pre-filling the fields - not Stripe.

maiden basalt
#

so we cant prefill email and phone number?

#

this is for type=express

fleet flume
#

same answer

#

The support engineers here won't say this as bluntly as I can - I don't work for Stripe, so I am not making legal representation for Stripe - but the same answer applies. This is due to both legal requirements, AND requirements by the payment networks. Stripe is REQUIRED to INDEPENDENTLY collect and verify the information. It is not just "they won't" - it's that "they can't due to regulations and requirements". There is no "secret backdoor"

#

And, yes, I've seen the same thing - I use express accounts - and yes, I've explored the API very very deeply. There is no such option because there can't be any such option.

#

migrations are a different thing (you'll likely see them mentioned on the discord) - in that case, a platform is programatically moving accounts that have already been verified/authenticated - but new accounts need to be verified, and Stripe is obligated to do so independently of your API calls.

#

Think of it from Stripe's side: they really can't go to the regulatory bodies and say "hey, this guy over here said it's good, so hey that's good enough for us"

maiden basalt
#

thanks

fleet flume
#

I do recommend some form of prompt for your users, informing them to expect to provide that information, and why - so they won't feel like they've made a mistake