Poll the status of an asynchronous operation. The webhook ID is returned
in the X-HTTPayer-Webhook header of the original response.
Two contexts produce webhook IDs:
Proxy — payment confirmation
When /proxy returns 502 (upstream refused payment), a webhook is created
to track whether the payment eventually confirmed on-chain. On success,
status is success and txHash is the on-chain payment proof.
Relay — refund tracking
When a relay payment cannot be settled or the target API never charges,
a webhook tracks the refund. Terminal statuses are refund_confirmed,
success_refunded, or no_refund_needed.
Poll until you receive HTTP 200 or 500. HTTP 202 means still in progress.
Webhook ID (UUID from X-HTTPayer-Webhook header)
Operation completed successfully
success — proxy payment confirmed on-chain (payment proof in txHash).
refund_confirmed — refund transaction confirmed on-chain.
success_refunded — relay succeeded but target did not charge; refund issued.
no_refund_needed — target charged HTTPayer within the auth window.
success, refund_confirmed, success_refunded, no_refund_needed Proxy: on-chain payment transaction hash (proof of payment). Relay: on-chain refund transaction hash.
Network the transaction was confirmed on.
Relay only — how the refund was executed: facilitator or direct.
Relay only — internal relay transaction ID.
Relay only — facilitator used for the refund, if applicable.
Human-readable description of the outcome.