​
Pay multiple people and PayMe Blinks

PayMe now gives a payer two additional ways to start a payment. Both preserve the same zero-custody boundary: the payer’s wallet reviews and signs the transaction, funds move directly on Solana, and Hilt records a receipt only after the finalized transaction matches the prepared terms.

​
Pay multiple people

Open pay.hilt.so/me/multiple when you want to send SOL to several verified PayMe recipients at once.
  1. Enter between two and five X handles with active PayMe links.
  2. Enter the SOL amount each recipient should receive.
  3. Connect the wallet that will pay.
  4. Review the recipient total and Hilt fee.
  5. Approve one Solana transaction in the wallet.
The transaction contains one transfer for every recipient and one transfer for Hilt’s flat 2% sender fee. Solana processes those instructions atomically: the complete transaction succeeds or none of its transfers do. Hilt then verifies the payer, memo, instruction order, recipient destinations, exact recipient amounts and exact fee before issuing the group receipt.
Pay multiple people currently supports native SOL only, a maximum of five verified recipients, and one paying wallet. Personal PayMe links continue to support the assets displayed by the payer’s wallet, while the PayMe MCP connector’s exact prepared-payment tools support SOL and Solana USDC.
A Solana Action is a public API that gives a compatible client payment metadata and an unsigned transaction for the user’s wallet to review. A Blink is the interactive presentation of that Action inside an Action-aware wallet, browser extension, bot, social surface or messaging client. Every public pay.hilt.so/me/@handle profile can be discovered through pay.hilt.so/actions.json. A compatible client maps the profile URL to Hilt’s PayMe Action endpoint, asks the payer for a SOL amount and optional note, then requests an unsigned transaction. The payer’s wallet remains the authority:
  • Hilt does not receive a seed phrase or private key.
  • Hilt does not sign or submit the payment for the payer.
  • The recipient receives the amount entered.
  • The sender sees and pays Hilt’s flat 2% fee.
  • Hilt returns a completed Action state only after the finalized transaction passes exact settlement verification.
If a client does not render Blinks, the same shared PayMe URL opens the normal browser payment page. Interactive rendering is a client capability, not a property Hilt can guarantee on every platform.

​
Choosing the right option

PayMe payment links, grouped payments and Blinks are separate from Hilt Pay API /v1/access. They do not create API entitlements or x402 metered access.