Blog

If an AI shopping agent buys the wrong item, who ends up paying?

Authorization, billing-error and return rights when software buys for you, why the rules are unsettled, and how to cap what an agent can spend.

Short answer: it depends on what you told the agent to do, what it actually bought, and whose card details it used. If the agent did something you did not authorize, a credit card dispute is possible, and federal law caps your liability for truly unauthorized use. If the agent did what you asked, only badly, you are mostly in ordinary return-policy territory and the card gives you fewer levers. The honest middle is that no one has settled where every case falls, because the rules were written for people and for cards, not for software acting on a person's behalf. This article takes the questions a cardholder is likely to have, one at a time, and says what is known, what is unsettled and what you can do before anything goes wrong.

One framing note. Nothing here relies on a rule written specifically for AI agents. The sources behind this site do not include one, so the answers apply general card rules (the Fair Credit Billing Act, the liability cap, network dispute practice) to a new situation. How a given issuer or court treats a given agent purchase can differ from the reading below, so treat it as a map of the questions, not a prediction of the outcome.

What do people mean by an "AI shopping agent"?

The term is used loosely. In the narrow sense, agentic commerce means software that can take a goal ("reorder the printer paper," "find a rain jacket under a set price") and carry it out across several steps, including paying, without you clicking through each page. What it means when an AI assistant shops and pays for you explains the moving parts. For this article, what matters is how much of the decision you handed over and what payment credential the software could reach.

There are roughly three setups, and the answers change with each:

  • Suggest only. The assistant finds items and builds a cart. You press the buy button and approve the payment yourself. Nothing here is new: you made the purchase.
  • Approve each purchase. The agent completes everything up to the last step, then asks you to confirm the item, the price and the card. You approve in your own interface.
  • Act within limits. You give the agent standing permission: a budget, a merchant list, a category. It buys when conditions are met and tells you afterward.

Most of the hard questions sit in the third setup, and some in the second when the confirmation screen is vague.

If the agent buys something I did not ask for, is that an "unauthorized" charge?

Possibly, but the word has a narrower legal meaning than it has in everyday speech. Federal law caps a cardholder's liability for unauthorized card use at $50, and the issuer carries the burden of proving the conditions for even that amount. If only the account number was misused rather than a stolen physical card, the cardholder generally has no liability under federal law, according to the CFPB. A card network or issuer "zero liability" policy can go further than the law, but its terms are set by the network and issuer, not by statute.

The difficulty is the definition. As the Truth in Lending Act is generally understood, use is unauthorized when it is made by someone with no actual, implied or apparent authority, and the cardholder gets no benefit. The phrase "apparent authority" is the crux for agents. If you handed an agent your card details and a standing instruction to buy things, an issuer could argue that the agent had authority to buy, even if it bought something you did not mean. If instead the agent used a credential you never gave it, or bought from a merchant outside your stated limits, the case for "unauthorized" looks stronger.

There is no clean answer, and this is where the details of your setup matter. Three questions help sort the cases:

  1. Did you give the agent this card, or did it get the details some other way?
  2. Did the purchase fall inside the limits you set (amount, merchant type, category)?
  3. Did you approve the specific purchase on a screen that showed the item and the price?

A "no" to the first or second leans toward unauthorized. A "yes" to the third leans toward authorized, even if the screen was confusing. If you are unsure, report it as a problem and let the issuer decide; do not decide for them by staying quiet.

What if the agent bought exactly what I asked for, but it was the wrong thing?

This is the most common case and the least favorable one for the cardholder. Say you asked for "a 12-pack of printer paper" and the agent bought a 12-pack of the wrong size. From the issuer's point of view the charge was authorized: you told the software to buy paper, it bought paper, the merchant delivered what was ordered. The error was in the translation between your intent and the order. The legal term billing error covers a defined list of problems, among them charges you did not make, charges for goods not delivered as agreed and math mistakes. A mismatch between what you meant and what you ordered is not on that list unless the merchant also failed to deliver what the order said.

