Skip to main content

Glossary

This page keeps the app, API, CLI, and docs talking about the same product.

Template​

The merchant-facing word used in the dashboard for a hosted checkout flow.

In the API and CLI, the same object is called a product.

Product​

The API and CLI word for the merchant object that defines:

  • the offer
  • the price
  • the payout wallet
  • the delivery type
  • the membership rules

In the dashboard, this is usually called a template.

Workspace​

The merchant account surface inside Hilt.

It includes:

  • billing plan
  • branding defaults
  • checkout defaults
  • support history
  • products, members, receipts, and keys

Checkout session​

The buyer-side payment session created when someone starts checkout.

It has its own:

  • payment_id
  • expiry
  • expected amount
  • fee split
  • identity requirements

Payment​

The on-chain transaction attempt tied to a checkout session.

It moves through states like:

  • PENDING_SIGNATURE
  • PENDING_CONFIRMATION
  • CONFIRMED
  • FAILED

Buyer handoff​

A signed link or token that pre-fills and locks the buyer identity before checkout loads.

This is usually created by:

  • a Telegram bot
  • Discord OAuth
  • a merchant app
  • a support flow

Identity handshake​

The wallet-signing step that proves a wallet is paying for a specific buyer identity.

Examples:

  • Telegram user ID
  • Discord user ID
  • merchant-defined customer reference

Delivery​

The post-payment handoff to the buyer.

Examples:

  • Telegram invite
  • Discord role or server flow
  • redirect URL
  • download
  • custom external workflow

Membership​

The merchant record created when a payment activates recurring or gated access.

It holds:

  • identity
  • current access state
  • renewal timing
  • delivery state
  • notes and lifecycle history

Receipt​

Hilt’s signed proof record for a payment.

It is separate from the wallet transaction itself and is designed to be:

  • shareable
  • verifiable
  • merchant-readable
  • suitable for support and audit trails

Billing​

Hilt’s own SaaS subscription relationship with the merchant.

This is not the same thing as the buyer’s on-chain checkout.

Hilt billing uses Stripe for:

  • Hilt plan checkout
  • invoicing
  • billing portal access

Live vs sandbox​

Hilt is currently live-first.

That means:

  • local and staging are used for shaping flows
  • tiny-value live payments are the safest way to prove checkout behavior
  • Stripe still has a true test/live split for Hilt’s own billing