Skip to content

Creditcrest Identity

Proof the applicant is who they say they are, kept with the file.

Know what was verified.

Email and mobile codes, an ID document and selfie, and a record of each.

What you do here. Check an applicant’s email, mobile, address and ID document, and keep a record of what was verified.

Check an addressTry it end to endTake the tour
You bring
Email, mobile, address and an ID document
You get
A record of what was verified, how, when and by whom
Holds the line
No code is stored on the server

Your residential address


For a lender’s developers

  • POST /v1/identity/contact/start {channel, destination, lender} — sends a six-digit code and returns a sealed token; the server keeps nothing.
  • POST /v1/identity/contact/resend {token} and POST /v1/identity/contact/check {token, code}.
  • GET /v1/identity/address?q= — address suggestions as the applicant types.
  • POST /v1/identity/id/start {reference, callback}, and POST /v1/identity/id/webhook for the provider’s signed result.

Until a deployment is in production with its approvals recorded, no message is sent and no provider is called; the answer says so.