That does not leave you with nothing. It moves the question to the merchant's return policy, which is where most wrong-size, wrong-color and duplicate-order cases end up resolved. billing error or a purchase gone wrong: which dispute rights apply? sets out the difference between a billing error and a bad purchase in more detail.

A worked example

Say Priya tells an agent to buy printer paper, and it buys the wrong size. These figures are an illustration, not market data.

  • Item price: $58.40
  • Shipping charged: $9.99
  • Total charged to the card: $58.40 + $9.99 = $68.39

The merchant's return policy, in this made-up case, refunds the item price less a 15 percent restocking fee and does not refund original shipping.

  • Restocking fee: 15 percent of $58.40 = $8.76
  • Refund: $58.40 - $8.76 = $49.64
  • Money not recovered: $68.39 - $49.64 = $18.75 (that is $8.76 plus $9.99)

Priya's loss is $18.75 if she returns the item within the window and pays for no return label. The card did not make her whole, because nothing was wrong with the charge. She also has a time pressure: the return window runs from delivery, not from the statement date. If she needs to return a sealed box, the sooner the better.

What if the merchant ships something different from what the agent ordered?

Then the ordinary rules apply, whether or not an agent was involved, and the Fair Credit Billing Act procedure is the one to use. If the charge is for goods or services not delivered as agreed, that can be a billing error. A written billing-error notice must reach the card issuer within 60 days after the statement showing the error was sent. The issuer must acknowledge in writing within 30 days (unless it resolves the matter sooner) and resolve it within two complete billing cycles and no later than 90 days. While the matter is under investigation, the creditor may not try to collect the disputed amount or report it as delinquent. The 60-day deadline is for the written notice, and a phone call alone may not trigger the statutory protections, though many issuers accept disputes by phone or in an app as a courtesy. How to write a billing error letter under the Fair Credit Billing Act covers the letter, and the billing dispute letter builder assembles one.

There is also a separate claim, covered in the CFPB's guidance, about a defective purchase. It generally requires the purchase to be over $50 and made in the cardholder's home state or within 100 miles of the billing address, after a good-faith attempt to resolve it with the merchant. An online purchase that arrives from out of state may not fit those conditions neatly, so do not assume it applies. The card network's own dispute system, described next, is often the more practical route.

What does a chargeback add?

A chargeback is the network-level process. The cardholder disputes a charge with the issuer, which can provisionally credit the account, send a dispute through Visa or Mastercard's system and let the merchant respond. The network rules are private contract rules between the banks and networks, not federal law, and the filing windows come from them. Vendor guides commonly describe a window of about 120 days from the transaction or the expected delivery date, with shorter and longer windows for some reason codes. Those figures come from vendor guides, not from the rulebooks, so treat them as typical and not exact.

Two practical points. First, the federal 60-day notice and the network window are separate clocks, and the federal one is often the shorter, so the safer habit is to act on the earlier of the two. Second, network dispute codes group disputes into fraud, authorization errors, processing errors and customer disputes such as item not received or not as described. "My agent bought the wrong thing" does not fit those codes well, which is why a dispute that stresses what the merchant did (shipped something other than what was listed, did not ship, refused a return that its own policy allowed) tends to fit better than one that stresses what the agent did. a chargeback from dispute to final decision: who does what, and when walks through the stages.

Who is responsible, you, the agent's maker or the merchant?

Three parties could in principle bear a loss, and the usual allocation is this:

  • You, for purchases you authorized or that fall inside permissions you gave. Terms of service for assistants typically say that the user is responsible for what the tool does on the user's instructions. Read the service's terms before granting purchasing power, and look for any section on errors, refunds or spending limits.
  • The merchant, for failing to deliver what was ordered, for deceptive listings, or for refusing to honor its own return policy.
  • The company behind the agent, for a malfunction, such as buying something you never asked for, only if its terms or a law put the loss there. Whether and when that happens is the unsettled part. Do not assume the assistant's maker will reimburse you. Ask, and keep the reply.

