China Resident ID Card Verification

overview and purpose overview the china national id verification api is a specialized digital tool designed specifically for businesses operating within china this api provides crucial support in confirming the authenticity of personal information against official chinese records, enhancing trust, accuracy, and compliance across various sectors use cases identity verification useful for businesses and financial institutions to authenticate the identity of individuals during account creation, loan application processing, or other identity verification procedures compliance checks assists organizations in complying with regulatory requirements by ensuring all customer identities are verified against official government databases fraud prevention helps prevent fraudulent activities by confirming the authenticity of personal identity information provided by users api details api overview the verification api enables the validation of various personal data inputs, including full name, date of birth, national id number each input is cross referenced against authorized sources to provide a overall verified / not verified result note the name must be provided in chinese authorization access to this api is granted via an authorization token, ensuring secure and authenticated access for authorized users request body preproduction curl location 'https //api preproduction signzy app/api/v3/global kyc verify/cn/nid' \\ \ header 'authorization < auth token >' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "", "dateofbirth" "", "identityinformation" { "nationalidnumber" "" }, "consent" true }' production curl location 'https //api signzy app/api/v3/global kyc verify/cn/nid' \\ \ header 'authorization < auth token ' \\ \ header 'content type application/json' \\ \ data '{ "fullname" "gou yunnian", "dateofbirth" "1961 12 05", "identityinformation" { "nationalidnumber" "442521196112052420" }, "consent" true }' request body parameters true false 163,98,243false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type response body { "result" { "verificationresult" { "fullname" "na", "dateofbirth" "na", "nationalidnumber" "na" }, "sourceverificationstatus" "verified" } } to maintain consistency across all the kyc apis the output parameters of fullname, dateofbirth and nationalidnumber would be "na" while the main reference point would be sourceverificationstatus response body parameters true false 241false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type error code and response mapping 400 (bad request) { "error" { "name" "error", "message" "bad input and description ", "status" 400, "reason" "validation error", "type" "bad request", "statuscode" 400 } } 401(unauthorized) { "error" { "name" "error", "message" "invalid authentication credentials", "status" 401, "reason" "authentication error", "type" "bad request", "statuscode" 401 } } 403 (forbidden) { "error" { "name" "error", "message" "forbidden", "reason" "error", "type" "bad request", "statuscode" "403" } } 500 (internal server error) { "error" { "name" "error", "message" "internal server error", "status" 500, "reason" "error", "type" "bad request", "statuscode" 500 } } 409(upstream down { "error" { "name" "error", "message" "upstream down", "status" 409, "reason" "error", "type" "bad request", "statuscode" 409 } } true falsefalse left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at help\@signzy com we strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively we value your feedback and are committed to making your experience smooth and enjoyable our team is dedicated to assisting you with any needs you may have thank you for choosing our services we look forward to helping you!