A wallet can hold more than one credential format, and a verifier request may accept only a particular format and set of claims. When a PID is not offered or cannot satisfy a request, what should an integration team compare first?\n\nI am looking for a repeatable diagnostic that covers the credential selected in the wallet, the requested format, and the verifier’s input descriptor—without sharing personal data or full presentation tokens. An older EUDI Reference Implementation discussion raised a similar interoperability issue.
What should I check when an SD-JWT PID is missing from a wallet presentation?
draganaberbatovic
Conversation
1 reply
Start by confirming the stored credential’s format and type, then compare them with the verifier request’s accepted format, document type, and requested claim paths. Select a matching test credential explicitly and retry with the smallest useful request. If it still fails, capture wallet/verifier versions and a redacted request/response summary; never post a PID, full token, private key, or other personal credential data. The linked discussion describes one historical UI issue, so verify current app behavior before applying that explanation.
Sign in with GitHub to reply.