#senor-taco_connect-verification

1 messages ยท Page 1 of 1 (latest)

azure spruceBOT
#

๐Ÿ‘‹ 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/1216883337558364281

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

safe pagodaBOT
woeful oriole
#

Hi ๐Ÿ‘‹

This server is specifically for unblocking developers coding integrations with Stripe APIs.

rigid lagoon
#

This is the account in question acct_1OswgzQtRrTg9YLd

#

I'm not the developer unfortunately but this is what is happening.

#

We collect all the required details for a connexxred account. But in stripe test it always puts a restriction on it, even thos the info is all being submitted.

woeful oriole
#

This account was created today

#

Even in Test mode, some of the verification checks take a little while

rigid lagoon
#

created yesterday

woeful oriole
#
pending_verification: [
      "individual.address.city",
      "individual.address.line1",
      "individual.address.postal_code",
      "individual.address.state",
      "individual.id_number",
    ],
rigid lagoon
#

It makes it restricted immediately though

woeful oriole
#

That is normal and expected

rigid lagoon
#

So you can see on my account that the address verification is not verified even though my user submitted this data during onboarding

#

?

woeful oriole
#

Yes. The user may have submitted it but we will still take time to verify it. In test mode the delay exists to better simulate what you can expect in Live mode

safe pagodaBOT
#

senor-taco_connect-verification