Submit the transaction hash

Attach the on-chain transaction hash to a session. The client's success claim is never trusted: the server reads the receipt from the network's RPC and requires a USDC `Transfer` log to the exact recipient for the exact expected amount, mined no earlier than the session was created, plus the network's minimum confirmations. A hash can only ever be attached to one session (replay guard), and submissions are rate limited per IP and per session. Returns `PENDING` or `CONFIRMING` while the transfer is still settling — keep polling the status query until `PAID`. Returns `FAILED` (with `error`) when the transaction is final but can never pay this session, e.g. wrong amount or reverted; the buyer must send a new transfer.

Base URL: https://platform.hyax.com · Replace YOUR_API_KEY with your team API key.

curl -X POST 'https://platform.hyax.com/hyax-api/trpc/crypto.submitCryptoPayment' \
  -H 'Content-Type: application/json' \
  -d '{
    "json": {
      "teamId": "clx_team_id",
      "sessionId": "clx_session_id",
      "txHash": "0x0000000000000000000000000000000000000000000000000000000000000000"
    }
  }'

{
  "result": {
    "data": {
      "json": {
        "status": "CONFIRMING",
        "confirmations": 1,
        "error": "Waiting for confirmations (1/3)."
      }
    }
  }
}