> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.8/product-specifications/core-functions/9.-verify-record.md). # 10. Verify record Certificates come equipped with a printed QR code that, when scanned, directs the user to OpenCRVS. This feature enables users to cross-check the information presented on the certificate against the registration data stored within OpenCRVS, thereby ensuring the certificate's authenticity and validity. ### **Pre condition** A record has been registered ### **Triggers** * QR code on a certificate is scanned * A user has `scope:record.registration-verify-certified-copies` ### **Standard flow** 1. QR code navigates user to OpenCRVS 2. User logs in using their username and password 3. User is presented with partial information about the record 4. User compares details recorded in the system with those on the certificate 5. User verifies that the certificate is genuine ### **Post conditions** * User closes partial view of the record * User can scan another certificate QR code ### **Variations/Exceptions** * If the QR code is invalid, then the user is shown an invalid QR code message * To prevent a man-in-the-middle attack, where someone creates a fake website resembling OpenCRVS to deceive users into believing that they are viewing genuine registration data, users are prompted to verify the URL of the webpage. It is essential to train users to check the authentic URL of their OpenCRVS instance to ensure they are accessing the genuine website. {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.opencrvs.org/v1.8/product-specifications/core-functions/9.-verify-record.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.