​

Hilt Direct Checkout

Hilt Direct Checkout is a public builder for a fast Solana checkout link. No Hilt account or monthly plan is required. Choose native SOL, the USDC preset, or one supported Solana token mint. Set the amount, add the result the buyer should receive, sign the setup with the payout wallet, and share the generated link.

​

Create a checkout

1. Open pay.hilt.so.
2. Select Use SOL, Use USDC, or paste one Solana token contract address.
3. Set the amount in token units, USD, or SOL where supported.
4. Add a title and choose what the buyer unlocks after payment.
5. Connect the merchant payout wallet.
6. Review token details and any declared transfer tax.
7. Sign the setup message and create the checkout link.
8. Copy, open, or embed the checkout.

The setup signature proves that the wallet owner approved the checkout configuration. It does not move funds.

​

What you can deliver

Direct Checkout supports lightweight post-payment outcomes:

• link unlock
• file download URL
• Telegram invite
• Discord invite
• booking link
• license or code reveal
• text or password reveal
• API or webhook handoff URL
• donation or support message

For file delivery, the merchant supplies the file URL. Direct Checkout does not store merchant files. Use Hilt Pay Workspace or Hilt Pay API when you need durable memberships, subscriptions, entitlements, webhooks, analytics, or a broader support record.

​

Buyer payment flow

The buyer opens the generated link, connects a compatible Solana wallet, reviews the asset, recipient amount, Hilt fee, and any token terms, then approves the transaction. Hilt restricts the transaction to the expected payment programs, signers, and writable accounts, then simulates the exact balance changes before wallet approval. After submission, Hilt matches the confirmed on-chain transaction to the transaction it checked before displaying the receipt and configured unlock. Hilt is zero-custody. The buyer signs from their wallet, and payment settles through the buyer-approved Solana transaction to the configured merchant payout and Hilt fee destinations.

​

Token checks and transfer taxes

Native SOL does not have a token transfer tax. For token mints, Hilt checks the token program, mint and token-account data, decimals, freeze authority, metadata, and Token-2022 extensions. Standard Token-2022 transfer fees are supported when Hilt can calculate and verify the exact fee. Direct Checkout blocks unknown or unsupported programmable transfer behaviour. This includes custom transfer hooks, permanent delegates, unexpected programs or signers, additional writable accounts, authority-changing instructions, and simulated balance changes outside the displayed payment. Token-2022 transfer fees can be read from mint configuration. Other token programs may implement transfer behaviour that is not represented as a standard on-chain percentage. The merchant must accurately declare a known token tax when the builder asks for it. The checkout grosses up supported taxed-token payments so the merchant receives the configured amount and Hilt receives its flat 2% fee. Token configuration is checked again for each payment. If Hilt cannot inspect, prepare, simulate, and verify the exact transaction, the checkout blocks rather than guessing or asking the buyer to make a second payment.

​

Embed a checkout

After creating a checkout, select the embed option to get the short Hilt embed snippet. The generated button opens the hosted checkout, so wallet approval and payment confirmation remain on Hilt’s checkout surface.

​

Direct Checkout boundaries

Direct Checkout is intentionally lightweight:

• one checkout uses one selected asset configuration
• it provides a transaction receipt and simple unlock
• it does not replace Workspace merchant records or Hilt Pay API entitlements
• it is not a native subscription or x402 product
• it does not guarantee that every Solana token can be supported

​

Machine-readable discovery

• Short LLM summary
• Full LLM context
• Agent pack
• Agent manifest
• Sitemap
• Setup video