​
Hilt docs

Hilt connects simple Solana payment products with a full payment-to-access layer for developers, agents, and merchants. It turns wallet payment into operational business state: payment session, proof, receipt, entitlement or member status, webhook trail, support context, analytics, and audit history. Hilt stays zero-custody and does not act as merchant of record. Hilt PayMe gives an X-verified identity a wallet-verified receiving link and QR. The link works on its own, a compatible AI client can optionally prepare and track wallet-approved SOL or Solana USDC payments through the PayMe MCP connector, and Wallet Security can protect future receiving-wallet changes. Hilt Direct Checkout is the no-account builder for a quick SOL, USDC, or single merchant-selected Solana token checkout with a simple post-payment unlock. Hilt Pay Workspace gives merchants a dashboard for hosted checkout, access, memberships, gated links, downloads, WooCommerce, receipts, support, analytics, webhooks, and recurring offers on Solana USDC. Hilt Pay API gives developers and agents the payment session, x402 protected-resource protocol flow, receipt, entitlement, webhook, support, and audit surface for paid APIs, AI tools, bots, datasets, private products, and agentic payment flows. Choose the surface that matches the job:
  • people share a PayMe link or QR to receive payment
  • creators and token communities build a Direct Checkout without an account
  • merchants shape and run durable offers from Workspace
  • developers and agents automate paid access from the API, SDKs, Postman, OpenAPI, and CLI
  • buyers always review and approve payment from their own wallet
API, CLI, and docs are available across every Hilt plan. Higher plans mainly change the economics, support level, and operating comfort once real volume is flowing.

​
Start in the right place

​
PayMe

Use Hilt PayMe when you want a verified personal receiving link, QR code, or an optional natural-language payment connector for a compatible AI client. Enable PayMe Wallet Security while you still control the active receiving wallet.

​
Direct Checkout

Use Direct Checkout when you want to create a checkout link without a Hilt account for SOL, USDC, or one supported merchant-selected Solana token and a simple post-payment unlock.

​
Merchants

Use the merchant guides if you want to:
  • launch your first template
  • set checkout branding
  • choose payout and access destinations
  • understand Payments, Members, Receipts, Support, and Billing
Go to Merchant quickstart.

​
Developers

Use the developer guides if you want to:
  • create one product from code
  • start from Agent Bootstrap and setup intents
  • protect an API or private product with x402 HTTP 402 requirements
  • use POST /v1/access/entitlements/check for durable access, or atomic POST /v1/access/entitlements/consume as the authority for each metered request
  • wire a webhook endpoint
  • test Hilt Pay API in sandbox
  • plan an optional low-value live settlement check
  • then grow into receipts, memberships, support, CLI, and broader automation
If you want one working integration path first, go to Developer quickstart. If an agent is setting up a paid API, go to Agent setup. If you want the broader model and route map first, go to Developer overview.

​
Fastest path by role

​
One product language rule

The dashboard calls the commercial object a template. The API and CLI call that same object a product. They are the same offer. The naming only changes with the surface you are using.

​
How Hilt flows work

Most successful Hilt flows look like this:
  1. a merchant publishes a clear template
  2. the buyer opens the hosted checkout
  3. the buyer confirms any required identity and pays
  4. Hilt records the payment and proof trail
  5. the merchant follows the outcome through Payments, Members, Receipts, and Support
That keeps checkout, access, receipts, and support tied together after payment.

​
Common questions

​
What is Hilt?

Hilt provides PayMe for verified personal receiving links, Direct Checkout for quick no-account checkout links, Hilt Pay API for developers and agents, and Hilt Pay Workspace for dashboard-led merchant operations.

​
Where should a merchant start?

Start with Merchant quickstart, launch one template, validate the buyer flow, then verify Payments, Members, Receipts, and Support.

​
Where should a developer start?

Start with Developer quickstart if you want one working API, webhook, sandbox, and live-payment path. Use Agent setup if an agent is configuring Hilt Pay API for a paid endpoint or product.