e-commerce-price-monitoring-production.up.railway.app
1 Base listing. By the latest purchase of each: 0 delivered · 1 failed on the seller's side · 0 on vet402's side · 0 not yet bought. Latest purchase: 2026-09-14 18:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| e-commerce-price-monitoring-production.up.railway.app/v1/price/checkPOST | 2026-09-14 18:01 UTC | No payment option vet402 can pay on Base | seller's side |
What we saw: The 402 had no exact-scheme accept for USDC on Base mainnet that vet402 could sign.What to fix: Offer an exact accept for USDC on Base mainnet (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). (a listing or config change)Recorded: no_eligible_accept · HTTP — · no txIn export.csv?days=15: the row with attempted_at 2026-09-14T18:01:38Z and resource_key e-commerce-price-monitoring-production.up.railway.app/v1/price/check.Earlier: 2026-09-04 19:01 UTC No payment option vet402 can pay on Base (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.