Niches · Commerce & checkout

Refund, cancel or return an order safely

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

0companies, full fit
17companies, fit with a limit
20companies carry the tag
5share of the category's work
2first-hand accounts

What counts as done

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

How agents ask for it: refund this order, cancel and refund the damaged item, issue store credit for this return

Does the job, with a limit 17

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.

ListingWhy
Adobe Commerce (Magento) D
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. source
BigCommerce API + MCP B
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. source
Commerce Layer API + MCP B
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. source
commercetools BB
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. source
Elastic Path API + MCP C
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. source
Fabric E
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. source
Medusa API + MCP C
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. source
Saleor API + MCP BB
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. source
Shopify API + MCP BB
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. source
Shopware BB
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. source
Snipcart API + MCP D
Snipcart inc.
The MCP views and creates refunds, but no quote, confirmation or idempotency key is documented, so a retried refund is not guarded. source
Spree Commerce BB
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. source
Square B
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. source
Swell C
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. source
Vendure BB
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. source
Wix Stores and eCommerce API B
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. source
WooCommerce API + MCP BB
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. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
Agentzon D
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. source
doola MCP F
doola
No refund or cancel tool is published. source
Ecwid by Lightspeed C
Ecwid, Inc.
Orders show refunds and refundedAmount, but no refund endpoint is listed in the REST reference; changing paymentStatus doesn't move money. source

What stops agents finishing

  • refund tool with no quote or confirmation step
  • retry creates a second payment or refund

Around it

Before: commerce.order-lookup, support.ticket-in. After: payments.refund, support.reply.

Where this comes from

Weight 5 of 100 in Commerce & checkout: 2 of 49 accounts (Square idempotency issue, Shopify refund-guardrails thread) plus BigCommerce and Shopware listing notes; few accounts but the costliest failure

The same as data: /api/v1/use-cases/commerce.refund-or-cancel.json, or the MCP tool get_use_case with id commerce.refund-or-cancel. Other jobs in this category: /api/v1/niches?category=commerce.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.