These are the pre-configured journey to perform Employment History Verification using Mobile Number or UAN Number or PAN Number.

Journeys	Input	Output
Employment History Journey	1. Mobile Number	1. Full Name
	or	2. D.O.B
	1. UAN Number	3. Employment History
		4. UAN Number

Employment History Verification Journey

The businesses can configure these checks with our Employment History Verification journeys

Ownership check

Journey Input Data

{
  "mobile_no": "XXXXXXXXXX",
}

OR

{
  "uan_no": "XXXXXXXXXX",
}

Journey Output Data

{
  "transaction_id": "",
  "journey_transaction_id": "",
  "journey_id": "",
  "status": "SUCCESS|FAILURE|IN_PROGRESS",
  "status_code": "Refer to the table below",
  "message": "Refer to the table below",
  "decision": "CLEAR|MUST REVIEW|NEEDS REVIEW",
  "checks": [],
  "data": {
    "employment_history": [
      {
        "uan": "",
        "employer": [
          {
            "name": "",
            "memberId": "",
            "settled": "",
            "isNameUnique": "",
            "matchName": "",
            "lastMonth": "",
            "isRecent": "",
            "isNameExact": "",
            "isEmployed": "",
            "nameConfidence": "",
            "emplrScore": "",
            "uanNameMatch": ""
          }
        ],
        "source": "",
        "issuer": "",
        "decision": "",
        "checks": []
      }
    ]
  }
}

📘
These journeys do not include any pre-configured Ownership or Fraud Checks. To add these checks, please contact your Account Manager.

Status Codes

Scenario	HttpStatus	status	status_code	message
When request is successful and Mobile details are available.	200	SUCCESS	success	Request successful
When no details found at Source for given Mobile/ UAN/ Number	200	FAILURE	document_not_found	Entity not found
When the Mobile/ UAN Number is not valid	200	FAILURE	invalid_input	Mobile/ UAN/ Number is invalid
When Input doesn't contain the Mobile/ UAN Number field.	400	FAILURE	invalid_request	Mobile/ UAN/ Number is required
Any unhandled error from Equal end	500	FAILURE	internal_server_error	Something went wrong, please try again.
Too many requests	429	No object will be sent, throttling happens at the gateway level.
Service Unavailable	503
Invalid Client Credentials	401	FAILURE	invalid_credentials	Invalid Client Credentials

Status

Possible Values	Description
SUCCESS	Shows that the verification process was completed successfully.
FAILURE	Indicates that the verification process did not succeed.
IN_PROGRESS	Signifies that the verification process is currently underway and has not yet been completed.

Decision

Possible Values	Description
CLEAR	Indicates that the verification has been completed and the information is confirmed as accurate and legitimate.
MUST REVIEW	Signifies that further review is needed due to potential issues or inconsistencies in the verification results.
NEEDS REVIEW	Suggests that the verification has identified areas that require further investigation or clarification before a final determination can be made.

📘
Journey ID will be shared as part of Onboarding