{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/",
    "json": "https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 4 | 24 | 12 | 3 |\n\n## What counts as done\n\nThe 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).\n\nHow 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\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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).\n\n## What stops agents finishing\n\n- no idempotency key or replay rule, so a sequential retry pays twice\n- receipt format in docs differs from what the verifier accepts\n\n## Around it\n\nBefore: pay-per-call.pay-and-retry. After: agent-observability.cost-report, accounting.record-expense.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Confirm a payment settled, recover an unknown outcome and keep a receipt",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Confirm a payment settled, recover an unknown outcome and keep a receipt",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/pay-per-call.settle-and-prove/",
    "published": "",
    "section": "agents",
    "title": "Confirm a payment settled, recover an unknown outcome and keep a…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/pay-per-call.settle-and-prove/"
  },
  "tokens": {
    "markdown": 900,
    "slim": 280
  },
  "version": 1
}
