Verification Service Error Codes
Verification service error codes are typically related to various client-side errors in request payloads, including missing or invalid fields such as requestId, exchange_id, or status_id. They often occur due to incorrect payload formats, invalid parameters, or mismatches with expected data during authentication or verification processes.
For any error code not documented here, please reach out to our support team and share the message and URL with us. We will immediately help investigate why this issue occured for you.
What does Verification service Error Code xxx mean?
cidaas returns error status codes on different occasion. To find about the Verification service related errors, you can navigate to the Verification Service Error Code Page and lookup your retrieved error code. There you will also find useful hints how to solve them.
For example:
If you encounter this error code (VER1003) in your application, you should follow the hint provided.
The following table represents the Verification service error codes that will help you in identifying and troubleshooting various errors or failures.
| Code | Error | Error Description | Hint |
|---|---|---|---|
| VER1003 | client_error | client_error: issue with the request payload structure | the request payload fields should be separated by semicolon and the last property should not have the semicolon at the end |
| VER1004 | client_error | client_error: required fields are missing in the request payload | required fields are necessary in payload and you need to pass them |
| VER1005 | client_error | client_error: invalid "requestId" is passed in the request payload | you need to pass a valid "requestId" in the request payload |
| VER1011 | client_error | client_error: invalid “push_id” is sent in the payload | you need to send a valid “push_id” in the payload |
| VER1016 | client_error | client_error: “method” sent as path parameter is not active | you need to send active “method” as path parameter |
| VER1018 | client_error | client_error: invalid “exchange_id” or expired “exchange_id” is sent in payload | you need to send valid “exchange_id” in payload |
| VER1019 | client_error | client_error: error while validating FIDO2 response, invalid payload is sent in body | you need to send valid payload |
| VER1020 | client_error | client_error: verification “method” sent as path parameter is invalid | you need to send valid “method” as path parameter |
| VER1021 | client_error | client_error: invalid “exchange_id” is sent in the payload or invalid pass code is sent in payload | you need to send valid “exchange_id” or pass code in payload |
| VER1022 | client_error | client_error: invalid “exchange_id” is sent in the payload | you need to send valid “exchange_id” in payload |
| VER1023 | client_error | client_error: error while authenticating user with face recognition, invalid “exchange_id” is sent in payload | you need to send valid “exchange_id” in payload |
| VER1057 | client_error | client_error: invalid “amr_values” are sent in url query | you need to send valid “amr_values” in url query |
| VER1058 | client_error | client_error: unable to acknowledge push notification as verification “method” sent as path parameter or payload are invalid | you need to send valid “method” as path parameter and valid payload |
| VER1059 | client_error | client_error: “mobile_number” or “email” or “username” sent in payload is not matching with the flow when initiating the login | you need to send valid “mobile_number” or “email” or “username” in payload which matches the flow when initiating the login |
| VER1060 | client_error | client_error: invalid masked “sub” is sent in payload | you need to send valid masked “sub” in payload |
| VER1061 | client_error | client_error: “method” sent as path parameter is not configured by the user | you need to send “method” as path parameter which is already configured by the user |
| VER1064 | client_error | client_error: invalid payload is sent in the request | you need to send valid payload in request |
| VER1065 | client_error | client_error: invalid “medium_id” is sent in payload | you need to send valid “medium_id” in payload |
| VER1066 | client_error | client_error: no device is configured for the data passed in payload | you need to send valid payload in request, for which the device should be already configured |
| VER1068 | client_error | client_error: the “exchange_id” sent in payload is not initiated with single factor authentication | you need to send valid “exchange_id” in payload which should be initiated with single factor authentication |
| VER1069 | client_error | client_error: unable to fetch user info through the “medium_id” sent in payload | you need to send valid “medium_id” in payload |
| VER1070 | client_error | client_error: “identifier” sent in payload is not matching with the login flow | you need to send valid “identifier” which should match with the login flow |
| VER1071 | client_error | client_error: invalid “usage_type” is sent in the payload | you need to send valid “usage_type” in payload |
| VER1072 | client_error | client_error: invalid “password” is sent in the payload when doing the authentication | you need to send valid “password” |
| VER1073 | client_error | client_error: invalid data is sent in the payload and because of this reason getting error in fraud detection user existence check | you need to send valid payload |
| VER1075 | client_error | client_error: “status_id” sent as path parameter is invalid | you need to send valid “status_id” as path parameter |
| VER1078 | client_error | client_error: “status_id” sent as path parameter is invalid | you need to send valid “status_id” path parameter |
| VER1080 | client_error | client_error: invalid payload or invalid “status_id” path parameter is sent in the request | you need to send valid payload and “status_id” as path parameter |
| VER0104 | client_error | client_error: not able to find user | user information is not present or not found by using the identifier provided in the request |
Need Support?
Please contact us directly on our support page