> 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.md).

# PRS.ID.03: SP-System authenticates beneficiary identity using verifiable credentials

This use case is applicable at all stages of the social protection delivery chain. Its purpose is to verify the beneficiary identity at any step needed in business process.

This use case applies in cases where the SP system authenticates a person or needs Know Your Customer (KYC) data.

Please refer to the sub-pages for descriptions that illustrate this generic use case using examples from common social protection programs.

## API Reference 

* [Verifiable credentials ](https://www.w3.org/TR/vc-data-model-2.0)
* [OpenID](https://openid.net/specs/openid-connect-core-1_0.html)


---

# 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.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.