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.Hilt Pay API
The developer and agent-facing Hilt surface. Hilt Pay API lets a backend or AI agent create products, configure setup state, create payment sessions, return x402 payment requirements, verify payments, issue receipts, check entitlements, and receive webhooks without requiring the merchant to operate from the dashboard for every action.Agent Bootstrap
The owner-approved setup path for AI agents and developer tools. Agent Bootstrap lets an agent discover Hilt, create a setup intent, propose the app/product/webhook/rail configuration, run sandbox checks, and then ask the owner to approve live keys, billing, payout wallets, or other sensitive changes.Agentic payments
The pattern where software discovers a paid resource, receives a machine-readable payment requirement, completes payment, retries the request, and receives access only after the payment-to-access system says access is active. For Hilt Pay API, agentic payments usually mean:- x402 as the HTTP
402 Payment Requiredprotocol shape - Solana USDC as the current public live settlement rail
- Hilt as the operating layer for sessions, receipts, entitlements, webhooks, support context, and audit history
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
Payment session
The API object that represents a specific buyer payment attempt. For Hilt Pay API, a payment session can power a hosted checkout handoff or an agent-first protected-resource flow where the merchant backend returns HTTP402 Payment Required.
x402
The HTTP payment protocol shape Hilt uses for protected-resource flows. In Hilt Pay API, x402 describes the402 Payment Required response and payment requirement. The requirement includes the settlement details Hilt needs to verify payment, starting with solana_usdc as the current public live rail.
x402 is not a blockchain, token, wallet, or settlement rail.
Settlement rail
The chain/token path used to settle the payment. The first public Hilt Pay API settlement rail issolana_usdc. Additional settlement options, such as Base USDC, selected EVM USDC chains, and USDT, will have separate public docs when they are available.
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.Common questions
Why does Hilt use both template and product?
Merchants see templates in the dashboard. Developers see products in the API and CLI. They refer to the same commercial offer.What is the most important object after checkout?
The payment is the anchor, andpayment_id is the id most integrations should store. It connects checkout, membership, receipt, webhook, and support records.
What should an agent store?
Store the Hiltproduct_id, payment_session_id, receipt_id, entitlement_id, and relevant external customer id. Do not store private keys, raw provider secrets, or full webhook signing secrets.