News

Returns and refunds in agentic commerce: who handles what?

AIR
November 20, 2026

In agentic commerce, an AI agent may help request a return, but the merchant still needs an operational process for deciding the request, receiving goods and arranging the financial outcome. Permission to buy should not automatically be treated as permission to accept store credit, choose a replacement or change a refund destination. Each action needs an accountable owner and a record of what the customer agreed to.

The commercial test extends beyond a successful checkout. A customer who buys through an agent should be able to resolve a problem without reconstructing the purchase from a chat history or being passed indefinitely between an assistant, merchant and payment provider.

Keep the return and the refund separate

A return concerns the goods and their movement back to the merchant. A refund concerns a financial adjustment. The two may be linked, but their timing and conditions can differ. A merchant might approve a return before receiving a parcel, issue a partial refund without requiring return shipping, or offer an exchange that needs another inventory decision.

Commerce systems already represent these separately. Shopify’s July 2026 returnCreate API creates an open return and a reverse fulfillment order after approval is assumed. Its July 2026 refundCreate API handles financial refunds, including full or partial amounts and associated order records. An agent-facing interface should preserve the distinction rather than collapse both into “resolved.”

These examples describe product capabilities, not a universal allocation of legal liability. The operating model below is a merchant design framework; applicable terms and jurisdiction determine obligations in a particular case.

Follow one purchase through the problem

Consider an illustrative order for a blue jacket and a travel bag. The agent correctly buys both. The jacket arrives in the wrong size, while the bag is satisfactory. The customer asks the agent to return the jacket and keep the bag.

The merchant needs the original order, the jacket’s line-item reference, the delivered item, the customer’s requested remedy and the current return status. The agent needs a usable response: whether more evidence is required, whether a label is available, what the customer must do, and when the next update should arrive.

The bag should remain unaffected. If a bundle discount or shipping promotion changes the amount repayable, the merchant should explain the calculation before the customer accepts a proposed resolution. An opaque refund amount can turn a simple sizing problem into a dispute about the original offer.

For merchants evaluating discovery and purchase together, our guide to how shopping agents rank products explains why an offer’s conditions matter before selection. Support should be able to recover those same conditions after purchase.

Assign an owner to each decision

The customer supplies the desired outcome and approves material changes. The agent can collect the required information and communicate within its granted authority. The merchant’s return process decides the operational request, including any review required by its policies and applicable obligations. The warehouse or logistics partner records receipt and inspection. The payment workflow records the financial adjustment and its result.

One service team should own the case across those handoffs. Ownership does not mean that team performs every step. It means the customer has a clear route when a label fails, a parcel is lost, or the financial outcome does not match the decision.

For the jacket, support should see “return approved; awaiting carrier scan,” not just “refund requested.” If the parcel is received but inspection is pending, the next action belongs to the inspection workflow. If the financial instruction failed, the next action belongs to the payment workflow. The case remains open until the promised outcome is established or the customer has a clear explanation of the remaining issue.

Check authority again when the remedy changes

Buying a jacket and accepting a replacement are different decisions. The replacement could be a different size, color, price or delivery date. Store credit may restrict where and when the customer can spend. A return request may disclose additional customer information.

Define which post-purchase actions the agent may perform without another interaction. Reading order status, preparing a return request and accepting a financial settlement should not be treated as equivalent permissions. Where existing authority does not cover the proposed remedy, ask the customer to decide and preserve that decision with the case.

Revoking an agent should stop the future actions covered by that revocation. It should not erase the customer’s access to the purchase or silently cancel a case already in progress. Our guide to spending limits, expiry and revocation explains the distinction between stopping authority and reversing a transaction.

Preserve evidence without copying everything

Retain the information needed to explain the purchase and resolve the case: the accepted offer, affected line items, relevant policy version, customer request, permission decision, status changes and financial references. Keep access and retention aligned with the purpose of the case. A complete copy of every agent conversation may add sensitive information without improving the decision.

The Universal Commerce Protocol Order specification, version April 8, 2026, separates purchased items, fulfillment and post-order adjustments. That separation supports a useful operating principle: a refund event should not overwrite the evidence of what was originally ordered or shipped.

For the jacket, a support specialist should be able to distinguish the model the customer requested, the variant the agent submitted, the merchant’s accepted order and the item actually delivered. Each points to a different failure and a different improvement. “The AI got it wrong” is too broad to guide either remediation or product changes.

Make escalation part of the customer journey

Before launching, test a partial return, a failed refund instruction, an expired agent permission and a customer who switches to human support. The receiving team should get the existing case reference and relevant evidence rather than asking the customer to begin again.

Measure how many cases need manual reconstruction and how long each stage remains unresolved. Faster replies are valuable only when the underlying case progresses. A polite agent repeatedly reporting the same pending status can hide an ownership gap.

AIR Agent brings customer identity and delegated credential presentation into agent interactions. Merchants should connect that identity context to the appropriate support process while defining return decisions, payment execution and escalation within their own operating model.

Frequently asked questions

Can an AI agent request a return?

It can do so where the merchant supports the action and the customer has granted appropriate authority. A request is separate from the merchant’s decision and the eventual financial outcome.

Does permission to purchase include permission to accept store credit?

It should not be assumed. Store credit changes the remedy offered to the customer. Check whether the granted authority covers that decision or request approval.

Is a return approval the same as a completed refund?

No. Return approval, receipt of goods, inspection, refund initiation and the final financial outcome are separate stages that may occur at different times.

What evidence should an agent-assisted return preserve?

Preserve the order and affected line items, accepted terms, customer request, relevant authority, case status and financial references. Limit personal information to what the workflow needs.

What if the customer stops using the original agent?

Provide a merchant support route that can recover the order and active case after appropriate checks. Continued access to the purchase should not depend entirely on one agent session.

Partner with AIR

Designing customer recognition across agent-assisted purchases and service? Talk to AIR about the identity and credential context your business needs.

Moca Network, the identity network of Animoca Brands.

Partner with AIR

AIR is one integration suite for identity, money and loyalty. AIR Identity lets trusted issuers issue verifiable credentials and businesses verify them, so acquisition starts with users who already qualify, with minimal data custody. AIR Money embeds compliant global financial infrastructure, opening new markets without building new rails. AIR Loyalty gives brands a programmable, stable-value points engine that keeps users coming back.

Partner with us to grow your business.

AIR is built by Moca Network, the identity network of Animoca Brands.

Stay updated on AIR launches
Product updates, partner launches, and research across digital identity, fintech, and loyalty. Unsubscribe anytime.
By subscribing, you agree to our Privacy Policy and consent to receive updates.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
In this article
Blog

Read more articles

View all
AI-generated photorealistic scene of an adult reviewing an AI account-data access request on a laptop alongside third-party AI terms; generic illustrative interface, not a real bank or AIR product screen.
News
AI banking agents and liability: what changed, what rights remain
What new bank AI-agent terms mean, when they take effect, which consumer rights remain, and why identity checks differ from permission to move money.
AI-generated photorealistic scene of two merchants scanning and weighing one test parcel beside a limited batch and a physical pilot test-order card.
News
How to launch an agentic commerce pilot that earns its next phase
Plan an agentic commerce pilot with a focused customer task, four launch gates and a commercial case based on contribution, support and returns.
AI-generated editorial illustration of a white shopping cart suspended above a silver coin stack on a white plinth.
News
How to measure agentic commerce: a merchant KPI framework
Measure agentic commerce from AI visibility to accepted orders and retained contribution, with clear denominators and an illustrative merchant funnel.