hypernatt.com
2 Base listings. By the latest purchase of each: 1 delivered · 0 failed on the seller's side · 1 on vet402's side · 0 not yet bought. Latest purchase: 2026-09-27 00:00 UTC.
Your most recent purchase failed on vet402's side. Nothing for you to fix there.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| hypernatt.com/api/m2m/swap/quoteGET | 2026-09-27 00:00 UTC | vet402 did not send the declared query | vet402's side |
What we saw: Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing marks some of them as required. The seller refused the request with 400 or 422.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settled · HTTP 400 · tx 0x1c83a382…e7d7 · held as settled_4xxIn export.csv?days=3: the row with attempted_at 2026-09-27T00:00:48Z and resource_key hypernatt.com/api/m2m/swap/quote.Earlier: 2026-09-20 18:01 UTC vet402 did not send the declared query (vet402's side) · 2026-09-14 12:08 UTC vet402's wallet was out of USDC (vet402's side) · 2026-08-29 12:08 UTC vet402 did not send the declared query (vet402's side) · 2026-08-21 12:22 UTC vet402 did not send the declared query (vet402's side) | |||
| hypernatt.com/api/m2m/liq-radarGET | 2026-09-25 18:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The latest purchase delivered. An earlier purchase listed below did not.Recorded: settled · HTTP 200 · tx 0x6c8b528e…3cb1In export.csv?days=4: the row with attempted_at 2026-09-25T18:01:08Z and resource_key hypernatt.com/api/m2m/liq-radar.Earlier: 2026-09-19 12:08 UTC delivered · 2026-08-27 12:31 UTC delivered · 2026-08-20 12:55 UTC Answered 2xx, but the payment was not confirmed (seller's side) · 2026-08-14 09:55 UTC Answered 2xx, but the payment was not confirmed (seller's side) | |||
2.How to read this
Each listing shows its latest purchase on Base and up to four earlier ones. Whose side says where the failure came from: the seller's answer or listing, or vet402 itself. A row held (held_reason in the export) is not counted against the seller in the delivered numbers, because vet402 cannot rule out that its request was the problem. The transaction link opens the settlement on Basescan. Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).
3.Think a row is wrong?
Open the listing's record (the link in the first column) and use “Dispute this record” there. Say which purchase and what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.