402cron.com: x402 purchase results on Base, as of 2026-09-24

2 Base listings. By the latest attempt at each: 1 delivered · 0 failed on the seller's side · 1 on vet402's side · 0 not tried yet. Latest attempt: 2026-09-24 12:02 UTC.

1.Your listings

1. 402cron.com/buy/trialGET

   Latest attempt

   2026-09-24 12:02 UTC

   Result

   delivered

   Whose side

   no failure (delivered)

   What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x8e37…36f4. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x8e37…36f4 · nonce 0x52c7…d6db · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · no PAYMENT-RESPONSE recorded.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xdfb920f5…e06dIn export.csv?days=6: the row with attempted_at 2026-09-24T12:02:09Z and resource_key 402cron.com/buy/trial.Dispute this purchaseEmail me when this result changes

   Earlier attempts

   1. 2026-09-17 18:02 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xf7d84754…5e6d
      What vet402 recorded

      Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x8e37…36f4. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x8e37…36f4 · nonce 0x942f…1420 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
   2. 2026-09-10 19:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x920854db…97f6
      What vet402 recorded

      Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x8e37…36f4. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x8e37…36f4 · nonce 0xa6a6…eb51 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
2. 402cron.com/buy/starterGET

   Latest attempt

   2026-09-12 06:00 UTC

   Result

   vet402's own limits

   Whose side

   vet402's side

   What we saw: vet402 did not pay: the price was over its per-purchase ceiling, its budget for the day was used up, its operator halted spending, or the 402 named vet402's own receiving address.Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 vet402 saw: The 402 offered: exact · eip155:8453 · amount 2000000 · asset 0x8335…2913 · payTo 0x8e37…36f4 · maxTimeoutSeconds 60. At the time, the listing declared price 2 · payTo 0x8e37…36f4.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (attempt; vet402 did not pay, not an L1 result): over_cap (the price was over vet402's per-purchase ceiling, so nothing was paid) · HTTP — · no txIn export.csv?days=19: the row with attempted_at 2026-09-12T06:00:45Z and resource_key 402cron.com/buy/starter.Dispute this purchaseEmail me when this result changes

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result (“Recorded (L1 paid purchase)”); a row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. 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?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.