Email Template Tags and Links

Knowledge Base > Members > Email Template Tags and Links

This document provides a reference guide to the dynamic tags and link structures used within email templates. These tags automatically populate with system‑generated values, ensuring that each email contains accurate, personalized information for the recipient. By combining tags with predefined URL patterns, users can access payment screens, invoice details, and account settings in a secure and streamlined way.

Payment Screen Link

Tag: [WebsiteURL]/pay

Purpose:Directs the recipient to the secure payment page.

  • Opens the payment screen.
  • Requires login credentials.
  • Enforces two‑factor authentication (2FA).
  • Allows entry of credit card details to complete payment.

Include in payment reminder or renewal emails where authentication is required for security.

Direct Payment Link

Tag: [WebsiteURL]/paid/[PaID]

Purpose: Provides a simplified payment link tied to a unique Payment ID

Opens a page that does not require login.

Displays limited information:

  • Outstanding balance
  • Credit card payment slot
  • User’s first initial and last name (for verification)

Offers convenience while exposing minimal personal data

Use in quick payment reminders where ease of access is prioritized.

Invoice List Link

Tag: [WebsiteURL]/usersettings?displayedTable=MyInvoices

Purpose: Takes the recipient directly to their invoice list.

  • Redirects to the account settings page.
  • Automatically displays the MyInvoices table.
  • Provides a consolidated view of all invoices.

Include in billing emails where the recipient needs to review multiple invoices.

Invoice Details Tag

Tag: [InvoiceDetails]

Purpose: Expands to show detailed invoice information.

When sent from the Invoice Screen, it includes:

  • A link to download the invoice
  • The invoice balance
  • The invoice number

Ensures recipients can access and verify billing details directly.

Use in invoice notification emails to provide clarity and transparency

Tags [WebsiteURL] and [PaID] are system‑recognized and always resolve correctly.

Sensitive actions (like payments) require authentication, while limited information can be shown without login for convenience.