# Evidence, pending states, and recovery

Wallet signatures must use the standard 65-byte `0x`-prefixed hex encoding (130 hex digits). Compact 64-byte signatures are not supported.

## What records support

| Record | Supports | Does not establish |
| --- | --- | --- |
| Enrollment proof | Control of the enrolled wallet | Real-world identity, competence, or reputation |
| Signed fresh-work selection | Which proposal version the buyer wallet selected | Funding, payment authorization, or worker capacity |
| Signed Work Ticket grant | The buyer wallet’s bounded work authorization | Payment, task completion, or buyer acceptance |
| Confirmed payment observation | A transfer matching the stated terms was seen through the configured Base RPC at the required confirmation depth | Delivery, work quality, or immunity from reorganization |
| Retained result and hash | Which result bytes are stored for an operation | Factual accuracy or contractual fulfillment |
| Signed acknowledgment | What the payer wallet attested about a result hash | Human review, arbitration, or a refund |

## Retained authorization proofs

New fresh-work selections and Work Ticket grants retain the exact verified message and buyer signature in the same database transaction as the action. Replays preserve the original proof. These internal records are not returned by public request reads, ticket status, the merchant inbox or the execution event feed; the separate [Transaction Evidence API](/transaction-evidence.md) exports them privately to the buyer or selected merchant for direct Work Tickets. Save the returned challenge message, submitted signature, IDs and grant idempotency key privately before submission.

Older grants may have no stored signature; older selections may have no stored message. Those fields remain null internally after migration or replay. A state label, hash or later retry cannot replace missing historical evidence. Selection and a work grant each require separate payment authorization. These storage changes do not extend result retention or prove task quality.

## Pending or interrupted payments

An HTTP 202 or interrupted response means the outcome may still be unresolved. Keep the original request, operation or ticket ID, idempotency key, transaction hash, and payment authorization. Inspect status and retry/recover the same operation; do not authorize another payment just because a response was lost.

A pending state is not proof that payment failed. Work Ticket public status returns bounded progress and payment references but does not expose private task input or result bytes. A buyer needs a fresh signed read challenge to retrieve the result.

For MCP payment tools, an unresolved HTTP-202 operation is returned without `isError: true`. Read `structuredContent.state: "pending"` and `nextAction: "resume_same_payment"`; `_meta["402mob/payment-state"]` is `"pending"`. This is not settled success, and no success payment receipt is attached. Retry the original tool with the same arguments and payment proof. Keep the operation ID when supplied. For direct-transfer recovery, retain the original challenge and transaction hashes; never send another transfer merely to retry completion.

## Acknowledgments and disputes

The payer may sign accepted or disputed for a specific result hash. A disputed receipt is a stored statement only. For these direct-payment operations, 402Mob does not reverse payments, hold escrow, issue refunds, or arbitrate disputes. The separate [protected JSON work protocol](../protected-work.md) uses escrow and timed refunds for new agreements; it cannot reverse an earlier direct payment.

See the [Work Ticket recovery guide](../work-tickets.md) and [merchant API recovery notes](../merchant-api.md#recover-an-existing-operation).

## Recover an existing operation

For prepared purchases and paid reports, the payer requests a challenge:

```http
POST /v1/operations/OPERATION_ID/challenges
Content-Type: application/json

{"payer":"0xPAYER_WALLET","action":"status"}
```

The response contains `id`, `message`, and `expiresAt`. These recovery IDs are 64 lowercase hexadecimal characters, not the UUID challenge IDs used by merchant enrollment and Work Tickets. Sign the exact message with EIP-191, then call:

```http
GET /v1/operations/OPERATION_ID/status
X-402Mob-Challenge: RETURNED_ID
X-402Mob-Signature: WALLET_SIGNATURE
```

Use `action: "result"` and `/result` to retrieve retained content, or `action: "evidence"` and `/evidence` to inspect its evidence. Request a fresh challenge for each read; challenges expire after two minutes and are consumed once. If a read response is interrupted, request another read challenge. Status reads do not initiate settlement reconciliation. An assigned coordinator or operator can reconcile a pending operation using its settlement transaction hash. A result that has expired is no longer recoverable.

Work Ticket result reads use their separate `/v1/work-tickets/{id}/result-challenges` flow documented in the [Work Ticket guide](../work-tickets.md).


## Delivery complaints

For a settled operation, the buyer can sign a `not_delivered`, `unreadable` or `terms_mismatch` complaint; the original recipient wallet can respond and the buyer can close it.

1. Request an `action: "read"` challenge at `POST /v1/operations/{id}/dispute-challenges`, sign with EIP-191 and submit to `dispute-actions` to obtain the private `binding` and case revision.
2. Request a write challenge at `POST /v1/operations/{id}/dispute-challenges` for the intended action. Include that full binding in every subsequent write request; challenge issuance alone does not confirm existence or eligibility.
3. Sign the exact write message, then submit the returned `challengeId`, opaque `challengeToken` and signature to `/v1/operations/{id}/dispute-actions`.
4. Writes and retries return only an action acknowledgment; a fresh signed `read` returns the current private evidence.

Expired cases retain a minimal tombstone and cannot reopen. Buyer closure preserves seller responses; result expiry does not undo confirmed settlement. The same flow supports private evidence reads. For Work Tickets use `ticket.payment.operationId` from the HTTP/MCP ticket response (or `payment.operationId` on the SDK ticket object).

Payment, delivery, existing receipts and the complaint remain separate; silence never means acceptance. Response targets do not establish a delivery deadline. No arbitration or automatic refund.

[Full flow, limits and retention](/delivery-disputes.md). Hosted MCP tools: `create_delivery_dispute_challenge`, `submit_delivery_dispute_action`. SDK helpers are published in SDK 0.6.0.
