#dgsunesen-account

1 messages · Page 1 of 1 (latest)

fathom drum
#

since it's about a live account and not a coding question I'd suggest reaching back out to our support team for help

whole robin
#

hm...

#

when I look at this request id: req_ls7rZ3z0AbnT7K

#

it shows me that I have provided back and front of my identification

#

but it does not say anything about pending

#

do you see anything wrong here?

fathom drum
#

well note you're supposed to use webhooks(you don't seem to, which is a massive problem as a Custom Connect platform) to listen to account.updated events for changes in status.
The current status of that account seems to be that nothing is required and it's fully active. We're going to eventually need a user identity document before July 21 to keep the account active.

whole robin
#

But shouldn't I get something back like "pending" after I succesfully uploaded the ID documents?

fathom drum
#

well that request is not uploading an identity document

#

you can also see that the status of the document verification at the time was failed

whole robin
#

I asked support what they could see after I uploaded my documents here: req_ixUNr032rCCgay

fathom drum
fathom drum
whole robin
#

I'm just wondering why I'm not seeing any pending status on my user when I get the lastest data on the user

fathom drum
#

because it's not pending, we checked and the document wasn't accepted and we decided it's unverified

#

the API-facing reason we gave you is in the screenshot above and I linked to the API field for it, and the docs that explain how your system can interpret that code

unknown.png
#

note I highly recommend not using Custom Connect in this way unless you have a lot of development resources as it's very complex, most platforms should use Express