OpenID4VP: the protocol behind the request
OpenID for Verifiable Presentations (OpenID4VP) is the open standard a “verifier” — in this case the webshop — uses to send a presentation request to the customer’s wallet. The wallet shows the customer what data is being requested and by whom, and the customer decides whether to approve it.
DCQL: specifying exactly what you need
Digital Credentials Query Language (DCQL) describes, within the request, exactly which credentials and fields are required. For a simple login, eIDAS Solutions asks only for first name, last name and email address; at checkout, an optional address credential is added (street, city, postal code, country, phone number). Because name/birth data and address data are often stored as separate credentials in the wallet, DCQL supports “credential sets”: the webshop specifies which combination is required (identity) and which is optional (address).
Selective disclosure with SD-JWT VC
Credentials themselves are commonly issued in the dc+sd-jwt format (SD-JWT Verifiable Credentials), which supports selective disclosure: the wallet can decide, per field, whether to reveal it, without invalidating the issuer’s signature. This lets a customer prove their address is genuinely verified without, say, sharing their date of birth if it wasn’t requested.
In practice: Magento + UniCore
In our Magento integration, the shop sends a DCQL request to a UniCore SSI agent, which handles the session with the wallet. Once the customer approves, the webshop receives the verified data via a webhook and the account or checkout form is filled in automatically.