# Refund a payment or answer a dispute without doing it twice

> Refund a payment or answer a dispute without doing it twice: 0 companies fully do it, 4 with a limit, 16 carry the tag. Every listing in Payment & monetisation platforms with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/payment-platforms.refund-and-dispute/
- Markdown: https://www.anchorterminal.com/niches/payment-platforms.refund-and-dispute/index.md (~1,300 tokens)
- Slim: https://www.anchorterminal.com/niches/payment-platforms.refund-and-dispute/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/payment-platforms.refund-and-dispute/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 | 16 | 17 | 4 |

## What counts as done

One refund or dispute action is applied, a timeout is reported as unknown rather than failed, an idempotency key or a read of the payment's refunds lets the agent check before retrying, and the tool asks for or records a person's approval for destructive writes.

How agents ask for it: refund order 412; issue a partial refund; respond to this chargeback; accept the dispute

## 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.

- **Adyen MCP server (Adyen N.V.)**: A refund tool exists, but open issue 149 shows it sends no Idempotency-Key, reports a timed-out refund as failed and has no refund read-back, so an agent can refund twice. No dispute tools.
- **Lago (Get Lago Corp.)**: Refunds go through create_credit_note and its refund status, collected by the connected processor; there are no dispute tools, and no idempotency key for these writes was found in the pages read.
- **PayPal MCP server (PayPal, Inc.)**: create_refund, get_refund, list_disputes, get_dispute and accept_dispute_claim exist. The only PayPal-Request-Id comes from a fixed context value, not a per-call key, and no approval step guards refunds or accepting a claim.
- **Stripe API + MCP (Stripe, LLC)**: Create refund carries Human confirmation with a 24-hour approval, refunds can be listed per charge and disputes updated. An open issue reports a framework retry becoming a new invocation with a new idempotency key and charging twice (acc-13).

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Payman Genie MCP (Payman AI, Inc.)**: Docs host unreachable; the README does not say whether Genie refunds or handles disputes.

- not this job: ATXP (Circuit & Chisel, Inc.): No refund or dispute call in the docs read.
- not this job: Circle Gateway Nanopayments (Circle Technology Services, LLC): No refund or dispute operation in the nanopayments docs read; failed transfers are simply never charged.
- not this job: Crossmint API + Docs MCP (Crossmint, Inc.): No refund or dispute tools for a merchant.
- not this job: FluxA AgentMarket (FluxA Technology Pte. Ltd.): No refund or dispute call for a merchant; a failed top-up order is dead and a new one is created.
- not this job: Metronome (Stripe, LLC): Credit memos adjust invoices, but refunds and disputes happen in the payment processor; Metronome has no refund or dispute call.
- not this job: Nevermined API + MCP (Nevermined AG): No refund or dispute tool in the Catalog MCP or Router docs read.
- not this job: Orb (Orb, Inc.): Credit notes adjust invoices; refunds and disputes stay with the payment processor, and no refund or dispute tool is listed.
- not this job: Paid (Agent Paid Limited): No refund or dispute endpoint or tool in the docs index; payments sit in the connected Stripe account.
- not this job: Skyfire API + MCP (Skyfire Systems Inc.): No refund or dispute endpoint in the API reference index; the Charge Token reference documents no idempotency key.
- not this job: Tempo (Tempo Labs Inc.): Refunds are a guide for sending a new stablecoin transfer from the builder's own records; no refund or dispute call.
- not this job: TermiX AACP (TermiX): Buyer refunds come only from cancelPending or cancelExpired on an order and disputes go to an evaluator panel; there is no merchant refund or chargeback tool.

## What stops agents finishing

- no idempotency key on refund or charge tools
- a retry as a new tool invocation gets a new key
- dispute tools missing from the server

## Around it

Before: support.read-ticket, payment-platforms.look-up-payments. After: support.reply-customer.

## Where this comes from

Weight 17 of 100 in Payment & monetisation platforms: 4 of 23 accounts (acc-11 to acc-14); acc-12 read eight platforms' toolkits and found five can charge twice

As data: https://www.anchorterminal.com/api/v1/use-cases/payment-platforms.refund-and-dispute.json, or the MCP tool get_use_case with id payment-platforms.refund-and-dispute. 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
