Skip to main content
vet402
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 04:07 UTC · reused for up to 5 min
vet402Sellers · What to fix firstMethodology

402.com.tr: x402 purchase results on Base, as of 2026-09-28

174 Base listings. By the latest attempt at each: 7 delivered · 0 failed on the seller's side · 49 on vet402's side · 118 not tried yet. Latest attempt: 2026-09-28 06:01 UTC. Leaving out attempts that failed on vet402's side, were not bought, or are not sorted, the latest result that says something about the seller is: 8 delivered · 0 failed on the seller's side · 48 with no such result among the attempts shown.

Rows marked census or retest were bought to give this seller a row of its own, or to buy again after a failure on vet402's side.

1.Your listings

  1. 402.com.tr/api/x402/holiday-calendarGET
    Latest attempt
    2026-09-28 06:01 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.002 USDC · payTo 0x973a…12d6. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x973a…12d6 · nonce 0xfe53…488a · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.The latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x5a63c204…ada9 · bought by the retestIn export.csv?days=2: the row with attempted_at 2026-09-28T06:01:48Z and resource_key 402.com.tr/api/x402/holiday-calendar.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-14 18:00 UTC · vet402's wallet was out of USDC · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))
      What vet402 recordedBetween 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x973a…12d6 · nonce 0xfc7c…8fa3 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
  2. 402.com.tr/api/x402/first-funderGET
    Latest attempt
    2026-09-27 06:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.04 USDC · payTo 0x973a…12d6. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.04 USDC · payTo 0x973a…12d6 · nonce 0x1a8f…0967 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=3: the row with attempted_at 2026-09-27T06:01:38Z and resource_key 402.com.tr/api/x402/first-funder.Dispute this purchaseEmail me when this result changes
  3. 402.com.tr/api/x402/token-momentumGET
    Latest attempt
    2026-09-27 00:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x973a…12d6. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x973a…12d6 · nonce 0x1a90…72b6 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=4: the row with attempted_at 2026-09-27T00:00:28Z and resource_key 402.com.tr/api/x402/token-momentum.Dispute this purchaseEmail me when this result changes
  4. 402.com.tr/api/x402/ai-tx-explainGET
    Latest attempt
    2026-09-20 06:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.04 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.04 USDC · payTo 0x973a…12d6 · nonce 0xcabc…8dca · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=10: the row with attempted_at 2026-09-20T06:01:43Z and resource_key 402.com.tr/api/x402/ai-tx-explain.Dispute this purchaseEmail me when this result changes
  5. 402.com.tr/api/x402/receipt-parseGET
    Latest attempt
    2026-09-20 06:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce 0x3cd9…e748 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=10: the row with attempted_at 2026-09-20T06:01:06Z and resource_key 402.com.tr/api/x402/receipt-parse.Dispute this purchaseEmail me when this result changes
  6. 402.com.tr/api/x402/b20-guardGET
    Latest attempt
    2026-09-20 00: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.05 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x973a…12d6 · nonce 0xfd65…d40d · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x2fce83a2…5f87In export.csv?days=11: the row with attempted_at 2026-09-20T00:02:12Z and resource_key 402.com.tr/api/x402/b20-guard.Dispute this purchaseEmail me when this result changes
  7. 402.com.tr/api/x402/decode-selectorGET
    Latest attempt
    2026-09-20 00:02 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce 0x1cc4…604d · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=11: the row with attempted_at 2026-09-20T00:02:10Z and resource_key 402.com.tr/api/x402/decode-selector.Dispute this purchaseEmail me when this result changes
  8. 402.com.tr/api/x402/compliance-checkGET
    Latest attempt
    2026-09-19 12:07 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0x39a8…796b · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=11: the row with attempted_at 2026-09-19T12:07:54Z and resource_key 402.com.tr/api/x402/compliance-check.Dispute this purchaseEmail me when this result changes
  9. 402.com.tr/api/x402/token-compareGET
    Latest attempt
    2026-09-18 12:08 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x973a…12d6 · nonce 0xbf10…8cdd · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=12: the row with attempted_at 2026-09-18T12:08:28Z and resource_key 402.com.tr/api/x402/token-compare.Dispute this purchaseEmail me when this result changes
  10. 402.com.tr/api/x402/address-intelGET
    Latest attempt
    2026-09-18 00:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x973a…12d6 · nonce 0xec39…836f · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=13: the row with attempted_at 2026-09-18T00:01:52Z and resource_key 402.com.tr/api/x402/address-intel.Dispute this purchaseEmail me when this result changes
  11. 402.com.tr/api/x402/phone-checkGET
    Latest attempt
    2026-09-17 06:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x973a…12d6 · nonce 0x9f16…89b1 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=13: the row with attempted_at 2026-09-17T06:00:49Z and resource_key 402.com.tr/api/x402/phone-check.Dispute this purchaseEmail me when this result changes
  12. 402.com.tr/api/x402/gas-oracleGET
    Latest attempt
    2026-09-17 06:00 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.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce 0x413e…eaf6 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x108fb99e…3ae5In export.csv?days=13: the row with attempted_at 2026-09-17T06:00:46Z and resource_key 402.com.tr/api/x402/gas-oracle.Dispute this purchaseEmail me when this result changes
  13. 402.com.tr/api/x402/settlement-lineGET
    Latest attempt
    2026-09-16 12:08 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x973a…12d6 · nonce 0xe436…4d30 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=14: the row with attempted_at 2026-09-16T12:08:28Z and resource_key 402.com.tr/api/x402/settlement-line.Dispute this purchaseEmail me when this result changes
  14. 402.com.tr/api/x402/buy-creditsGET
    Latest attempt
    2026-09-14 18: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 5000000 · asset 0x8335…2913 · payTo 0x973a…12d6 · maxTimeoutSeconds 300. At the time, the listing declared price 5 · payTo 0x973a…12d6.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=16: the row with attempted_at 2026-09-14T18:00:14Z and resource_key 402.com.tr/api/x402/buy-credits.Dispute this purchaseEmail me when this result changes
  15. 402.com.tr/api/x402/b20-gateGET
    Latest attempt
    2026-09-14 12:07 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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 terms vet402 paid: vet402 signed: exact · 0.1 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.1 USDC · payTo 0x973a…12d6 · nonce 0x872e…0886 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=16: the row with attempted_at 2026-09-14T12:07:39Z and resource_key 402.com.tr/api/x402/b20-gate.Dispute this purchaseEmail me when this result changes
  16. 402.com.tr/api/x402/breach-checkGET
    Latest attempt
    2026-09-14 06:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x973a…12d6 · nonce 0x9ecb…1858 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=16: the row with attempted_at 2026-09-14T06:00:28Z and resource_key 402.com.tr/api/x402/breach-check.Dispute this purchaseEmail me when this result changes
  17. 402.com.tr/api/x402/counterparty-checkGET
    Latest attempt
    2026-09-14 06:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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 terms vet402 paid: vet402 signed: exact · 0.12 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.12 USDC · payTo 0x973a…12d6 · nonce 0x4491…4b26 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=16: the row with attempted_at 2026-09-14T06:00:22Z and resource_key 402.com.tr/api/x402/counterparty-check.Dispute this purchaseEmail me when this result changes
  18. 402.com.tr/api/x402/ai-translateGET
    Latest attempt
    2026-09-14 06:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0x43b3…d6b6 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=16: the row with attempted_at 2026-09-14T06:00:15Z and resource_key 402.com.tr/api/x402/ai-translate.Dispute this purchaseEmail me when this result changes
  19. 402.com.tr/api/x402/b20-launch-radarGET
    Latest attempt
    2026-09-13 18:01 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).Last result about the seller: delivered on 2026-09-04 09:25 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce 0x084f…35ce · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=17: the row with attempted_at 2026-09-13T18:01:36Z and resource_key 402.com.tr/api/x402/b20-launch-radar.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-04 09:25 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x9864f623…bb17
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  20. 402.com.tr/api/x402/bank-csvGET
    Latest attempt
    2026-09-13 06:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce 0x2c29…72bc · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=17: the row with attempted_at 2026-09-13T06:00:28Z and resource_key 402.com.tr/api/x402/bank-csv.Dispute this purchaseEmail me when this result changes
  21. 402.com.tr/api/x402/exit-liquidityGET
    Latest attempt
    2026-09-13 06:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x973a…12d6 · nonce 0x13d6…5bd6 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=17: the row with attempted_at 2026-09-13T06:00:18Z and resource_key 402.com.tr/api/x402/exit-liquidity.Dispute this purchaseEmail me when this result changes
  22. 402.com.tr/api/x402/portfolio-scanGET
    Latest attempt
    2026-09-13 06:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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 terms vet402 paid: vet402 signed: exact · 0.15 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.15 USDC · payTo 0x973a…12d6 · nonce 0x53e1…a07e · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=17: the row with attempted_at 2026-09-13T06:00:14Z and resource_key 402.com.tr/api/x402/portfolio-scan.Dispute this purchaseEmail me when this result changes
  23. 402.com.tr/api/x402/lp-lockGET
    Latest attempt
    2026-09-12 06:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x973a…12d6 · nonce 0xcd7e…d1ae · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=18: the row with attempted_at 2026-09-12T06:00:44Z and resource_key 402.com.tr/api/x402/lp-lock.Dispute this purchaseEmail me when this result changes
  24. 402.com.tr/api/x402/whale-flowGET
    Latest attempt
    2026-09-12 06:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.04 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.04 USDC · payTo 0x973a…12d6 · nonce 0xec8d…1839 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=18: the row with attempted_at 2026-09-12T06:00:42Z and resource_key 402.com.tr/api/x402/whale-flow.Dispute this purchaseEmail me when this result changes
  25. 402.com.tr/api/x402/b20-memoGET
    Latest attempt
    2026-09-12 06:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0xddf5…e3f8 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=18: the row with attempted_at 2026-09-12T06:00:41Z and resource_key 402.com.tr/api/x402/b20-memo.Dispute this purchaseEmail me when this result changes
  26. 402.com.tr/api/x402/b20-freeze-checkGET
    Latest attempt
    2026-09-11 06:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0x1225…f293 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=19: the row with attempted_at 2026-09-11T06:01:26Z and resource_key 402.com.tr/api/x402/b20-freeze-check.Dispute this purchaseEmail me when this result changes
  27. 402.com.tr/api/x402/b20-seizure-historyGET
    Latest attempt
    2026-09-11 06:01 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.05 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x973a…12d6 · nonce 0xd258…6402 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x512e6667…476aIn export.csv?days=19: the row with attempted_at 2026-09-11T06:01:24Z and resource_key 402.com.tr/api/x402/b20-seizure-history.Dispute this purchaseEmail me when this result changes
  28. 402.com.tr/api/x402/pre-trade-gateGET
    Latest attempt
    2026-09-11 06:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.1 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.1 USDC · payTo 0x973a…12d6 · nonce 0x57fb…5b8c · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=19: the row with attempted_at 2026-09-11T06:01:24Z and resource_key 402.com.tr/api/x402/pre-trade-gate.Dispute this purchaseEmail me when this result changes
  29. 402.com.tr/api/x402/chain-statusGET
    Latest attempt
    2026-09-10 12:08 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.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce 0xc069…3cf9 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xe6e90cec…6c4dIn export.csv?days=20: the row with attempted_at 2026-09-10T12:08:58Z and resource_key 402.com.tr/api/x402/chain-status.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-02 12:08 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xa6f9655a…6b3a
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  30. 402.com.tr/api/x402/batch-riskGET
    Latest attempt
    2026-09-10 07:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.08 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.08 USDC · payTo 0x973a…12d6 · nonce 0x7d3e…76c3 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=20: the row with attempted_at 2026-09-10T07:01:18Z and resource_key 402.com.tr/api/x402/batch-risk.Dispute this purchaseEmail me when this result changes
  31. 402.com.tr/api/x402/commerce-operator-auditGET
    Latest attempt
    2026-09-10 07:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x973a…12d6 · nonce 0xb536…1940 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=20: the row with attempted_at 2026-09-10T07:00:57Z and resource_key 402.com.tr/api/x402/commerce-operator-audit.Dispute this purchaseEmail me when this result changes
  32. 402.com.tr/api/x402/stock-positionGET
    Latest attempt
    2026-09-10 07:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0x3ba2…c56f · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=20: the row with attempted_at 2026-09-10T07:00:56Z and resource_key 402.com.tr/api/x402/stock-position.Dispute this purchaseEmail me when this result changes
  33. 402.com.tr/api/x402/company-leiGET
    Latest attempt
    2026-09-10 01:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x973a…12d6 · nonce 0x956c…2a84 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=21: the row with attempted_at 2026-09-10T01:00:17Z and resource_key 402.com.tr/api/x402/company-lei.Dispute this purchaseEmail me when this result changes
  34. 402.com.tr/api/x402/token-poolsGET
    Latest attempt
    2026-09-09 07:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x973a…12d6 · nonce 0xecd7…d7de · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=21: the row with attempted_at 2026-09-09T07:01:47Z and resource_key 402.com.tr/api/x402/token-pools.Dispute this purchaseEmail me when this result changes
  35. 402.com.tr/api/x402/ai-market-briefGET
    Latest attempt
    2026-09-09 07:01 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.05 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x973a…12d6 · nonce 0xd421…fa2c · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xf8d0e065…9b9bIn export.csv?days=21: the row with attempted_at 2026-09-09T07:01:08Z and resource_key 402.com.tr/api/x402/ai-market-brief.Dispute this purchaseEmail me when this result changes
  36. 402.com.tr/api/x402/b20-announcementsGET
    Latest attempt
    2026-09-09 07:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0xe0c9…47fc · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=21: the row with attempted_at 2026-09-09T07:00:56Z and resource_key 402.com.tr/api/x402/b20-announcements.Dispute this purchaseEmail me when this result changes
  37. 402.com.tr/api/x402/sanctions-nameGET
    Latest attempt
    2026-09-08 07:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x973a…12d6 · nonce 0xbf5a…f4d3 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=22: the row with attempted_at 2026-09-08T07:01:13Z and resource_key 402.com.tr/api/x402/sanctions-name.Dispute this purchaseEmail me when this result changes
  38. 402.com.tr/api/x402/onramp-quoteGET
    Latest attempt
    2026-09-08 07:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0xe0d1…3215 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=22: the row with attempted_at 2026-09-08T07:00:58Z and resource_key 402.com.tr/api/x402/onramp-quote.Dispute this purchaseEmail me when this result changes
  39. 402.com.tr/api/x402/proxy-checkGET
    Latest attempt
    2026-09-07 12:09 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0x1c20…e255 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=23: the row with attempted_at 2026-09-07T12:09:03Z and resource_key 402.com.tr/api/x402/proxy-check.Dispute this purchaseEmail me when this result changes
  40. 402.com.tr/api/x402/inflation-adjustGET
    Latest attempt
    2026-09-07 07:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x973a…12d6 · nonce 0x96e7…c5e2 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=23: the row with attempted_at 2026-09-07T07:01:29Z and resource_key 402.com.tr/api/x402/inflation-adjust.Dispute this purchaseEmail me when this result changes
  41. 402.com.tr/api/x402/ai-extract-batchGET
    Latest attempt
    2026-09-06 07:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.1 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.1 USDC · payTo 0x973a…12d6 · nonce 0xd682…3cef · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=24: the row with attempted_at 2026-09-06T07:01:23Z and resource_key 402.com.tr/api/x402/ai-extract-batch.Dispute this purchaseEmail me when this result changes
  42. 402.com.tr/api/x402/b20-dossierGET
    Latest attempt
    2026-09-06 01:02 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.75 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.75 USDC · payTo 0x973a…12d6 · nonce 0x421d…c851 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-06T01:02:15Z and resource_key 402.com.tr/api/x402/b20-dossier.Dispute this purchaseEmail me when this result changes
  43. 402.com.tr/api/x402/contract-infoGET
    Latest attempt
    2026-09-06 01:02 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x973a…12d6 · nonce 0x49cf…67be · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-06T01:02:06Z and resource_key 402.com.tr/api/x402/contract-info.Dispute this purchaseEmail me when this result changes
  44. 402.com.tr/api/x402/watchlist-diffGET
    Latest attempt
    2026-09-06 01:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.06 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.06 USDC · payTo 0x973a…12d6 · nonce 0xd3cd…ad5f · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-06T01:01:26Z and resource_key 402.com.tr/api/x402/watchlist-diff.Dispute this purchaseEmail me when this result changes
  45. 402.com.tr/api/x402/onramp-coverageGET
    Latest attempt
    2026-09-05 19:02 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0x973a…12d6 · nonce 0x79d8…925e · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-05T19:02:11Z and resource_key 402.com.tr/api/x402/onramp-coverage.Dispute this purchaseEmail me when this result changes
  46. 402.com.tr/api/x402/ai-wallet-reportGET
    Latest attempt
    2026-09-05 19:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.06 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.06 USDC · payTo 0x973a…12d6 · nonce 0xec20…476f · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-05T19:01:31Z and resource_key 402.com.tr/api/x402/ai-wallet-report.Dispute this purchaseEmail me when this result changes
  47. 402.com.tr/api/x402/url-to-jsonGET
    Latest attempt
    2026-09-05 19:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x973a…12d6 · nonce 0x4266…2e8d · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-05T19:00:42Z and resource_key 402.com.tr/api/x402/url-to-json.Dispute this purchaseEmail me when this result changes
  48. 402.com.tr/api/x402/spend-auditGET
    Latest attempt
    2026-09-05 19:00 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x973a…12d6 · nonce 0x2963…34ae · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-05T19:00:19Z and resource_key 402.com.tr/api/x402/spend-audit.Dispute this purchaseEmail me when this result changes
  49. 402.com.tr/api/x402/base-withdrawalGET
    Latest attempt
    2026-09-05 12:09 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.04 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.04 USDC · payTo 0x973a…12d6 · nonce 0x3d30…f2c3 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-05T12:09:55Z and resource_key 402.com.tr/api/x402/base-withdrawal.Dispute this purchaseEmail me when this result changes
  50. 402.com.tr/api/x402/address-trustGET
    Latest attempt
    2026-09-05 12:07 UTC
    Result
    vet402 did not send the declared query
    Whose side
    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 declares them (example values, or required names). The seller refused the request with 400 or 422.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 terms vet402 paid: vet402 signed: exact · 0.03 USDC · payTo 0x973a…12d6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.03 USDC · payTo 0x973a…12d6 · nonce 0x1567…b208 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=25: the row with attempted_at 2026-09-05T12:07:38Z and resource_key 402.com.tr/api/x402/address-trust.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.