None of these is a promise. They describe where responsibility usually starts, not where every dispute ends.

How do I limit what an agent can spend before anything goes wrong?

Most of the protection is in setup, not in dispute rights after the fact. A checklist:

  1. Prefer the approve-each-purchase mode for anything beyond small, repeat purchases. A confirmation screen that shows the item, the quantity, the final price with shipping and the card is a useful record and a useful stop.
  2. Use a dedicated credential. A virtual card number is a separate card number issued for a merchant or purpose, which many issuers offer. If one can be given a spending limit, an agent that goes wrong runs into a ceiling instead of your whole credit line. If you cannot do that, consider a separate card with a low credit limit, so the most you can lose is the most you were willing to risk.
  3. Set a per-purchase and a monthly ceiling in the assistant itself, if it lets you, and set alerts on the card for every transaction so a purchase shows up on your phone within minutes.
  4. Restrict categories and merchants to the ones you actually want automated.
  5. Keep records. Save the instruction you gave, the confirmation screen and the order email. A dispute is easier to win with a dated record than with a recollection.
  6. Review the activity regularly. Check what the agent bought each week, not each quarter, since the return window and the dispute deadline both start running early.

The point of the list is not that agents are dangerous. It is that a card with no ceiling and an agent with broad authority is a combination that no one has yet tested in the dispute system.

What should I do right away if an agent buys the wrong thing?

A short order of operations, in the first day or two:

  1. Stop further buying. Pause or revoke the agent's access to the card or payment method.
  2. Look at the order itself. Is it cancellable before shipping? Many merchants let you cancel for a short time. Cancelling is faster than any dispute.
  3. Contact the merchant. Ask for a cancellation or a return and ask what the return policy is. Do it in writing where you can, and save the reply.
  4. Check the charge on the statement. Compare it with the order. If the amount differs from what the confirmation said, that is a billing error candidate.
  5. If the merchant will not help or the charge was not authorized, call the number on the back of your card and tell the issuer what happened, factually and in order. Then follow up in writing within the 60-day window.
  6. If you disagree with the result, you can file a complaint with the CFPB, which forwards complaints to companies and publishes the process on its website.

If at any point the situation looks like a scam rather than a mistake, for instance an "agent" or "assistant" that you never set up, or a caller who offers to "fix" a purchase and asks for remote access, stop. scam payment or unauthorized charge: why your protections can differ shows why the two cases are treated differently, and why a scam you were talked into can be harder to recover.

What is still unsettled?

Several things, and it is better to say so than to guess:

  • Whether a standing instruction to an agent counts as "apparent authority" for purposes of the liability cap.
  • Whether networks and issuers will adopt specific dispute codes or policies for agent-initiated purchases.
  • How merchants will treat orders placed by software, including return policies written for people.
  • Whether any federal or state rule will address it. As of November 2026, the sources for this site do not point to one.

Because the ground is moving, the safe posture is to assume that a loss caused by your own instructions will be yours and to arrange things so that the amount is small.

Key takeaways

  • A purchase that matches what you told the agent to do is usually treated as authorized, even if the result is not what you meant; a purchase outside your permissions is the stronger "unauthorized" case.
  • Federal law caps liability for unauthorized card use at $50, and a written billing-error notice must reach the issuer within 60 days of the statement; call the number on the back of your card first, then follow up in writing.
  • A wrong-size or wrong-color order is mostly a return-policy problem, as the $18.75 example shows, so cancel or return fast.
  • The best protection is setup: approve-each-purchase mode, a separate virtual card with a spending limit, transaction alerts and saved records.
  • No rule written for AI agents is known to this site as of November 2026, so how disputes are treated may differ by issuer; the CFPB complaint process is available if you disagree with an outcome.

Terms used in this article

Related tools

Latest on this topic