Get the x402 payments of one transaction
/v1/chains/{chain}/x402/payments/{tx}Returns every x402 payment one transaction settled. Use it on a transaction page to show what was paid, to whom, through which facilitator, and whether Sona counts it as genuine. One transaction can settle several payments.
What you can pass. {tx} is the transaction hash, 0x and 64 hex digits in any case. There is no query string.
What comes back: data (kind x402_tx) has the lowercase tx and items, its payments in log order, at least one. A payment of any tier is returned, tier X included, because you asked for the transaction by name. Only payments up to the newest block served are known, so a transaction from the last minute or two may answer 404 for a moment.
Path parameters
| Name | Type | Description |
|---|---|---|
chainRequired | string | The chain, as a CAIP-2 chain ID. Only Monad, |
txRequired | string | The transaction hash: |
Response
The payments of the transaction, wrapped in the {data, meta, links} envelope. data.kind is x402_tx.
| Field | Type | Description |
|---|---|---|
| chain | string | eip155:143eip155:5042eip155:8453 |
| items | array of objects | The payments of the transaction in log order, at least one. |
| kind | string | Always |
| tx | string | The transaction hash in lowercase. |
Cost
1 credit.
Errors
| Status | Code |
|---|---|
| 400 | invalid_queryinvalid_id |
| 404 | not_foundunsupported_chain |
| 429 | rate_limitedcredits_exhausted |
| 500 | internal |
| 503 | upstream_unavailable |
| 504 | deadline_exceeded |
400 invalid_query if you add a query string, 400 invalid_id for a malformed hash. 404 not_found when the transaction settled no x402 payment (it costs the credit). 404 unsupported_chain, 503 upstream_unavailable, 504 deadline_exceeded.