Review offer status, entries and verification reads
Step 1 of 5 in Prove the credential status profiles.
All four profiles use the same backend operations around issuance and verification. Wallet grant exchange, credential retrieval, storage and presentation are separate holder activities, not backend requests.
Follow an offer with the correlation_id returned at creation. Only credential_issued reports
completed issuance; issuance_data carries configuration and credential identifiers, not a substitute
for the credential-bound status URI and index.
Read and change a status entry with the list id from createStatusList and the index from the
issued credential. List creation does not allocate an entry. Keep the media type and binary bytes of
CWT status responses.
Verify with an authorization request once the verifier, DCQL query and trust policy are configured, and poll its status. A new request or a pending status is not a successful verification.
The full narrative of this shared workflow is on the profile walkthroughs page.
Next
Continue with step 2, SD-JWT VC with JWT Token Status.