​

Dashboard

The dashboard is the merchant operating surface for Hilt. It is where a merchant:

• shapes the offer
• launches the hosted checkout link
• watches payments settle
• verifies access outcomes
• answers buyer exceptions

​

The daily operating loop

Most merchants move through the dashboard in this order:

1. complete the Get Started wizard or set the workspace defaults
2. build or update one template
3. publish the checkout link
4. watch payments confirm
5. verify the buyer appeared in Members or Receipts
6. use Support only when the flow needs a human follow-up

​

Get Started

Get Started is the guided launch path for a new merchant workspace. Use it when you want Hilt to walk through:

• payout wallet setup
• checkout details
• first template creation
• launch path selection
• channel-specific instructions for link-only, embed, WooCommerce, Telegram, Discord, redirect, download, or custom handoff flows

The wizard uses the same dashboard, product, and checkout rails as the rest of Hilt. It is not a separate checkout system.

​

Overview

Overview is the fastest answer to:

• how many templates are live
• how many paying members are active right now
• what has been earned so far
• what needs attention today

Use it as your top-of-day snapshot. Use the deeper pages when you need the actual ledger.

​

Analytics

Analytics is the merchant operating read for:

• hosted checkout opens
• payment session starts
• confirmed payments
• revenue by day
• date-range filtering
• net take-home and Hilt fees by product
• traffic sources and template performance
• renewals due soon
• delivery-failed rate
• support load per product

Use it when the merchant question is not “did this one buyer pay?” but “which template is leaking, which renewal cohort needs attention, and where is support drag building up?” It is the right page for:

• reading the open -> connect -> confirmed funnel
• clicking a day to inspect what happened in that period
• spotting products with traffic but weak payment completion
• comparing take-home across templates
• seeing which products have delivery failures or support backlog
• deciding which renewal cohort to handle first

​

Templates

Templates are where the merchant defines the offer:

• title and description
• price
• renewal behavior
• payout wallet
• success destination
• checkout presentation

If the commercial promise is unclear, fix it here before sending traffic.

​

Payments

Payments is the transaction ledger. Use it to answer:

• did a buyer actually pay
• which template was used
• what asset was used
• when the payment confirmed
• what the next click should be

​

Members

Members is the access workspace. Use it to:

• confirm access is active
• search by handle, wallet, or transaction
• update display details
• add merchant notes
• gift extra access
• retry the access handoff when needed

​

Receipts

Receipts are the proof layer. Use them when:

• a buyer wants proof of payment
• support needs a verification trail
• you want the public proof link for a confirmed payment

​

Support

Support keeps buyer issues attached to the payment trail instead of scattered across inboxes and chat logs. Use it when the normal path has fallen out of line and you need a durable conversation around the same purchase.

​

Billing

Billing is for the merchant’s own Hilt plan:

• plan status
• renewal date
• invoice history
• payment details
• plan changes

​

Settings

Settings is where the merchant shapes the workspace defaults that new templates inherit:

• display and brand settings
• payout defaults
• support and redirect defaults
• checkout branding
• account access details

Getting Settings right first makes every new template easier to launch cleanly.

​

Common questions

​

What is the Hilt dashboard for?

The dashboard is where merchants launch templates, inspect payments, manage members, open receipts, handle support issues, review billing, and set workspace defaults.

​

Which dashboard page should I check after a sale?

Start with Payments to confirm the transaction, Members to confirm access, Receipts for proof, and Support if the buyer needs human follow-up.

​

What should I configure before creating templates?

Set checkout branding, payout defaults, support URL, redirect defaults, and access settings first so every template starts from a clean workspace baseline.