Skip to main content

Accepting Credentials

Every wallet can act as a holder — receiving and storing credentials issued to it — without any configuration. This page covers the ways credentials and requests reach you, and how you act on them.

The Messages inbox​

Anything a counterparty wallet sends to you that needs an action — a connection invitation, a credential offer, or a verification request delivered over WMP — arrives as a Message, not silently in the background.

  • The bell icon in the header shows a red dot when you have unread messages and lists them in a popup, with a View All Messages link.
  • The full inbox lives at Messages (/messages) — every message, read and unread, each showing a type icon, a relative timestamp ("5m ago," "2h ago"), sender name, message text, an unread indicator, and — once acted on — an accepted/rejected outcome icon.
  • Click a message to open its detail view.

Unread messages that require action show an inline action widget, described below by message type.

Accepting a credential offer​

Manually, with an offer URL​

If someone shares an offer URL or QR code with you directly (rather than through a WMP connection), use the Accept button on your wallet's Identity Info panel. This opens Accept Credential Offer:

  • Offer URL (paste it in) — your wallet's own identifier is shown above for reference/copying.
  • PIN (optional, if the issuer requires one).

Click Accept Offer.

If the issuer requires you to present other credentials first (a CredentialRequirements or VPDriven issuer — see Issuing Credentials), you'll see a presentation-candidates screen instead: "{issuer} requires you to present the following credentials before accepting the offer," with a checkbox list of your matching credentials for each requirement. Select the ones to present and click Confirm & Accept.

On success: a green check, "Credential(s) Accepted," and a note that they've been added to your wallet.

Via a Message (WMP-delivered offer)​

If the offer arrives over an existing WMP connection, it shows up as a message instead of a URL you have to paste anywhere. The message shows who it's from (with a "Verified connection" or "Unverified" chip depending on whether that peer's identity has been confirmed — see below) and, if available, a View identity assertion link. Click Accept offer.

On success, a modal lists the credential(s) you received with a Done button. On failure, an error modal appears with Dismiss.

Responding to a verification request via a Message​

A verification request delivered over WMP also arrives as a message, with its own accept/respond action — functionally the same idea as the offer flow above: review who's asking and what they want, then respond from the message.

Setting up a WMP connection​

Before offers or verification requests can flow directly (no QR code per interaction), two wallets need a verified connection. From the wallet dashboard's WMP Connections section, click Create verified connection. This is a two-step dialog:

Step 1 — Connect​

Either:

  • Create invitation — Nexus shows a QR code and a copyable URL; share it with the other party and wait (Nexus polls automatically once they accept), or
  • Accept invitation — paste in a URL someone else shared with you.

Step 2 — Verify Identity​

Once the invitation is accepted, both sides perform a mutual identity assertion — each wallet proves who it is to the other by presenting a credential. Nexus polls for the peer's request and lets you pick which of your valid credentials to present (if you have more than one option), then click Provide your identity. Once both sides have completed this, you'll see "Identity verified. Verified connection established."

From this point on, the connection appears in both wallets' WMP Connections lists, and either side can issue/verify directly to the other without new QR codes — see Issuing Credentials and Verifying Credentials.

ID token flows​

When an issuer chooses ID Token Exchange as the recipient-resolution method during issuance (see Issuing Credentials), it's your wallet that generates and returns the ID token behind the scenes when you open the shared URL — there's no separate consent screen beyond what's described above once the credential offer itself arrives.

Continue to The Nexus AI Assistant.