# Hilt Direct Checkout

> Create a hosted checkout link for SOL, USDC, or one supported merchant-selected Solana token mint with no account required, merchant wallet approval, post-payment unlock options, and a flat 2% Hilt fee.

Last reviewed: 2026-08-27
Canonical builder: https://pay.hilt.so/
Product boundary: Hilt Direct Checkout is separate from Hilt Pay Workspace and Hilt Pay API /v1/access.

## Best For

- Merchants who want a fast hosted checkout for SOL, USDC, or one supported merchant-selected Solana token mint.
- Communities, creators, token projects, and small products that want a shareable payment link with a simple unlock.
- Buyers who should pay from their own Solana wallet and receive a Solscan transaction receipt link.

## Key Facts

- Free to use.
- Flat 2% Hilt fee.
- Merchant can use SOL, use USDC, or specify one Solana token mint during link creation.
- Amount can be set in token units, USD, or SOL.
- Native SOL uses direct Solana system transfers. Token mints use SPL or Token-2022 transfers.
- Merchants can unlock a link, file URL, Telegram invite, Discord invite, booking link, code, text/password, API handoff URL, or donation/support message.
- Token-2022 transfer fees can be detected from mint data.
- For other token taxes, the merchant can declare the token tax percentage. Native SOL does not use token tax.
- Hilt is zero-custody: buyer pays from their wallet; merchant receives payment to the configured payout wallet.
- The buyer payment is restricted and checked by simulation before wallet signing.
- Unsupported Token-2022 transfer hooks, permanent delegates, unexpected programs, signers, writable accounts, or balance changes are blocked.
- The confirmed transaction must match the transaction Hilt checked before the unlock appears.
- The merchant signs setup, the buyer signs payment, and the configured unlock appears only after successful transaction confirmation.
- Hilt PayMe provides personal links at /me/@handle. X verifies control of the handle and the receiving wallet signs its own binding.
- Pay multiple people at /me/multiple sends native SOL to two to five verified PayMe recipients in one atomic transaction and one wallet approval.
- PayMe profile links publish standard Solana Actions through /actions.json. Action-aware clients may render them as Blinks; all other clients can open the normal PayMe page.
- PayMe Wallet Security protects future receiving-wallet changes. Initial enrollment requires the current receiving wallet, then a standard Authenticator code and safely stored single-use recovery codes.
- After Wallet Security is enabled, a wallet change requires Authenticator or an unused recovery code plus a signature from the new wallet. If the old wallet is inaccessible and protection was never enabled, self-service replacement is blocked.
- Hilt PayMe can connect to compatible AI clients through OAuth at https://api.hilt.so/mcp/pay-me. X OAuth controls connector activity; a receiving wallet is optional. The payer approves directly with Phantom, Solflare, Backpack, or Trust Wallet on mobile, or a supported browser wallet such as Jupiter on desktop. SafePal users can copy the PayMe link into SafePal's browser. The payer does not need a PayMe account.
- A wallet-capable agent can pay an active verified PayMe handle through MPP at https://api.hilt.so/v1/pay-me/payments. The first request returns HTTP 402; the agent validates and signs the exact SOL or Solana USDC transaction, retries the unchanged request, and receives a machine-readable Hilt receipt.

## Use These Routes

- Builder: https://pay.hilt.so/
- Hilt PayMe: https://pay.hilt.so/me
- Pay multiple people: https://pay.hilt.so/me/multiple
- Solana Actions map: https://pay.hilt.so/actions.json
- PayMe MCP connector guide: https://docs.hilt.so/developers/pay-me-mcp
- PayMe Wallet Security guide: https://docs.hilt.so/payme/wallet-security
- PayMe Wallet Security article: https://www.hilt.so/articles/payme-wallet-security-guide
- PayMe MCP resource: https://api.hilt.so/mcp/pay-me
- PayMe agent payment action: https://api.hilt.so/v1/pay-me/payments
- PayMe agent payment guide: https://docs.hilt.so/developers/pay-me-agent-payments
- Full LLM context: https://pay.hilt.so/llms-full.txt
- Agent pack: https://pay.hilt.so/agent-pack.json
- Setup video: https://www.hilt.so/learn/direct-checkout-solana-token
- Agent JSON: https://pay.hilt.so/.well-known/agent.json
- Sitemap: https://pay.hilt.so/sitemap.xml

