> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/id-systems-v1.0.0/wip-id-systems-and-sp-system-interface/1.-crvs/1.2-process/prs.id.03-sp-system-authenticates-beneficiary-identity-using-verifiable-credentials/example-1-registration-offline-authentication-identification.md).

# Example 1: Registration - offline authentication, identification

This process allows beneficiaries to present **verifiable credentials issued by trusted authorities** (e.g., identification system, civil registry, social registry, or health authority) to enroll in a social protection system (SP-System).

## Process Flow

This process allows beneficiaries to use Verifiable Credentials (VCs) to enroll in a social protection system.

**Process Flow: Registration to SP-system**

<table><thead><tr><th width="213">Section </th><th>Description </th></tr></thead><tbody><tr><td>Actors and Entities</td><td>SP system, beneficiary, digital wallet/digitally signed QR code</td></tr><tr><td>Assumptions</td><td><p></p><ul><li>Issuers are onboarded and authorized to issue <strong>cryptographically signed verifiable credentials</strong>.</li><li>Beneficiaries have access to <strong>a digital device</strong> (e.g., smartphone) or printed secure QR code on paper/card.</li><li>The SP-System supports <strong>verification</strong> of VCs.</li></ul></td></tr><tr><td>Prerequisites</td><td><p></p><ul><li>Issuing authorities have issued verifiable credentials to eligible individuals.</li><li>Beneficiary has installed and activated a <strong>digital wallet</strong> or have stored the required VCs on digital device or has them in some paper/card.</li><li>The SP-System is integrated with the trust framework and verification infrastructure (e.g., DID resolver, revocation registry).</li><li>Consent and data-sharing policies are in place, aligned with data protection laws.</li></ul><p></p></td></tr><tr><td>Process Inputs</td><td>SP system collects verifiable credentials presented by the beneficiary</td></tr><tr><td>Process Flow Steps</td><td><p><strong>Step 1:</strong> The beneficiary opts to register in the SP-System using verifiable credentials.</p><p></p><p><strong>Step 2:</strong> The beneficiary presents the VC to the service provider. if wallet is used, the wallet presents selected VCs data attributes consented to by the beneficiary to the SP-System via secure protocols.</p><p></p><p><strong>Step 3:</strong> SP-System displays what data is being used and collects explicit beneficiary consent. </p><p></p><p><strong>Step 4:  T</strong>he SP-System validates the digital signature, confirms issuer trust status and the provider does manual/digital verification of beneficiary face with that presented on VC.</p><p></p><p><strong>Step 5:</strong> SP-System processes the verified identity claims to determine program eligibility and benefit type.</p><p></p><p><strong>Step 7:</strong> SP-System confirms enrollment and optionally issues a <strong>enrollment verifiable credential</strong> to the beneficiary. </p></td></tr><tr><td>Outputs</td><td>Register beneficiary in the SP-System. Optionally: Issuance of a <strong>Social Protection Credential</strong></td></tr><tr><td>Control Points</td><td><p></p><ul><li><strong>Credential Validation</strong>: Ensure credentials are from trusted issuers and not revoked.</li><li><strong>Data Privacy &#x26; Consent</strong>: Beneficiary consent must be logged and linked to specific data use.</li><li><strong>Issuer Trust Registry</strong>: The system must reference an up-to-date list of authorized issuers.</li><li><strong>Revocation Check</strong>: Real-time revocation status must be confirmed at the point of verification.</li></ul></td></tr><tr><td>Exception Handling</td><td>Refer to Exception Handling for alternate flows.</td></tr></tbody></table>

## Diagram 1 - Enrollment in SP-System program

<figure><img src="https://1423868655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvbstdtqZjt3kXL01w3dN%2Fuploads%2FxDCbOy7JYk8iT4EBrgGh%2Fid0ffline.drawio.svg?alt=media&amp;token=b3ba3dea-3cda-448c-a652-64a3b60aa40f" alt=""><figcaption></figcaption></figure>


---

# 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://standards.spdci.org/standards/dci-standards/id-systems-v1.0.0/wip-id-systems-and-sp-system-interface/1.-crvs/1.2-process/prs.id.03-sp-system-authenticates-beneficiary-identity-using-verifiable-credentials/example-1-registration-offline-authentication-identification.md?ask=<question>&goal=<user_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.