Use QCDS Email Template Tokens

QCDS email-template tokens are placeholders such as {{request.title}} that are replaced with transaction-specific values when a message is rendered. The Email Templates editor exposes the supported token set as clickable buttons so you can insert the exact syntax without retyping it.

Recipient and Sender Tokens

  • {{recipient.name}} — current recipient name.
  • {{recipient.email}} — current recipient email address.
  • {{sender.name}} — frozen/configured sender display name.
  • {{sender.email}} — sender/reply-to email address used by the transaction.

Request and Site Tokens

  • {{request.title}} — Request title.
  • {{request.number}} — QCDS Request number.
  • {{request.link}} — secure signer link when the message type supplies one.
  • {{request.expires}} — formatted Request/link expiration when applicable.
  • {{request.reason}} — cancellation or other event reason when supplied.
  • {{site.name}} — Joomla site name.

Identity Verification Tokens

The editor also exposes Identity Verification placeholders:

  • {{verification.status}}
  • {{verification.signer_name}}
  • {{verification.verified_name}}
  • {{verification.document_type}}
  • {{verification.country}}
  • {{verification.confirmed_at}}
  • {{verification.reference}}
  • {{verification.provider}}

These values are populated by Identity Verification events. Ordinary invitation, reminder, cancellation, completion, or resend paths do not automatically manufacture Identity Verification values, so use verification tokens where the related event actually supplies them.

Insert Tokens Without Changing Their Syntax

In the Email Template editor, click a token button to insert it at the cursor in the active Subject or message editor. Keep both braces and the exact token name intact. QCDS performs literal runtime substitution; an unknown or mistyped {{...}} placeholder is not silently guessed.

HTML Token Values Are Escaped

When QCDS renders HTML, runtime token values are HTML-escaped before substitution. This lets a Custom HTML template control its markup without allowing a Contact name, Request title, or other runtime value to inject new HTML.

Use Preview HTML to spot unresolved placeholders visually. Send Test performs a stricter check and refuses to send when unresolved token syntax remains in the rendered Subject or body.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.