# Confirm a payment settled, recover an unknown outcome and keep a receipt

> Confirm a payment settled, recover an unknown outcome and keep a receipt: 0 companies fully do it, 4 with a limit, 24 carry the tag. Every listing in Pay-per-call protocols with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/
- Markdown: https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/index.md (~900 tokens)
- Slim: https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 4 | 24 | 12 | 3 |

## What counts as done

The agent can tell from documented fields whether the payment settled, look it up by transaction or idempotency key before paying again, and keep a receipt a third party can verify (transaction hash, preimage or signed credential).

How agents ask for it: did that payment go through; retry without paying twice; show me the receipts for this run; prove I paid for this

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **ACK-Pay (Agent Commerce Kit) (Catena Labs, Inc.)**: Receipts are W3C Verifiable Credentials signed by a Receipt Service and verifiable offline against its DID. The docs show an Ed25519Signature2020 proof while the verifier accepts only JwtProof2020 (acc-24, open), and there are no settlement status codes or idempotency key.
- **L402 (Lightning Labs, Inc.)**: The preimage proves payment to anyone (sha256 matches the payment hash), and lnget caches tokens per domain so a later call reuses the paid credential. Handling of an in-flight or timed-out Lightning payment before retrying is not documented.
- **Machine Payments Protocol (MPP) (Tempo and Stripe)**: Payment proofs MUST be single-use, concurrent requests with one credential MUST settle once, and Payment-Receipt carries status, method, timestamp and a tx hash or invoice reference. Receipts exist only on success, and Idempotency-Key for paid POSTs is a SHOULD, so a lookup before re-paying depends on the server.
- **x402 (x402, a Series of LF Projects, LLC)**: SettleResponse carries success, errorReason and the transaction hash, settlement_pending is non-terminal with the broadcast hash required, and the payment-identifier extension is an idempotency key. The extension is optional, and facilitator-unavailability semantics are undefined (acc-25).

## What stops agents finishing

- no idempotency key or replay rule, so a sequential retry pays twice
- receipt format in docs differs from what the verifier accepts

## Around it

Before: pay-per-call.pay-and-retry. After: agent-observability.cost-report, accounting.record-expense.

## Where this comes from

Weight 12 of 100 in Pay-per-call protocols: 3 of 25 accounts (acc-17, acc-24, acc-25), two of them implementer issues; set low because few users report reaching this step

As data: https://www.anchorterminal.com/api/v1/use-cases/pay-per-call.settle-and-prove.json, or the MCP tool get_use_case with id pay-per-call.settle-and-prove. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
