{"id":3886,"date":"2026-05-18T11:36:26","date_gmt":"2026-05-18T09:36:26","guid":{"rendered":"http:\/\/tsholo"},"modified":"2026-05-18T11:36:26","modified_gmt":"2026-05-18T09:36:26","password":"","slug":"what-information-is-usually-needed-for-a-verification-request","status":"publish","type":"docs","link":"https:\/\/j-cred.co.za\/zh\/helpcenter\/what-information-is-usually-needed-for-a-verification-request\/","title":{"rendered":"What Information Is Usually Needed for a Verification Request"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>The information needed depends on the check. Common fields include full names, identity number, date of birth, contact details, document images, qualification details, employer details, company registration number, case reference, consent record and purpose of request.<\/p>\n<h2>Why it matters<\/h2>\n<p>Good input quality improves matching accuracy, reduces failed requests and avoids unnecessary escalations. Poor input quality can cause false non-matches, duplicated work and delayed decisions.<\/p>\n<h2>How to think about it<\/h2>\n<ul>\n<li>Collect the minimum information needed for the check.<\/li>\n<li>Validate obvious formatting errors before submitting the request.<\/li>\n<li>Capture the purpose and reference number at the start of the process.<\/li>\n<li>Separate applicant-supplied data from source-returned data.<\/li>\n<li>Record who submitted the request and when.<\/li>\n<\/ul>\n<h2>Common examples<\/h2>\n<ul>\n<li>For a qualification check: certificate type, year, institution or assessment body where relevant, names and ID\/passport number.<\/li>\n<li>For a company check: registration number, company name and director or representative context.<\/li>\n<li>For a trace check: identity details, last known contacts and lawful collection purpose.<\/li>\n<li>For support: search ID, request date, user, client and screenshot if appropriate.<\/li>\n<\/ul>\n<h2>Responsible use reminders<\/h2>\n<ul>\n<li>Avoid collecting documents because they are convenient if they are not necessary.<\/li>\n<li>Protect high-risk identifiers such as ID numbers, biometric data and criminal history information.<\/li>\n<li>Use standard input templates to improve data quality.<\/li>\n<\/ul>\n<hr \/>\n<p><strong>Public knowledge note:<\/strong> This article is intended as general education for verification, compliance, fraud prevention and responsible data-use discussions. It is not legal advice and should not replace your organisation&#8217;s own compliance review, regulator guidance, or contractual obligations.<\/p>","protected":false},"excerpt":{"rendered":"<p>Overview The information needed depends on the check. Common fields include full names, identity number, date of birth, contact details, document images, qualification details, employer details, company registration number, case reference, consent record and purpose of request. Why it matters Good input quality improves matching accuracy, reduces failed requests and avoids unnecessary escalations. Poor input quality can cause false non-matches, duplicated work and delayed decisions. How to think about it Collect the minimum information needed for the check. Validate obvious formatting errors before submitting the request. Capture the purpose and reference number at the start of the process. Separate applicant-supplied data from source-returned data. Record who submitted the request and when. Common examples For a qualification check: certificate type, year, institution or assessment body where relevant, names and ID\/passport number. For a company check: registration number, company name and director or representative context. For a trace check: identity details, last known contacts and lawful collection purpose. For support: search ID, request date, user, client and screenshot if appropriate. Responsible use reminders Avoid collecting documents because they are convenient if they are not necessary. Protect high-risk identifiers such as ID numbers, biometric data and criminal history information. Use standard input templates to improve data quality. Public knowledge note: This article is intended as general education for verification, compliance, fraud prevention and responsible data-use discussions. It is not legal advice and should not replace your organisation&#8217;s own compliance review, regulator guidance, or contractual obligations.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_eb_attr":"","footnotes":""},"doc_category":[27],"doc_tag":[],"class_list":["post-3886","docs","type-docs","status-publish","hentry","doc_category-public-verification-101"],"blocksy_meta":[],"year_month":"2026-06","word_count":243,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"KTO Digital Admin","author_nicename":"tsholo","author_url":"https:\/\/j-cred.co.za\/zh\/author\/tsholo\/"},"doc_category_info":[{"term_name":"Verification 101","term_url":"https:\/\/j-cred.co.za\/zh\/docs-category\/public-verification-101\/"}],"doc_tag_info":[],"_links":{"self":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3886","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/comments?post=3886"}],"version-history":[{"count":0,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3886\/revisions"}],"wp:attachment":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/media?parent=3886"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_category?post=3886"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_tag?post=3886"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}