Support

X402 payments

XPay is built for USDT micropayments: a seller publishes a priced URL, the buyer gets HTTP 402, pays, and the seller is credited in USDT immediately. Agents should use this for per-call charges (from 0.001 USDT plus the live x402 fee). HeartBix posts an Alephium receipt hash; that is not a second Tether balance. Agent spec: /llms.txt.

Do this in four steps

  1. Log in → Fund → Deposit USDT (any supported chain).
  2. Seller: X402 Endpoint → slug price1, price 0.001 → Create. Copy the pay URL.
  3. Send that URL to the buyer (chat, docs, or your app). XPay does not send it for you.
  4. Buyer opens the URL (HTTP 402), signs, retries with PAYMENT-SIGNATURE. Check X402 transactions for sent / received.
# Buyer discovers the price
curl -i https://xpay.heartbix.com/api/pay/<seller-alph>/price1

# Buyer pays (signature from the 402 / wallet)
curl -i -H "PAYMENT-SIGNATURE: <base64>" \
  https://xpay.heartbix.com/api/pay/<seller-alph>/price1

Seller

The URL is unique because it includes your Alephium address: https://xpay.heartbix.com/api/pay/<your-alph>/price1. Every seller can reuse the same slug. Optional: one-off price with ?price=0.05 and your API key. The buyer still uses the same URL and does not need your key.

Buyer

First GET has no payment header → 402 with amount and payTo. Read the vault nonce (GET /api/hub/x402/intent?from=<buyer-alph>), sign, retry. Success is HTTP 200 with an Alephium txId. Same buyer: wait for 200 before the next pay (nonce +1). Different buyers can pay the same URL at once.

USDT

Deposit and withdraw are real USDT on EVM. You can deposit on one network and withdraw on another; HeartBix routes treasury USDT. Each x402 pay moves XPay USDT and includes a small live transaction fee (ALPH gas in USDT, rounded up). Withdraw to a 0x address has a separate transfer fee; send more than that fee.

API, Python examples with expected HTTP bodies, errors, balance, and withdraw: API reference.