ISO mdoc and mobile driving licence verification
mso_mdoc is the credential format identifier used for ISO mobile documents in an OID4VP request. A mobile driving licence (mDL) is one possible credential; the doc_type, namespace, claims, issuer, and supported presentation profile determine which document is actually requested.
Create an mdoc request
For a mobile driving licence profile, provide the expected issuer, document type, namespace, and only the claim names required by your flow:
import { EidClient } from "@dlbr/eid-sdk";
const id = new EidClient({
baseUrl: process.env.DLBR_ID_BASE_URL!,
apiKey: process.env.DLBR_ID_API_KEY!,
mode: "test",
});
const session = await id.sessions.create({
credentials: [{
id: "driving-licence",
format: "mso_mdoc",
issuer_id: "https://issuer.example",
namespace: "org.iso.18013.5.1",
doc_type: "org.iso.18013.5.1.mDL",
claims: ["driving_privileges"],
}],
});
console.log(session.session_id, session.qr_code_url);The claim identifiers must be supported by the wallet credential and the issuer configuration. For EUDI PID requests, use the EUDI PID document type, namespace, and claim mapping described in the advanced OID4VP guide.
What the verifier checks
The gateway validates the issuer-signed document and the device proof against the configured trust and the session's OID4VP request. The device proof binds the response to the verifier and transaction. The gateway returns the requested result only after verification; the relying party still makes its own rental, access, or eligibility decision.
An mdoc request does not guarantee that every wallet supports the requested claims or presentation mode. Confirm issuer availability, trust material, profile requirements, and local acceptance rules for each deployment. Do not describe a test credential or synthetic sandbox response as production-issued identity evidence.