{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/commerce.refund-or-cancel/",
    "json": "https://www.anchorterminal.com/niches/commerce.refund-or-cancel/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/commerce.refund-or-cancel/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/commerce.refund-or-cancel/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 | 17 | 20 | 5 | 2 |\n\n## What counts as done\n\nOne refund created for no more than the refundable balance, read back by ID with matching amount and status, and no second refund or charge after a retry.\n\nHow agents ask for it: refund this order; cancel and refund the damaged item; issue store credit for this return\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- **Adobe Commerce (Magento) (Adobe Inc.)**: POST /V1/order/{id}/refund and /V1/invoice/{id}/refund create a credit memo and update the order in one call, but no quote step or idempotency key is documented, so a retry can refund twice.\n- **BigCommerce API + MCP (Commerce.com US, Inc.)**: get_refund_quote then create_refund re-quotes and refuses on mismatch, but create_refund has no idempotency and the docs say a second submit can refund twice; readback is through get_orders refunded amount.\n- **Commerce Layer API + MCP (Commerce Layer, Inc.)**: Orders carry a refund trigger and webhooks fire orders.refund, but the docs read show no quote step, and earlier reading found no confirmation on the MCP's delete tool.\n- **commercetools (commercetools GmbH)**: Payments and transactions are tools, but a refund is a transaction with no quote step, and writes use optimistic version checks rather than idempotency keys, so a retry after a timeout must re-read first.\n- **Elastic Path API + MCP (Elastic Path Software Inc.)**: Refund a Transaction refunds through the gateway or marks a refund recorded elsewhere, but there is no quote, no idempotency key and no read-only or confirmation mode on the MCP.\n- **Fabric (Commerce Fabric, Inc.)**: check-return-eligibility, check-credits-eligibility and appeasement actions guard refunds and credits, but no idempotency key appears anywhere in the Orders reference, so a retry can repeat a credit.\n- **Medusa API + MCP (MedusaJS, Inc.)**: Admin payment refunds exist over the API, but no idempotency header is documented in the reference, and a closed issue shows refund retries once sent a new provider key.\n- **Saleor API + MCP (Saleor Commerce sp. z o.o.)**: Refunds run only through run_high_impact_mutation after approval, but an idempotency key appears on transaction events, not on the refund mutations an agent sends, so retry safety is not documented.\n- **Shopify API + MCP (Shopify Inc.)**: refundCreate requires an @idempotent key from 2026-04 and returns the refund and refunded total, so retries are safe. The page shows no quote step, and a forum thread says caps must sit inside the refund tool.\n- **Shopware (shopware AG)**: shopware-order-state takes transactionAction refund with a dry run, but that is a state transition whose money movement depends on the payment plugin, with no amount, quote or idempotency key.\n- **Snipcart API + MCP (Snipcart inc.)**: The MCP views and creates refunds, but no quote, confirmation or idempotency key is documented, so a retried refund is not guarded.\n- **Spree Commerce (Vendo Connect Inc)**: returns_refund and refunds through create_resource exist with client confirmation, but no refund quote or idempotency for admin writes was found in the tool reference.\n- **Square (Block, Inc.)**: The refunds service takes an idempotency key, but the same tool-description flaw means a retried refund or payment can get a fresh key, and no quote step is documented.\n- **Swell (Swell Commerce Corp.)**: The Backend API issues and lists refunds, but no MCP tool refunds and no idempotency key is documented; cancel_order refunds nothing and points to the dashboard.\n- **Vendure (Elevantiq GmbH)**: refund_order defaults to the payment's remaining refundable balance behind a confirm step, but carries no idempotency key, so a retried call can refund again.\n- **Wix Stores and eCommerce API (Wix.com Ltd.)**: calculate-refund and get-order-refundability give a quote, and refund-payments caps quantities and amounts at the refundable balance, but no idempotency key is documented on the refund call.\n- **WooCommerce API + MCP (WooCommerce, Inc.)**: REST POST /orders/{id}/refunds creates and returns a refund, but takes no idempotency key and no MCP refund ability is listed, so a retry can refund twice.\n\n- not this job: Agentzon (Merit Systems Inc (agentzon.co terms); Merit Systems, Inc. (merit.systems terms)): No refund or cancel endpoint; refunds and cancellations go by email to the seller's support address.\n- not this job: doola MCP (doola): No refund or cancel tool is published.\n- not this job: Ecwid by Lightspeed (Ecwid, Inc.): Orders show refunds and refundedAmount, but no refund endpoint is listed in the REST reference; changing paymentStatus doesn't move money.\n\n## What stops agents finishing\n\n- refund tool with no quote or confirmation step\n- retry creates a second payment or refund\n\n## Around it\n\nBefore: commerce.order-lookup, support.ticket-in. After: payments.refund, support.reply.\n\n## Where this comes from\n\nWeight 5 of 100 in Commerce \u0026 checkout: 2 of 49 accounts (Square idempotency issue, Shopify refund-guardrails thread) plus BigCommerce and Shopware listing notes; few accounts but the costliest failure\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/commerce.refund-or-cancel.json, or the MCP tool get_use_case with id commerce.refund-or-cancel. 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": "Refund, cancel or return an order safely",
        "url": ""
      }
    ],
    "description": "Refund, cancel or return an order safely: 0 companies fully do it, 17 with a limit, 20 carry the tag. Every listing in Commerce \u0026 checkout with the reason and a source.",
    "facts": null,
    "h1": "Refund, cancel or return an order safely",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/commerce.refund-or-cancel/",
    "published": "",
    "section": "agents",
    "title": "Refund, cancel or return an order safely | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/commerce.refund-or-cancel/"
  },
  "tokens": {
    "markdown": 1600,
    "slim": 380
  },
  "version": 1
}
