Credential verification consists of defining a verification template / proof template, using it to generate a proof request, delivering the proof request to a holder, receiving the proof response from the holder's wallet, and checking that response for consistency. The Truvera API automates many of these steps for you. The REST API does not contain functions to create a verifiable presentation, as that is done through the Wallet SDK. The open source Truvera Credential SDK also contains the foundational capabilities needed to create proof presentations.
Our system supports the DIF Presentation Exchange (PEX) syntax for querying and filtering credentials.
These are a few common examples of credential verification. More examples are in the documentation for DIF Presentation Exchange.
A verifier might require that the holder have an income between $100,000 and $200,000 per year. This could be requested using the following input_descriptor
{
path: ['$.credentialSubject.income.2022.total'],
filter: {
type: 'number',
minimum: 100000,
maximum: 200000
},
}
A verifier might require that the credential be issued after a certain date. In this example the verifier is requiring that the credential was issued between January 1, 2020 and December 31, 2020.
{
path: ['$.issuanceDate'],
filter: {
"type": "string",
"format": "date",
"formatMinimum": "2020-01-01",
"formatMaximum": "2020-12-31"
},
}