Skip to main content

Templates

Templates are the fastest way to launch a Hilt flow without starting from raw API calls.

In the dashboard these are called templates. In the API and CLI, the same merchant objects are exposed as products.

Offer formats​

Telegram​

Best for:

  • paid groups
  • paid channels
  • membership communities
  • recurring access with a Telegram connect step

Discord​

Best for:

  • paid servers
  • role-gated access
  • premium community areas
  • recurring memberships tied to a Discord connect step

Redirect / Download​

Best for:

  • digital products
  • paid links to content
  • download unlocks
  • private site or page access

Custom​

Best for:

  • manual delivery
  • unusual fulfilment flows
  • staged rollout when you want HiltPay checkout but a custom fulfillment step

Common template fields​

Every template starts with:

  • title and description
  • price in SOL or USDC
  • merchant payout wallet
  • delivery method
  • destination name

Membership-oriented templates also include:

  • interval days
  • grace period days
  • optional delivery override or automation target override when one template should behave differently from the workspace default

Checkout branding lives at the workspace level, not inside every template:

  • checkout brand name
  • logo image
  • hero image
  • accent color
  • default success handoff

Templates can still add a per-template cover image when that one offer needs its own visual promise.

For Telegram and Discord flows, the buyer identity is handled in checkout with Connect Telegram or Connect Discord. Merchants do not type buyer identities into the template itself.

For redirect and custom flows, the merchant can still ask for a buyer handle, email, or customer ID when they need that extra record.

How to choose​

Choose Telegram or Discord if access depends on a buyer identity after payment.

Choose Redirect / Download if the payment unlocks a URL or asset without a community membership.

Choose Custom if HiltPay should handle checkout and confirmation, but your team will handle fulfillment differently.

Launch advice​

  • keep the first template narrow
  • make the access promise explicit in the title and description
  • use a dedicated merchant payout wallet
  • use memberships only when you genuinely need identity and renewal state
  • keep the post-payment handoff obvious so buyers know where to go next

Next guides​