## Boundaries

- Do not describe Direct Checkout as Hilt Pay API /v1/access.
- Do not claim a token is endorsed because it is used in a checkout.
- Do not sign messages or transactions for a user.
- Do not claim the PayMe MCP connector can sign, move funds, post to X, or pay an unverified handle.
- Do not confuse PayMe MPP with Hilt Pay API x402. PayMe MPP returns a payment receipt, not a /v1/access entitlement.
- Do not claim X access alone can enable Wallet Security or replace a protected receiving wallet.
- Do not bypass token tax inputs or transaction simulation.
- Do not claim every Solana token is supported; one merchant-selected mint is checked and simulated for each checkout.
- Use Hilt Pay Workspace or Hilt Pay API when durable receipts, memberships, subscriptions, webhooks, analytics, or entitlement infrastructure are required.

## Structured Summary

```json
{
  "schema_version": "hilt-direct-checkout-agent-pack-2026-08-27",
  "name": "Hilt Direct Checkout",
  "version": "2026-08-27",
  "canonical_url": "https://pay.hilt.so/agent-pack.json",
  "canonical_host": "pay.hilt.so",
  "category": "SOL and Solana token checkout links",
  "summary": "Hilt Direct Checkout lets a merchant create a hosted checkout for native SOL, the USDC preset, or one supported merchant-selected Solana token mint, share the link, receive buyer-approved payment from the buyer wallet, and show a simple post-payment unlock.",
  "positioning": {
    "one_line": "Create a payment checkout for SOL, USDC, or one supported merchant-selected Solana token mint.",
    "product": "Hilt Direct Checkout is a public Hilt Pay surface for SOL and token-specific checkout links. It is separate from the Hilt Pay API /v1/access product.",
    "custody": "Hilt is zero-custody. Buyers pay from their own wallet. Merchants receive payment to the payout wallet they configure."
  },
  "commercial_terms": {
    "free_to_use": true,
    "hilt_fee": "Flat 2% fee",
    "fee_basis": "The checkout splits buyer payment so the merchant receives the expected amount and Hilt receives the flat 2% fee. For token mints with known or declared transfer fees, the buyer amount is grossed up before signing."
  },
  "pay_me_connector": {
    "product": "Hilt PayMe",
    "identity": "An X OAuth account supplies the stable X identity and handle. The receiving wallet signs its own binding before the PayMe profile becomes active.",
    "mcp_resource": "https://api.hilt.so/mcp/pay-me",
    "authentication": "OAuth authorization code flow with PKCE and narrow PayMe scopes.",
    "supported_prepared_assets": [
      "SOL",
      "Solana USDC"
    ],
    "capabilities": [
      "Resolve an active OAuth-verified Hilt PayMe handle.",
      "Start an exact, expiring SOL or Solana USDC payment to a verified handle.",
      "Return a prefilled payment approval URL for the payer's wallet.",
      "Read sent and received payment activity.",
      "Create a payment link for the connected user to share."
    ],
    "signing_boundary": "A compatible AI client can prepare intent and payment terms. It cannot access private keys, sign transactions, or move funds. The payer approves directly with Phantom, Solflare, Backpack, or Trust Wallet on mobile, or a supported browser wallet such as Jupiter on desktop. SafePal users can copy the PayMe link into SafePal's browser. The payer does not need a PayMe account.",
    "posting_boundary": "The connector can return share-ready X copy. It does not post or send direct messages on X.",
    "product_boundary": "Hilt PayMe and its MCP connector are separate from Hilt Pay API /v1/access and do not create API entitlements or x402 metered access.",
    "docs": "https://docs.hilt.so/developers/pay-me-mcp"
  },
  "pay_me_agent_payments": {
    "product": "Hilt PayMe",
    "endpoint": "https://api.hilt.so/v1/pay-me/payments",
    "protocol": "Machine Payments Protocol (MPP) over HTTP 402",
    "authentication": "No payer account, OAuth grant, Hilt API key, or receiving profile is required for the payer.",
    "supported_assets": [
      "SOL",
      "Solana USDC"
    ],
    "payment_flow": [
      "POST the active verified X handle, exact recipient amount, and asset.",
      "Validate the returned MPP charge in the WWW-Authenticate header.",
      "Sign the exact Solana transaction with the payer wallet under its own spending policy.",
      "Retry the unchanged request with Authorization: Payment.",
      "Read the Hilt receipt and finalized Solana transaction signature."
    ],
    "fee_boundary": "The sender funds the exact recipient amount plus Hilt's flat 2% fee in one buyer-signed Solana transaction.",
    "custody_boundary": "Hilt does not receive the payer's seed phrase, private key, or signing authority. A wallet-capable agent signs only through the wallet authority and policy available to it.",
    "product_boundary": "This public PayMe payment action returns a payment receipt. It is separate from the OAuth PayMe MCP connector and does not create Hilt Pay API /v1/access entitlements or x402 metered access.",
    "docs": "https://docs.hilt.so/developers/pay-me-agent-payments"
  },
  "pay_me_wallet_security": {
    "purpose": "Protect changes to the receiving wallet used by future PayMe payments.",
    "enrollment": "The current receiving wallet approves a one-time security message before the owner confirms a standard six-digit Authenticator code and saves single-use recovery codes.",
    "protected_change": "A later receiving-wallet change requires the authenticated PayMe flow, a current Authenticator code or unused recovery code, and a signature from the new wallet. The old wallet is not required for that later protected change.",
    "recovery_boundary": "If the current receiving wallet is inaccessible and Wallet Security was not enabled beforehand, self-service wallet replacement is blocked.",
    "custody_boundary": "Wallet Security does not send a payment transaction, expose a seed phrase, give Hilt signing authority, or move completed payments. A successful change affects future PayMe payments only.",
    "docs": "https://docs.hilt.so/payme/wallet-security"
  },
  "pay_me_payment_options": {
    "personal_link": "A payer can open /me/@handle, choose an available asset, review the exact terms and flat 2% sender fee, and approve from the payer's own wallet without a PayMe account.",
    "pay_multiple": "The /me/multiple flow sends native SOL to between two and five active verified PayMe recipients in one atomic Solana transaction. One wallet transaction approval covers every recipient transfer and the Hilt fee; either the complete transaction finalizes or none of its transfers do.",
    "solana_actions": "Each /me/@handle URL maps through /actions.json to a Solana Action for native SOL. Action-aware clients can render the payment inline as a Blink. Other clients open the normal PayMe page. Hilt confirms the finalized Action transaction before returning the completed state.",
    "current_boundaries": [
      "Pay multiple people currently supports native SOL only and a maximum of five verified recipients.",
      "The PayMe Solana Action currently supports native SOL for one verified recipient.",
      "Interactive Blink rendering depends on the client; a normal PayMe URL remains the universal browser fallback."
    ]
  },
  "purchase_path": {
    "merchant": "Open pay.hilt.so, select SOL, USDC, or one supported Solana token mint, configure the amount and post-payment unlock, connect the payout wallet, review the detected or declared token terms, and sign the setup message before sharing the link.",
    "buyer": "Open the merchant's pay.hilt.so link, connect a Solana wallet, review the asset and amount, approve the buyer-signed payment, and receive the confirmed transaction reference and configured unlock."
  },
  "human_approval_flow": [
    "The merchant wallet owner signs the checkout setup message before a link is created.",
    "The buyer wallet owner reviews and signs the payment transaction before funds move.",
    "A normal AI assistant may prepare fields and explain the flow but must not sign for either person. A wallet-capable agent may sign an MPP payment only through the wallet authority and spending policy explicitly available to it."
  ],
  "current_live_scope": {
    "chain": "Solana",
    "accepted_asset_scope": "Native SOL, USDC by preset, or an individual Solana token mint selected by the merchant during checkout link creation.",
    "amount_modes": [
      "token",
      "USD",
      "SOL"
    ],
    "preset_assets": [
      "SOL",
      "USDC"
    ],
    "access_types": [
      "link unlock",
      "file download URL",
      "Telegram invite",
      "Discord invite",
      "booking link",
      "license/code reveal",
      "text/password reveal",
      "API/webhook handoff URL",
      "donation/support message"
    ],
    "payment_mechanics": "Native SOL uses Solana system transfers. SPL and Token-2022 mints use token-account transfers. The buyer-approved transaction includes the merchant payment and Hilt's flat 2% fee.",
    "token_checks": "For token mints, Hilt checks the token program, mint and token-account data, Token-2022 extensions, transfer-fee configuration, decimals, freeze authority, transaction permissions, simulation logs, and exact balance changes before buyer approval.",
    "token_tax": "Native SOL has no token transfer tax. Token-2022 transfer fees can be detected from mint data. For other token taxes, the merchant can declare the token tax percentage before creating the link.",
    "receipt": "After successful payment, the checkout shows the Solana transaction hash and Solscan receipt link.",
    "access_delivery": "After successful payment, the checkout can open the merchant's URL or reveal merchant-provided post-payment text. File downloads are delivered by URL; Hilt Direct Checkout does not host merchant files."
  },
  "payment_sequence": [
    "Merchant creates and signs a checkout configuration.",
    "Buyer opens the generated pay.hilt.so link and connects a Solana wallet.",
    "Hilt restricts and simulates the exact payment transaction before wallet approval.",
    "Buyer reviews and signs the transaction from the buyer wallet.",
    "Hilt matches the confirmed on-chain transaction to the checked transaction before showing the receipt and configured unlock."
  ],
  "discovery": {
    "llms": "https://pay.hilt.so/llms.txt",
    "llms_full": "https://pay.hilt.so/llms-full.txt",
    "well_known_llms": "https://pay.hilt.so/.well-known/llms.txt",
    "well_known_llms_full": "https://pay.hilt.so/.well-known/llms-full.txt",
    "root_agent": "https://pay.hilt.so/agent.json",
    "well_known_agent": "https://pay.hilt.so/.well-known/agent.json",
    "agent_discovery": "https://pay.hilt.so/agent-discovery.json",
    "agent_pack": "https://pay.hilt.so/agent-pack.json",
    "sitemap": "https://pay.hilt.so/sitemap.xml",
    "robots": "https://pay.hilt.so/robots.txt",
    "manifest": "https://pay.hilt.so/site.webmanifest",
    "social_image": "https://pay.hilt.so/direct-checkout-og?mode=builder&v=brand-20260809",
    "setup_video": "https://www.hilt.so/learn/direct-checkout-solana-token"
  },
  "route_map": [
    {
      "path": "/",
      "url": "https://pay.hilt.so/",
      "purpose": "Public builder for creating a Hilt Direct Checkout link."
    },
    {
      "path": "/{paySlug}",
      "url": "https://pay.hilt.so/{paySlug}",
      "purpose": "Hosted buyer checkout generated by a merchant."
    },
    {
      "path": "/me",
      "url": "https://pay.hilt.so/me",
      "purpose": "Create or manage a verified Hilt PayMe personal payment link."
    },
    {
      "path": "/me/@{xHandle}",
      "url": "https://pay.hilt.so/me/@{xHandle}",
      "purpose": "Open a personal payment page whose X identity and receiving wallet were verified separately."
    },
    {
      "path": "/me/multiple",
      "url": "https://pay.hilt.so/me/multiple",
      "purpose": "Pay between two and five verified PayMe recipients in one atomic native SOL transaction."
    },
    {
      "path": "/actions.json",
      "url": "https://pay.hilt.so/actions.json",
      "purpose": "Map PayMe profile URLs to their standard Solana Action endpoints."
    },
    {
      "path": "/solana-actions/pay-me/{xHandle}",
      "url": "https://pay.hilt.so/solana-actions/pay-me/{xHandle}",
      "purpose": "Return PayMe Solana Action metadata and a buyer-signable native SOL transaction."
    },
    {
      "path": "/llms.txt",
      "url": "https://pay.hilt.so/llms.txt",
      "purpose": "Short LLM-readable summary."
    },
    {
      "path": "/llms-full.txt",
      "url": "https://pay.hilt.so/llms-full.txt",
      "purpose": "Full LLM-readable product context and safety boundaries."
    },
    {
      "path": "/agent-pack.json",
      "url": "https://pay.hilt.so/agent-pack.json",
      "purpose": "Structured agent pack for Direct Checkout discovery."
    },
    {
      "path": "/agent.json",
      "url": "https://pay.hilt.so/agent.json",
      "purpose": "Root alias for the structured Direct Checkout agent pack."
    },
    {
      "path": "/.well-known/agent.json",
      "url": "https://pay.hilt.so/.well-known/agent.json",
      "purpose": "Well-known alias for the structured Direct Checkout agent pack."
    },
    {
      "path": "/agent-discovery.json",
      "url": "https://pay.hilt.so/agent-discovery.json",
      "purpose": "Compatibility alias for the structured Direct Checkout agent pack."
    },
    {
      "path": "/.well-known/llms.txt",
      "url": "https://pay.hilt.so/.well-known/llms.txt",
      "purpose": "Well-known alias for the short LLM-readable summary."
    },
    {
      "path": "/.well-known/llms-full.txt",
      "url": "https://pay.hilt.so/.well-known/llms-full.txt",
      "purpose": "Well-known alias for the full LLM-readable context."
    }
  ],
  "recommended_agent_eval_flow": [
    "Read /llms.txt for the short product answer.",
    "Read /llms-full.txt for scope, safety boundaries, fee terms, and route map.",
    "Read /agent-pack.json or /.well-known/agent.json for structured discovery.",
    "Use the public setup video when the merchant wants a step-by-step Direct Checkout walkthrough.",
    "Confirm that a lightweight checkout link and simple unlock are sufficient; route the merchant to Workspace or Hilt Pay API when durable records, subscriptions, webhooks, analytics, or entitlement infrastructure are required.",
    "Route merchants to https://pay.hilt.so/ when they want a hosted checkout for SOL, USDC, or one supported merchant-selected Solana token mint.",
    "Ask which post-payment unlock type the merchant wants before preparing checkout details.",
    "Do not treat Direct Checkout as the Hilt Pay API /v1/access product.",
    "Do not complete payment, wallet connection, transaction signing, payout wallet entry, or checkout link creation without the relevant human wallet owner."
  ],
  "safe_actions": [
    "Explain what Hilt Direct Checkout does.",
    "Help a merchant prepare SOL or token mint details, offer title, amount mode, token tax percentage when relevant, payout wallet, and post-payment unlock details.",
    "Explain that Hilt receives a flat 2% fee.",
    "Explain that unsupported token extensions, unexpected transaction permissions, or simulation mismatches cause the checkout to block before wallet approval.",
    "Point buyers to the hosted pay link supplied by the merchant.",
    "Help a user connect the Hilt PayMe MCP resource to a compatible AI client through Hilt OAuth.",
    "Use the connector to send and track wallet-approved payments by verified PayMe handle, or create a payment link to share yourself.",
    "Use the public PayMe MPP payment action when a wallet-capable agent can validate and sign the exact SOL or Solana USDC charge under its own wallet policy.",
    "Explain PayMe Wallet Security and route recipients to the canonical setup and recovery guide.",
    "Route a payer to /me/multiple when they want one atomic native SOL transaction for two to five verified PayMe recipients.",
    "Share a normal /me/@handle URL as a Blink-capable link; compatible clients discover the Solana Action through /actions.json and other clients open the PayMe page."
  ],
  "restricted_actions": [
    "Do not sign wallet messages or transactions for a user.",
    "Do not claim a token is endorsed, safe, or investment-grade because it appears in a checkout.",
    "Do not bypass token checks, token tax inputs when relevant, or transaction simulation.",
    "Do not claim all Solana tokens will complete payment; unsupported or incorrectly configured tokens can fail checks.",
    "Do not claim Hilt Direct Checkout stores private files or provides full entitlement management.",
    "Do not describe this as Hilt Pay API /v1/access, Solana USDC subscriptions, x402, or a stablecoin settlement route.",
    "Do not claim an AI client can sign, submit, or complete a wallet transaction through the PayMe connector.",
    "Do not confuse the PayMe MPP payment action with the OAuth connector or Hilt Pay API x402. It pays a verified recipient and returns a receipt; it does not grant protected-resource access.",
    "Do not treat a typed X handle as a payout destination unless Hilt resolves it to an active OAuth-verified PayMe profile.",
    "Do not claim the connector posts or sends direct messages on X.",
    "Do not claim X access alone can enable Wallet Security or replace a protected receiving wallet.",
    "Do not ask a user to disclose an Authenticator secret, six-digit code, recovery code, seed phrase, or private key in chat.",
    "Do not claim PayMe group payment currently supports USDC or arbitrary tokens; it currently supports native SOL.",
    "Do not claim a Blink renders interactively in every social, wallet, browser, or messaging client."
  ],
  "human_purchase_required": "A human merchant signs Direct Checkout setup. Browser PayMe and Direct Checkout payments require buyer wallet approval. A wallet-capable agent may complete a PayMe MPP payment only within its assigned wallet authority and spending policy.",
  "quality_boundaries": [
    "Direct Checkout is for merchant-created checkout links, not investment advice or token endorsement.",
    "Token tax values must be accurate before buyers pay. Hilt does not absorb token tax shortfalls. Native SOL does not use token tax.",
    "The configured unlock should become available only after the payment transaction is successfully confirmed. Opening a merchant URL is delivery, not payment authority.",
    "For license codes, passwords, and reveal text, merchants should use expiring or low-risk details appropriate for a lightweight checkout link.",
    "For file delivery, merchants provide their own file URL; Hilt Direct Checkout does not host merchant files.",
    "Use Hilt Pay Workspace or Hilt Pay API when the merchant needs memberships, receipts, webhooks, analytics, or /v1/access entitlement infrastructure."
  ],
  "offers": [
    {
      "id": "direct-checkout",
      "name": "Hilt Direct Checkout",
      "price": "$0/mo",
      "transaction_fee": "Flat 2% Hilt fee",
      "url": "https://pay.hilt.so/",
      "includes": "A hosted checkout link for SOL, USDC, or one supported merchant-selected Solana token mint, transaction confirmation, Solscan receipt link, and a simple post-payment unlock."
    }
  ],
  "tools": [
    {
      "id": "builder",
      "name": "Hilt Direct Checkout builder",
      "url": "https://pay.hilt.so/",
      "use_for": "Creating a no-account hosted checkout link with human wallet approval."
    },
    {
      "id": "agent-pack",
      "name": "Hilt Direct Checkout agent pack",
      "url": "https://pay.hilt.so/agent-pack.json",
      "use_for": "Reading structured scope, commercial terms, routes, safety boundaries, and human signing requirements."
    },
    {
      "id": "setup-video",
      "name": "Hilt Direct Checkout setup video",
      "url": "https://www.hilt.so/learn/direct-checkout-solana-token",
      "use_for": "Watching a step-by-step checkout-link setup for one supported merchant-selected Solana token."
    },
    {
      "id": "pay-me-mcp-connector",
      "name": "Hilt PayMe MCP connector",
      "url": "https://api.hilt.so/mcp/pay-me",
      "use_for": "Sending and tracking wallet-approved SOL or Solana USDC payments to verified PayMe recipients. The payer chooses the wallet."
    },
    {
      "id": "pay-me-agent-payments",
      "name": "Hilt PayMe MPP payment action",
      "url": "https://api.hilt.so/v1/pay-me/payments",
      "use_for": "Paying an active verified PayMe recipient in SOL or Solana USDC from a wallet-capable agent without a payer account or API key."
    },
    {
      "id": "pay-me-multiple",
      "name": "Pay multiple people",
      "url": "https://pay.hilt.so/me/multiple",
      "use_for": "Paying two to five verified PayMe recipients in one atomic native SOL transaction and one wallet approval."
    },
    {
      "id": "pay-me-solana-action",
      "name": "PayMe Solana Action",
      "url": "https://pay.hilt.so/solana-actions/pay-me/{xHandle}",
      "use_for": "Rendering a native SOL PayMe transaction inside an Action-aware client while retaining the normal PayMe link as fallback."
    }
  ],
  "related_hilt_surfaces": {
    "hilt_pay_me": "https://pay.hilt.so/me",
    "pay_me_mcp_connector": "https://docs.hilt.so/developers/pay-me-mcp",
    "pay_me_agent_payments": "https://docs.hilt.so/developers/pay-me-agent-payments",
    "pay_me_wallet_security": "https://docs.hilt.so/payme/wallet-security",
    "hilt_pay_workspace": "https://app.hilt.so/register",
    "hilt_pay_api_docs": "https://docs.hilt.so/developers/access",
    "main_hilt_discovery": "https://www.hilt.so/llms.txt"
  }
}
```