Veriff
How does it work?
By using this integration, you will get result of person verification based on checking their identity document and face image. Those data will be used to check if document and face of verifing person is real and valid.
In addition to the verification result, you will also receive personal data and identity document data.
More about this service you can find here
Response Content
veriff
status
string
The status of the identity verification. Possible values are APPROVED, PENDING, or REJECTED.
reason
string
The reason for the verification status, if applicable.
object
An object containing personal information of the individual being verified. This field represents another table.
object
An object containing information about the identity document used for verification. This field represents another table.
highRisk
boolean
Whether the verification result is deemed to be high risk.
array of objects
An array of objects that describe the type and category of risk factors associated with the verification result. Each object represents another table.
identity
lastName
string
The last name of the individual.
firstName
string
The first name of the individual.
idNumber
string
The national ID number of the individual.
dateOfBirth
string
The date of birth of the individual in the format YYYY-MM-DD.
nationality
string
The nationality of the individual.
citizenship
string
The citizenship of the individual.
gender
string
The gender of the individual. Possible values are M (male), F (female), X (indeterminate/intersex/unspecified), or N (not applicable).
yearOfBirth
string
The year of birth of the individual.
placeOfBirth
string
The place of birth of the individual.
document
number
string
The document number.
type
string
The type of the document. Possible values are PASSPORT, ID_CARD, DRIVERS_LICENSE, or RESIDENCE_PERMIT.
country
string
The country of issuance of the document.
validFrom
string
The start date of the validity period of the document in the format YYYY-MM-DD.
validUntil
string
The end date of the validity period of the document in the format YYYY-MM-DD.
riskLabels
label
string
The label of the risk factor.
category
string
The category of the risk factor. Possible values are DEVICE, NETWORK, or OTHER.
Reason and Decision codes
Decline veriff.idVerification.reasonCode
102
Suspected document tampering.
103
Person showing the document does not appear to match document photo.
105
Suspicious behaviour.
106
Known fraud.
108
Velocity/abuse duplicated user.
109
Velocity/abuse duplicated device.
110
Velocity/abuse duplicated ID.
112
Restricted IP location
113
Suspicious behaviour - Identity Farming
502
Multiple parties present in session
503
Attempted deceit
504
Attempted deceit, device screen used
505
Attempted deceit, printout used
507
Presented document tampered, data cross reference
508
Presented document tampered, document similarity to specimen
509
Person showing the document does not match document photo
515
Attempted deceit, device screen used for face image
526
Attempted deceit, photos streamed
527
Unable to collect proof of address data
528
Proof of address issue date too old
Resubmit veriff.idVerification.reasonCode
201
Video and/or photos missing.
204
Poor image quality.
205
Document damaged.
206
Document type not supported.
602
Presented document type not supported.
603
Video missing.
605
Face image missing.
606
Face is not clearly visible.
608
Document front missing.
609
Document back missing.
614
Document front not fully in frame.
615
Document back not fully in frame.
619
Document data not visible.
620
Presented document expired.
621
Document annulled or damaged.
625
Unable to collect surname.
626
Unable to collect first names.
627
Unable to collect date of birth.
628
Unable to collect issue date.
629
Unable to collect expiry date.
630
Unable to collect gender.
631
Unable to collect document number.
632
Unable to collect personal number.
633
Unable to collect nationality.
634
Unable to collect home address.
635
Document and face image missing.
Decision veriff.idVerification.code
9001
Positive: Person was verified. The verification process is complete. Accessing the sessionURL again will show the client that nothing is to be done here.
9102
Negative: Person has not been verified. The verification process is complete. Either it was a fraud case or some other severe reason that the person can not be verified. You should investigate the session further and read the "reason". If you decide to give the client another try you need to create a new session.
9103
Resubmitted: Resubmission has been requested. The verification process is not completed. Something was missing from the client and she or he needs to go through the flow once more. The same sessionURL can and should be used for this purpose.
9104
Negative: Verification has been expired. The verification process is complete. After 7 days the session gets expired. If the client started the verification process we reply "abandoned" here, otherwise if the client never arrived in our environment the status will be "expired"
9121
Review: Review status is issued whenever automation engine could not issue a conclusive decision and the verification session needs to be reviewed by a human. This status will be sent depending on service agreement.
Example response
Last updated