​

Glossary

​

Template

The dashboard word for a merchant offer. A template is where the merchant defines the commercial promise:

• what the buyer gets
• what the buyer pays
• what happens after payment

​

Product

The API and CLI word for the same object the dashboard calls a template. If a developer automates Hilt from a backend, they are usually working with products that map directly to dashboard templates.

​

Checkout

The hosted buyer payment surface on Hilt. This is where the buyer:

• reads the offer
• confirms any required identity
• connects a wallet
• completes payment

​

Payment

The recorded buyer transaction state as Hilt tracks it. This is the commercial event a merchant uses to answer:

• did the buyer pay
• which asset was used
• when it confirmed

​

Membership

The active or historical access record tied to a payment trail. Memberships matter when the offer creates or extends buyer access over time.

​

Receipt

The proof and verification record tied to a confirmed payment. Receipts are the clean answer when a merchant or buyer needs a shareable proof trail.

​

Support ticket

The merchant-side conversation trail for buyer issues that need human follow-up. Support tickets keep the conversation tied to the same payment, member, and receipt context.

​

Hilt plan

The merchant’s own Hilt subscription. This belongs to the merchant workspace and is managed from the Billing page in the dashboard.