Skip to main content
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 06:13 UTC · reused for up to 5 min

scvd.store: x402 purchase results on Base, as of 2026-09-26

27 Base listings. By the latest attempt at each: 4 delivered · 0 failed on the seller's side · 13 on vet402's side · 1 not bought (vet402 did not pay) · 9 not tried yet. Latest attempt: 2026-09-26 18:01 UTC.

1.Your listings

  1. scvd.store/api/buy/daily_fortuneGET
    Latest attempt
    2026-09-26 18: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.01 USDC · payTo 0xdd35…9bd0. 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.01 USDC · payTo 0xdd35…9bd0 · nonce 0xf81d…52a8 · 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 0xd622dbc0…c317In export.csv?days=4: the row with attempted_at 2026-09-26T18:01:45Z and resource_key scvd.store/api/buy/daily_fortune.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-12 06:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x49bd456a…d61b
      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 0xdd35…9bd0. 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 0xdd35…9bd0 · nonce 0x7d64…5bf8 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  2. scvd.store/api/buy/luckiesGET
    Latest attempt
    2026-09-26 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.99 USDC · payTo 0xdd35…9bd0. 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.99 USDC · payTo 0xdd35…9bd0 · nonce 0xc6da…0000 · 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 0xf70c7561…0117In export.csv?days=4: the row with attempted_at 2026-09-26T12:02:32Z and resource_key scvd.store/api/buy/luckies.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-12 18:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x1421cddc…85f6
      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.99 USDC · payTo 0xdd35…9bd0. 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.99 USDC · payTo 0xdd35…9bd0 · nonce 0x2374…8226 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-09-05 19:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xf3dabf7a…454c
      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.99 USDC · payTo 0xdd35…9bd0. 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.99 USDC · payTo 0xdd35…9bd0 · nonce 0x4d85…6672 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  3. scvd.store/api/buy/signature_agent_cardGET
    Latest attempt
    2026-09-21 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.99 USDC · payTo 0xdd35…9bd0. 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.99 USDC · payTo 0xdd35…9bd0 · nonce 0xde5f…04cd · 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-21T00:02:04Z and resource_key scvd.store/api/buy/signature_agent_card.Dispute this purchaseEmail me when this result changes
  4. scvd.store/api/buy/settlement_attestationGET
    Latest attempt
    2026-09-20 18: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.004 USDC · payTo 0xdd35…9bd0. 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.004 USDC · payTo 0xdd35…9bd0 · nonce 0xb919…f5ed · 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-20T18:02:28Z and resource_key scvd.store/api/buy/settlement_attestation.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-13 18:01 UTC · vet402's wallet held less USDC than the price · vet402's sidesettle_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)
      What vet402 recordedWhen vet402 signed, its payer wallet held less USDC than the price, by the wallet's balance rebuilt from its own USDC transfers on-chain. The payment had nothing behind it, so the failure is on vet402's side.The 402 terms vet402 paid: vet402 signed: exact · 0.004 USDC · payTo 0xdd35…9bd0. 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.004 USDC · payTo 0xdd35…9bd0 · nonce 0x57e0…810e · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.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's wallet held less USDC than the price.
      Dispute this purchase
    2. 2026-09-03 07:01 UTC · vet402 did not send the declared query · vet402's sidesettle_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)
      What vet402 recordedBefore 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.The 402 terms vet402 paid: vet402 signed: exact · 0.004 USDC · payTo 0xdd35…9bd0. 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.004 USDC · payTo 0xdd35…9bd0 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.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.
      Dispute this purchase
  5. scvd.store/api/buy/graffiti_on_a_trainGET
    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 · 1 USDC · payTo 0xdd35…9bd0. 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 · 1 USDC · payTo 0xdd35…9bd0 · nonce 0x3aa4…641a · 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-20T06:01:43Z and resource_key scvd.store/api/buy/graffiti_on_a_train.Dispute this purchaseEmail me when this result changes
  6. scvd.store/api/buy/passport_refreshGET
    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 · 1 USDC · payTo 0xdd35…9bd0. 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 · 1 USDC · payTo 0xdd35…9bd0 · nonce 0x5d00…580c · 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-20T06:01:38Z and resource_key scvd.store/api/buy/passport_refresh.Dispute this purchaseEmail me when this result changes
  7. scvd.store/api/buy/the_case_fileGET
    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.25 USDC · payTo 0xdd35…9bd0. 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.25 USDC · payTo 0xdd35…9bd0 · nonce 0x56a4…f45d · 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-20T06:01:32Z and resource_key scvd.store/api/buy/the_case_file.Dispute this purchaseEmail me when this result changes
  8. scvd.store/api/buy/attestation_bundleGET
    Latest attempt
    2026-09-20 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.05 USDC · payTo 0xdd35…9bd0. 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 0xdd35…9bd0 · nonce 0xcd70…7f99 · 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-20T06:00:43Z and resource_key scvd.store/api/buy/attestation_bundle.Dispute this purchaseEmail me when this result changes
  9. scvd.store/api/buy/spot_checkGET
    Latest attempt
    2026-09-19 18: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.001 USDC · payTo 0xdd35…9bd0. 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.001 USDC · payTo 0xdd35…9bd0 · nonce 0xce3a…853b · 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-19T18:00:34Z and resource_key scvd.store/api/buy/spot_check.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-13 12:09 UTC · vet402's wallet held less USDC than the price · vet402's sidesettle_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)
      What vet402 recordedWhen vet402 signed, its payer wallet held less USDC than the price, by the wallet's balance rebuilt from its own USDC transfers on-chain. The payment had nothing behind it, so the failure is on vet402's side.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xdd35…9bd0. 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.001 USDC · payTo 0xdd35…9bd0 · nonce 0xe75a…8932 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.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's wallet held less USDC than the price.
      Dispute this purchase
    2. 2026-09-04 07:01 UTC · vet402 did not send the declared query · vet402's sidesettle_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)
      What vet402 recordedBefore 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.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xdd35…9bd0. 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.001 USDC · payTo 0xdd35…9bd0 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.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.
      Dispute this purchase
  10. scvd.store/api/buy/small_blessingGET
    Latest attempt
    2026-09-17 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.005 USDC · payTo 0xdd35…9bd0. 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 0xdd35…9bd0 · nonce 0x0bc9…a649 · 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 0xdf8c64a7…99c9In export.csv?days=14: the row with attempted_at 2026-09-17T00:02:14Z and resource_key scvd.store/api/buy/small_blessing.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-10 19:02 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x32248fb5…ef6c
      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.005 USDC · payTo 0xdd35…9bd0. 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 0xdd35…9bd0 · nonce 0xc075…2837 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-09-02 07:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xddd48f2e…7417
      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.005 USDC · payTo 0xdd35…9bd0. 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 0xdd35…9bd0 · 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
  11. scvd.store/api/buy/settlement_reconciliationGET
    Latest attempt
    2026-09-15 23:51 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.006 USDC · payTo 0xdd35…9bd0. 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.006 USDC · payTo 0xdd35…9bd0 · nonce 0xacdb…d6e3 · 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=15: the row with attempted_at 2026-09-15T23:51:20Z and resource_key scvd.store/api/buy/settlement_reconciliation.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-07 19:01 UTC · vet402 did not send the declared query · vet402's sidesettle_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)
      What vet402 recordedBefore 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.The 402 terms vet402 paid: vet402 signed: exact · 0.006 USDC · payTo 0xdd35…9bd0. 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.006 USDC · payTo 0xdd35…9bd0 · nonce 0x013b…c656 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.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.
      Dispute this purchase
  12. scvd.store/api/buy/coffees_for_closersGET
    Latest attempt
    2026-09-11 18:00 UTC
    Result
    Not bought: no 402 to the unpaid request
    Whose side
    not bought: vet402 did not pay
    What we saw: The unpaid request got a status other than 402 (for example 400 or 422; the unpaid request does not carry the declared input), so vet402 did not pay.Last result about the seller: none among the attempts shown. The latest attempt was not a purchase (vet402 did not pay); vet402 has not bought this listing again since.The 402 vet402 saw: The unpaid request got HTTP 400, not a 402.What to fix: Nothing is counted against the seller: vet402 did not pay, so this is not a purchase result.Recorded (attempt; vet402 did not pay, not an L1 result): no_402 (the unpaid request did not get a 402, so nothing was paid) · HTTP — (unpaid answer 400) · no txIn export.csv?days=19: the row with attempted_at 2026-09-11T18:00:25Z and resource_key scvd.store/api/buy/coffees_for_closers.Dispute this purchaseEmail me when this result changes
  13. scvd.store/api/buy/the_confessionGET
    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.01 USDC · payTo 0xdd35…9bd0. 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 0xdd35…9bd0 · nonce 0x8d26…023b · 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:48Z and resource_key scvd.store/api/buy/the_confession.Dispute this purchaseEmail me when this result changes
  14. scvd.store/api/buy/the_mandateGET
    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.1 USDC · payTo 0xdd35…9bd0. 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 0xdd35…9bd0 · nonce 0xebcf…3dc2 · 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:45Z and resource_key scvd.store/api/buy/the_mandate.Dispute this purchaseEmail me when this result changes
  15. scvd.store/api/buy/bitcoin_anchorGET
    Latest attempt
    2026-09-07 07: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 · 1 USDC · payTo 0xdd35…9bd0. 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 · 1 USDC · payTo 0xdd35…9bd0 · nonce 0xd21b…0450 · 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:02:03Z and resource_key scvd.store/api/buy/bitcoin_anchor.Dispute this purchaseEmail me when this result changes
  16. scvd.store/api/buy/onpage_auditGET
    Latest attempt
    2026-09-06 19:01 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 3000000 · asset 0x8335…2913 · payTo 0xDD35…9bd0 · maxTimeoutSeconds 300; exact · eip155:137 · amount 3000000 · asset 0x3c49…3359 · payTo 0xdd35…9bd0 · maxTimeoutSeconds 300; exact · solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp · amount 3000000 · asset EPjFWd…Dt1v · payTo DGxcPr…vMgE · maxTimeoutSeconds 300. At the time, the listing declared price 3 · payTo 0xdd35…9bd0.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=24: the row with attempted_at 2026-09-06T19:01:27Z and resource_key scvd.store/api/buy/onpage_audit.Dispute this purchaseEmail me when this result changes
  17. scvd.store/api/buy/helloGET
    Latest attempt
    2026-09-05 12:10 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.5 USDC · payTo 0xdd35…9bd0. 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.5 USDC · payTo 0xdd35…9bd0 · nonce 0xdfeb…7a85 · 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 0xde840b86…64dcIn export.csv?days=25: the row with attempted_at 2026-09-05T12:10:02Z and resource_key scvd.store/api/buy/hello.Dispute this purchaseEmail me when this result changes
  18. scvd.store/api/buy/conformance_watchGET
    Latest attempt
    2026-09-05 07:02 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 0xDD35…9bd0 · maxTimeoutSeconds 300; exact · eip155:137 · amount 5000000 · asset 0x3c49…3359 · payTo 0xDD35…9bd0 · maxTimeoutSeconds 300; exact · solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp · amount 5000000 · asset EPjFWd…Dt1v · payTo DGxcPr…vMgE · maxTimeoutSeconds 300. At the time, the listing declared price 5 · payTo 0xdd35…9bd0.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=25: the row with attempted_at 2026-09-05T07:02:08Z and resource_key scvd.store/api/buy/conformance_watch.Dispute this purchaseEmail me when this result changes
  19. scvd.store/api/buy/good_buyerGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  20. scvd.store/api/buy/launch_checkGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  21. scvd.store/api/buy/packGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  22. scvd.store/api/buy/provenance_checkGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  23. scvd.store/api/buy/research_comparisonGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  24. scvd.store/api/buy/service_auditGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  25. scvd.store/api/buy/standing_watchGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  26. scvd.store/api/buy/the_statementGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  27. scvd.store/api/buy/window_pickGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email 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.