​

Hilt docs

Hilt Pay is payment-to-access infrastructure for stablecoin commerce. 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 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. The product stays simple:

• merchants shape and run offers from the dashboard
• developers and agents automate paid access from the API, SDKs, Postman, OpenAPI, and CLI
• buyers complete payment in Hilt checkout and land in the right destination afterwards

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

​

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
• run the agentic payments loop with POST /v1/access/entitlements/check as the access decision
• 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 Pay is payment-to-access infrastructure for stablecoin commerce. Workspace serves merchants from a dashboard; API serves developers and agents through setup intents, payment sessions, receipts, entitlements, webhooks, SDKs, and docs.

​

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.