Northwind Outdoor · Dispute desk · test money on Metal testnet
Your dispute DD-a88e8959
Summit Outfitters is a simulated customer run by us; we filed this claim on its behalf (30 October recorded run).
Opened 2026-10-30 08:32 UTC · 12 payments from 0xB6C24EC17Ab3fa37d80eC7739AaF387e49a1eB25
The evidence, per payment
| Payment | Charged | Signed order | Chain check | Delivered | Refund |
|---|---|---|---|---|---|
| 5 GET /v1/stock?seq=5 2026-10-30 07:06:20 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0x2a81d430…f08a |
✓ as we recorded it dc5531775ed246ac… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 6 GET /v1/stock?seq=6 2026-10-30 07:06:24 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0xaf863cec…3e50 |
✓ as we recorded it 9c8b7c9aa9990fbd… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 7 GET /v1/stock?seq=7 2026-10-30 07:06:28 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0x5362e5e7…82be |
✓ as we recorded it dfb5c35698225858… |
0.00 0.05 already refunded earlier Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 8 GET /v1/stock?seq=8 2026-10-30 07:06:31 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0x294576a1…ffd9 |
✓ as we recorded it 1f3c6de5a3b2aee9… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 9 GET /v1/stock?seq=9 2026-10-30 07:06:35 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0xb7451dbf…a282 |
✓ as we recorded it ee416f9e322fea92… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 10 GET /v1/stock?seq=10 2026-10-30 07:06:38 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0xff9aaa36…c64f |
✓ as we recorded it 7cf8769e4e4e091f… |
0.00 0.05 already refunded earlier Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 11 GET /v1/stock?seq=11 2026-10-30 07:06:41 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0xe9e765bb…37d6 |
✓ as we recorded it 5f0679075d0b4092… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 12 GET /v1/stock?seq=12 2026-10-30 07:06:45 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0xb941d7db…d0c4 |
✓ as we recorded it 8c7b85396fc2e925… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 13 GET /v1/stock?seq=13 2026-10-30 07:06:48 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0x147281a4…6676 |
✓ as we recorded it d022485046ca46aa… |
0.00 0.05 already refunded earlier Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 14 GET /v1/stock?seq=14 2026-10-30 07:06:52 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0x3167d810…742e |
✓ as we recorded it 8cc1081f24ed1d74… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 15 GET /v1/stock?seq=15 2026-10-30 07:06:55 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0xe20e1428…e45a |
✓ as we recorded it 8c0aa541d67606bc… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
| 16 GET /v1/stock?seq=16 2026-10-30 07:06:59 UTC |
0.05 | ✓ signed for 0.05 | ✓ inside the bound mandate payment 0x320447bb…4109 |
✓ as we recorded it dccad0d4a63e77ee… |
0.00 Not refunded: your agent gave us a signed order for 0.05 to us (GET /v1/stock), and the payment was verified on chain inside the mandate your account bound. |
Who stood behind the purchase
The decision, explained
Already refunded before this claim: orders 7, 10, 13, 0.15 test USD in all, for wrong data. This decision refunds 0.00 more. Where the explanation below says no payment was refunded, it means by this decision. Where it says the data matches the expected hash, it means the hash recorded at delivery, not that the data was right.
Thank you for raising this. We reviewed each of sales 5 to 16 against the evidence. None of these payments was refunded, and the total refunded by this decision is 0.00 test USD to the paying account 0xB6C24EC17Ab3fa37d80eC7739AaF387e49a1eB25. You said your agent never placed these orders. The records show otherwise. For every sale from 5 through 16 (GET /v1/stock, sequence 5 to 16, each charged 0.05 test USD), the evidence is the same: (1) Your agent gave us a valid signed order for 0.05 to us. (2) The on-chain check confirmed the payment was inside the mandate your account bound. (3) The payment settled on chain, and each sale's transaction ID is listed in the decision record. (4) The data we delivered matches the expected hash. Because a valid signed order, an in-mandate payment and a confirmed delivery exist for each sale, the decision made by code was a refund of 0.00 for each one. If you believe your agent's signing key or mandate was used without your permission, please let us know so the matter can be reviewed further. This explanation does not change the decision.Check it yourself
Each payment and refund links to Metal's explorer. The signed orders, the mandate and each payment can be checked with verifyMandatePayment from @metalntwx/metal-pay (step 4: the payment is your agent's per-payment mandate, inside the mandate at its block). The delivered data's SHA-256 is shown so you can compare it with what you received.