​
Hilt PayMe

Hilt PayMe turns an X identity into a simple Solana payment destination. Connect X, bind the receiving wallet you control, then share one pay.hilt.so/me link or QR code. The receiving link works without an AI client. A payer opens the link, connects Phantom, Solflare, Backpack, Trust Wallet, or SafePal on mobile, or a supported browser wallet such as Jupiter on desktop, reviews the exact payment, and approves it. The payer does not need a PayMe account.
Creating and receiving through PayMe is free. The sender sees and pays Hilt’s flat 2% fee before wallet approval.

​
Create your PayMe

  1. Open pay.hilt.so/me.
  2. Continue with X to verify the identity behind the handle.
  3. Connect the Solana wallet where you want to receive payments.
  4. Sign the wallet-binding message. This proves control of the receiving wallet; it does not move funds.
  5. Share your PayMe link or QR code.
Your PayMe page keeps two facts together:
  • the X account controls the public handle
  • the receiving wallet controls its own wallet binding
Hilt never receives a seed phrase or private key and cannot sign a payment for the payer.

​
Protect future wallet changes

After your link is active, open Wallet Security and enable a standard Authenticator app. Initial enrollment requires a signature from the current receiving wallet. Hilt then gives you single-use recovery codes to store safely. Once Wallet Security is enabled, changing the destination for future PayMe payments requires a current Authenticator code or unused recovery code plus a signature from the new receiving wallet. The old wallet does not need to sign the later change, which provides a recovery path if it becomes inaccessible. If the current wallet is already inaccessible and Wallet Security was never enabled, self-service replacement is blocked. Enable protection while you still control the active receiving wallet. Read the PayMe Wallet Security guide for setup, wallet-browser handoff, recovery scenarios, and troubleshooting.

​
Receive a payment

The payer:
  1. opens your PayMe link or scans the QR code
  2. selects an available payment asset and amount
  3. connects the wallet they want to pay from
  4. reviews the recipient, amount, asset, and Hilt fee
  5. approves the transaction in that wallet
The receiving profile belongs to the recipient. The payer does not sign in with X, create a PayMe profile, or use the recipient’s wallet.

​
Share without AI

You can use PayMe as a normal payment link:
  • put it in a bio or profile
  • send it in a message
  • show the QR code in person or on a screen
  • add it to an invoice, proposal, or support page
The MCP connector is optional. It adds natural-language payment preparation and activity lookup for compatible AI clients; it is not required to create, share, or pay a PayMe link.

​
Pay several people with one approval

The Pay multiple people flow lets a payer send native SOL to between two and five verified PayMe recipients in one atomic Solana transaction. The wallet approves once; all recipient transfers and Hilt’s flat 2% sender fee either finalize together or do not execute. PayMe profile URLs publish standard Solana Action discovery. In a compatible Action-aware client, the normal /me/@handle URL can render as an interactive Blink for a native SOL payment. In other clients, the same URL opens the normal PayMe page. Read Pay multiple people and PayMe Blinks for the exact flow and boundaries.

​
Connect a compatible AI client

The PayMe MCP connector lets a compatible AI client resolve an active PayMe handle, prepare exact SOL or Solana USDC payment terms, create self-shared payment links, and read payment activity. The AI never signs or submits the wallet transaction. It returns a Hilt approval URL, and the payer chooses a wallet and approves the payment there. Read the PayMe MCP connector guide for setup, tools, OAuth scopes, examples, and security boundaries.

​
Current asset scope

The MCP connector’s exact send-payment and payment-link tools support:
  • native SOL
  • Solana USDC
The PayMe page may display supported assets available to the connected payer wallet. A natural-language send command does not advertise a custom token unless Hilt can bind and validate the exact mint terms.

​
PayMe and other Hilt products

PayMe and Direct Checkout are public payment surfaces. They are separate from Hilt Pay API /v1/access and do not create API entitlements or x402 metered access.