Skip to main content

DCQL – KYC request with Photo ID and address proof

This workflow demonstrates a KYC scenario where a verifier requires:

  • A Photo ID credential for identity verification.
  • A separate Proof of Address, where either a Utility Bill or Bank Statement is acceptable.

The workflow is executed using OpenID4VC APIs and DCQL-based presentation requests, combining an identity credential with a separate Proof of Address.

For the underlying DCQL query, diagram and example, see the “KYC request with Photo ID and address proof” use case in our DCQL concepts article.

Fig 04: Require a Photo ID (Mandatory) plus Proof of Address via Utility Bill or Bank Statement.

Step 1: Get the API Key (Issuer Admin)​

To obtain your API key, please contact [email protected]. Once you have received your API key, enter it in the field below and click the Set API Key button to save it for future use.

Step 2: Create Credential Definition (Issuer Admin)​

To create a credential definition, run the interactive blocks below using the Run button. Alternatively, you can manually copy the JSON body and use it in the API request available here.

Note: The kid value is mandatory with trust anchor x509. To obtain the kid value for the respective organisation use the API available here.

From the API response, copy the credentialDefinitionId and id value from the credentialDefinitions array for use in the Step 3.

Credential definitions for this KYC use case:

Bank Statement​

A Bank Statement credential provides verified financial information including account details, transaction history, and balance information. It serves as a proof of financial stability and is commonly used for KYC (Know Your Customer) verification processes in accordance with European Anti-Money Laundering directives.

Request

Response

Utility Bill​

A Utility Bill credential contains verified address information from utility service providers such as electricity, water, or telecommunications companies. It serves as a proof of residence and is commonly required for address verification in accordance with EU identity verification standards.

Request

Response

Photo ID​

Photo ID is based on an electronic Machine-Readable Travel Document (eMRTD), is issued and verified as a digital credential under the EU Digital Travel Credential (DTC) framework and the EU Digital Identity Framework (eIDAS Regulation). For more technical details, please refer to EWC RFC 013: Issue Photo ID.

Request

Response

Step 3: Issue and Receive Credential (Issuer/Holder)​

The holder of the wallet submits a request for the issuance of a credential by executing the JSON code block below using the Run button in InTime issuance mode. Choose the credential format and replace <credentialDefinitionId> and <id> with the actual values obtained from the previous step. Alternatively, you may use the API available here.

The user needs to issue three credentials to the holder wallet:

  • Bank Statement
  • Utility Bill
  • Photo ID

After receiving the response, toggle the button provided to dynamically generate a QR code. The EUDI Wallet/Holder can then accept the credential offer using the Data Wallet (or any other EU Digital Identity Wallet) by either scanning the QR code or directly accessing the credential offer on their mobile device, such as via a browser.

Bank Statement​

Request

Response

Utility Bill​

Request

Response

Photo ID​

Request

Response

To receive and accept the credential via API. First, use the credentialOffer to call the Receive Credential API. Once you have the response, copy the credentialId and provide it at Accept Credential API to accept the credential.

Step 4: Create Presentation Definition (Verifier Admin)​

To create a presentation definition for requesting proof, you can run the code block below using the Run button. Alternatively, you can manually copy the code block and use it in the body of the API request provided here.

Request

Response

Once a presentation definition is created, the presentationDefinitionId can be reused to verify multiple credentials (Step 6).

Step 5: Create Verification Request (Verifier/Relying Party)​

To create the verification request, execute the code block below using the Run button. Alternatively, you can manually copy the JSON and use it in the body of the API available here.

After receiving the response, toggle the button provided to dynamically generate a QR code. The EUDI Wallet/Holder can then accept the verification request using the Data Wallet (or any other EU Digital Identity Wallet) by either scanning the QR code or directly accessing the verification request on their mobile device, such as via a browser.

Request

Response

Users can copy the presentationExchangeId from the JSON response for use in Step 7 to read verification history.

Step 6: Send and Receive Verifiable Presentation (Holder)​

The holder wallet accepts (consents) to send the requested credentials.

  • Receive Verification:
    • Use the vpTokenQrCode(step 5) with the API available here to receive the verification.
    • Copy the presentationId from the JSON response received from Receive Verification for use in Step 6b.
  • Filter Verification:
    • Use that presentationId with the API available here to find matching credentials.
    • Save the <id> and <credentialId> from the response.
  • Send Verification:
    • Use the presentationId, <id> and <credentialId> with the API available here to send the credentials to the verifier.

Step 7: Send and Receive Verifiable Presentation (Verifier/Relying Party)​

  • The Verfier (Relying Party) receives the requested credentials and can verify it. They may read the received credential by executing the Read Verification History API.
  • From the response received, the vpTokenResponse can be decoded using JWT Decoder.
  • From the decoded response, the verifiableCredential inside the 'vp' can be further decoded to view the received credentials.