Skip to content
sinc-LLMBook a 15-minute call

When Should an AI Agent Ask a Human to Approve a Refund?

Work through a refund approval decision using the captured payment, prior refunds, pending amounts and the AI agent’s cumulative order limit.

On this page

By Mario Alexandre · November 18, 2026 · 8 min read

The short answer is to ask a supervisor when an eligible refund would push the order’s total over the agent’s limit. Count completed and pending refunds first. Block duplicate claims, changes of payment destination and requests above the remaining balance, even if a supervisor is available.

How the order limit changes a refund decision

A refund approval limit is the most a merchant lets its agent return on an order without a person signing off. Suppose a customer opens a chat about a damaged mixing bowl. The support agent refunds $15. An hour later, the customer emails a photo of a cracked serving plate from the same order and asks for $20. The supervisor sees a $20 request, but approving it would bring the order total to $35.

In this fictional merchant policy, order 4817 had one captured payment of $80. Support has verified both damaged items and their eligible credit amounts. All amounts are in US dollars. The merchant lets its agent refund up to $25 in total per order to the original payment method. A support supervisor can approve a larger total up to the amount captured. These are example thresholds chosen for this merchant.

  1. Start with the captured payment. Subtract completed refunds and amounts already reserved for unsettled refunds. Each refund belongs in one of those buckets.
  2. Check the proposed refund against that available balance, then compare the cumulative refund total with the agent’s $25 limit. A request awaiting review has no reservation under this policy.
  3. When the supervisor acts, recheck the available balance. Reserve the approved amount before submitting it to the processor.
What happens on order 4817 Decision and who makes it What the support team sees
The customer requests $15 for the bowl. Allow. The refund tool calculates $0 + $15 = $15, within the $25 automatic limit. Once the processor confirms completion, $15 has been refunded and $65 remains available.
A second ticket repeats the bowl claim. Block a second refund. The tool matches the ticket to the completed bowl credit. A new ticket number does not create a new entitlement. Link the existing $15 refund to both tickets. The available balance stays at $65.
The customer requests $20 for the plate. Review. This is a separate eligible item, but $15 + $20 = $35. A support supervisor can approve or decline the $20 credit. While the decision is open, $65 remains available. On approval and reservation, $45 remains available.
Someone changes the requested destination to another card. Block the change. The tool requires the original payment destination even with supervisor approval. Keep the existing $20 instruction tied to the original payment. Send the customer to a payment specialist if they need help with that method.
The original $20 refund was submitted, but the payment response is pending. The approved ticket reopens. Block another submission. The tool returns the existing refund reference. The payments team checks that operation with the processor. $15 is confirmed, $20 is reserved and $45 is available. Tell the customer the $20 refund is pending.
The processor confirms the $20 refund. The approval is presented again. Block another submission. The tool returns the completed result for the same operation. Move $20 from reserved to completed. A total of $35 has been refunded, and $45 remains available.

What evidence does a refund supervisor need?

On the review screen, ask “Approve a $20 refund for the cracked plate on order 4817 to the original card ending in 1142?” Put the photo, eligible item value and earlier bowl credit beside the buttons. Show the consequence in dollars alongside the amount. “$15 already refunded. Approving brings the total to $35 and leaves $45 available.” A decline should close the request with a reason the next support rep can read.

Save the details the supervisor saw with the decision.

Field Example value
Decision Approved by supervisor S17 at 14:05 UTC on November 18, 2026. Valid for first submission until 14:20 UTC that day.
Exact operation Refund request R2, order 4817, captured payment P1, original payment destination P1 (card ending in 1142), USD 20.00.
Basis Damaged serving plate, one unit, case C92, photo and item value verified. Merchant refund policy v3.
Balance at review USD 80.00 captured, USD 15.00 completed, USD 0.00 reserved. The supervisor authorized USD 20.00 for R2.
Payment outcome Recorded separately under R2 as the processor responds.

Use the stored payment reference to identify the destination. The last four digits help a supervisor recognize the card. When work resumes, check the precise operation, current policy, supervisor authority, expiry and available balance together. If the facts supporting the decision changed, hold the request for a fresh decision. Record the reservation and claim the operation for submission in one transaction so two workers cannot both spend the same balance. Use that operation’s stable identifier for any processor interaction that supports idempotency.

How to avoid a second refund after a timeout

If the response is lost, keep the $20 reserved while payments reconciles R2. Expiry limits the first submission. It does not release money already in flight. A confirmed failure with no refund releases the $20 and restores the available balance to $65. A confirmed completion leaves $45 available. The broader guide to human approval workflows covers how to preserve a decision through a pause and restart.

Final checks before granting refund access

Run these cases with synthetic payments in the supported integration. Check both the decision shown to support and the count of distinct refund operations at the payment destination.

Test Passing result
Try a first eligible credit of $25.00, then test $25.01 on a fresh copy of the order. $25.00 can submit automatically. $25.01 waits for a supervisor with zero submissions.
After the $15 bowl refund, request $20 for the plate and have the supervisor decline. The tool requests review. Declining leaves $65 available and creates no plate refund.
Repeat the bowl claim from a different ticket. Support sees the original refund reference. The processor still has one $15 refund.
Change the destination or amount after approval, or resume an unused approval at 14:21 UTC. Each case creates zero new payment operations. The altered destination is blocked. An eligible revised amount or expired approval requires a fresh decision.
Resume the valid $20 approval twice at the same time, then simulate a missing processor response. One $20 operation and one $20 reservation. The queue shows pending and the available balance is $45.
Deliver the completion for that same operation twice. The ledger shows $35 completed, $0 reserved and $45 available. Reopening R2 returns its completed result.
With $45 available, request $45.01. The tool blocks the request before submission, even if a supervisor is willing to approve it.

A support rep should be able to close the plate ticket once the record shows who authorized the $20 and what happened to it. Until the processor confirms the refund, the customer-facing answer is “Your $20 refund was approved and is pending.” After confirmation, the rep can give the customer the refund reference without sending another payment.

Which refund requests should your agent hold for a supervisor? Agent Action Gate checks your rule before the agent uses the refund tool. The build includes tests with synthetic payments in the agreed integration. Bring your tool name, approval limit and one request the agent should hold.

Book a 15-minute call about refund approvals · Request an estimate by email

Frequently asked questions about refund approvals

What if the customer replaced the card used for the purchase?

For a Stripe payment, submit the refund against the original charge. The issuer usually routes it to the replacement card. If the customer cannot locate the credit, the payments team can check the refund status and give them a reference when available.

What should we ask a vendor to demonstrate if supervisors also refund orders in a separate dashboard?

Have a supervisor refund an item in the dashboard while an agent holds a second request for the same order. Ask the vendor to show when the agent sees the first refund and which balance it uses before submitting the second. If the agent cannot establish the remaining balance, route the order to the payments team for reconciliation.

Sources

Stripe explains how issuers handle refunds to replaced cards. The $25 approval threshold and 15-minute window in the worked example are settings the merchant chose for its own support team. Stripe’s guide to refund destinations