search
WebsiteTruvera Workspace

Holder messaging via DIDComm

Holder messaging enables secure, encrypted communication between organizations and digital wallet holders using the DIDComm protocol. This feature allows verifiers to send authenticated requests directly to credential holders' wallets, enabling real-time verification workflows without requiring traditional authentication methods.

hashtag
Example use case

Consider a customer service scenario where enhanced identity verification is needed. A customer calls their bank to request a credit limit increase or password change. Rather than relying solely on traditional phone-based verification, the call center can leverage the customer's existing digital credentials for stronger authentication.

The process works as follows: the customer receives a credential during onboarding. The call center agent can initiate a credential verification request. The customer receives a secure message in their digital wallet via push notification, reviews the request, and responds using biometric authentication to unlock their wallet and confirm the data sharing.

hashtag
Technical implementation

hashtag
Prerequisites

  • Issuer has captured the holder's DID

  • Issuer is using a valid message schema

circle-info

Current Truvera wallet implementation supports only YES/NO holder messaging schema. Customers using the wallet SDK can implement custom schemas based on their needs.

hashtag
Encrypted message dispatch

Uses the Truvera API to send an encrypted DIDComm message to the holders DID.

On steps how to create the sender DID see the Create DID or step by step instructions in the Truvera Workspace.\

circle-exclamation

Static key (did:key method) cannot be used for the senders DID. Please use other available methods (e.g. did:cheqd). Recipient DID from the holder wallet will be a did:key.

The message script:

const axios = require("axios").default;
const API_KEY = ;//Your Truvera API key// 
const API_URL = "https://api-testnet.truvera.io";//for production https://api.truvera.io
const WALLET_DID = ;//Holders wallet DID//

const apiClient = axios.create({
  baseURL: API_URL,
  headers: {
    "Content-Type": "application/json",
    "User-Agent": "insomnia/9.3.2",
    Authorization: `Bearer ${API_KEY}`,
  },
});

async function sendYesNoMessage() {
  const payload = {
    type: "text",
    payload: {
      senderName: , //Name of the message sender DID//
      senderDid: , //Message sender DID//
      senderLogo: , //Logo of the message sender DID//
      title: "Are you currently speaking with our customer support team?",
      question:
        "This confirms you initiated the call and helps prevent fraud. Your personal information will not be shared.",
      yesText: "Yes",
      noText: "No",
      expirationDate: new Date(Date.now() + 1000 * 60 * 60 * 24).toISOString(),
      messageId: 'Internal-message-1234'//add a message ID to track the message
    },
    type: "https://schema.truvera.io/yes-no-payload-V1.json",
    senderDid: ,//the message sender DID//
    algorithm: "ECDH-1PU+A256KW",
    recipientDids: [WALLET_DID],
  };

  const { data: encryptedMessage } = await apiClient.post(
    "/messaging/encrypt",
    payload
  );
  console.log("Message encrypted successfully:", encryptedMessage);

  const sendPayload = {
    to: WALLET_DID,
    message: encryptedMessage.jwe,
  };

  const { data: sentMessage } = await apiClient.post(
    "/messaging/send",
    sendPayload
  );
  console.log("Message sent successfully:", sentMessage);
}


sendYesNoMessage();

hashtag
Response payload from the wallet

hashtag
Response notification and retrieval

Configure a webhook via the API or the Truvera Workspace to listen to didcomm_message_received event.

You can also get all the received messages using the API.

hashtag
List DIDComm messages

get
/messaging/messages

Retrieve a list of DIDComm messages for the authenticated user. Messages are returned in reverse chronological order (newest first).

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Query parameters
offsetinteger · int32Optional

How many items to offset by for pagination

Default: 0
limitinteger · int32 · min: 1 · max: 64Optional

How many items to return at one time (max 64)

Default: 64
tostring · min: 32Optional

DID as fully qualified, typically. did:cheqd:

Example: did:cheqd:testnet:ac2b9027-ec1a-4ee2-aad1-1e316e7d6f59
messageTypestringOptional

Filter messages by type (e.g., 'https://didcomm.org/basicmessage/2.0/basic-message')

Responses
chevron-right
200

A paged array of DIDComm messages

application/json
get
/messaging/messages

To get the message content make an API call to retrieve the full response.

hashtag
Get a specific DIDComm message

get
/messaging/messages/{messageId}

Retrieve a specific DIDComm message by its ID. Only messages owned by the authenticated user can be retrieved.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
messageIdstringRequired

The unique identifier of the message

Example: msg_1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdefPattern: ^[a-f0-9]{64}$
Responses
chevron-right
200

The requested DIDComm message

application/json
get
/messaging/messages/{messageId}
PreviousTeamsNextMessaging API calls

Last updated

Was this helpful?