Prevención del fraude y Contracargos el comercio a través de agentes

Contracargos?
Ya no es problema tuyo.
Recupera cuatro veces más Contracargos y prevención , hasta un 90 % de las entradas, gracias a IA y a una red global de 20 000 comercios.
En resumen:
- Agentic commerce fraud is fraud, disputes and wrongful declines that occur when an AI agent, not the cardholder, completes checkout.
- Device, behavior and velocity signals break on agent orders, so verify the agent itself with signed requests, tokenized credentials and a recorded mandate.
- Score each order against its mandate and the customer’s history after checkout, and confirm with the customer before fulfillment when it deviates.
- Most disputes on legitimate agent orders trace to forgotten approvals and delegated mistakes, so store the agent ID and consent record as evidence.
- Chargeflow Prevent scans orders after checkout and before fulfillment, Alerts catch disputes before they become chargebacks, and Automation submits evidence for those that still go through.
Una guía práctica de Ben, estratega de fraude y devoluciones Chargeflowy mentor en el MRC
El comercio agentivo está redefiniendo las reglas del juego en materia de riesgos
Agentic commerce fraud is fraud, disputes and wrongful declines that occur when an AI agent, rather than the cardholder, completes the checkout. This guide is the operations playbook for legitimate agent orders: how to verify the agent, tokenize its credentials, score the order after checkout and be ready for the dispute. For attacks by malicious agents and spoofed bot traffic, read our guide to preventing AI agent fraud.
IA no solo influyen en las compras, sino que también están empezando a realizarlas. A medida que estos sistemas automatizados se hacen cargo de una parte cada vez mayor del proceso de compra, surgen nuevos problemas en cuanto a cómo los comerciantes detectan el fraude, interpretan la intención del cliente y evitan Contracargos.
Veo este cambio cada día. Los datos sobre reclamaciones revelan una tendencia al alza en el número de clientes que reclaman cargos derivados de decisiones automatizadas que no comprendían del todo o que no esperaban. A través de mi trabajo como mentor de equipos de lucha contra el fraude, mi participación en el Comité de Fraude del MRC y mi colaboración diaria con los departamentos de operaciones de los comercios, observo cómo tanto los clientes como los estafadores se están adaptando a esta nueva forma de comprar.
This guide focuses on issues already appearing in dispute queues, rather than predictions about the distant future. These cases show how quickly agent-driven purchasing is shaping post-purchase risk. Who ends up paying for those disputes is covered in our guide to AI agent chargeback liability.
Cómo cambia el comercio agentico la situación del fraude
Las herramientas tradicionales de detección de fraudes parten de la base de que detrás de cada acción hay una persona. Esa suposición empieza a tambalearse en el momento en que el comprador es un agente autónomo.
Visa’s own research on agentic commerce makes the same point: current payment infrastructure was designed around human interaction and will need to adapt (The Rise of Agentic Commerce). At Sibos on September 29, 2026, Federal Reserve Governor Christopher Waller described the authentication shift in his speech Payments in the Age of AI Agents: the question moves from proving that a buyer is an authorized payer to proving that an agent has the authority to pay on the buyer’s behalf. He added that fraud models and rules will need to be recalibrated for agent payment patterns.
A medida que los agentes adquieren un mayor control, muchas de las señales tradicionales pierden su fiabilidad. Las huellas digitales de los dispositivos, los patrones de los perfiles de comportamiento, las señales de fricción y las rutas de navegación se basan en comportamientos humanos. Ahora, los agentes actúan de formas predecibles y «coherentes con el funcionamiento de las máquinas» que los sistemas actuales no pueden procesar.
Intent becomes much harder to verify. Sometimes the customer expected the agent to take action, but not in the specific manner in which it was taken. Sometimes the agent acted on learned logic that the customer had overlooked or forgotten. Fraudsters are leveraging that lack of clarity. Legitimate customers are, at the same time, disputing charges because of their own confusion versus deliberate misuse. Stopping that loss means building chargeback fraud prevention into the order flow, not only the dispute queue.
El riesgo va mucho más allá del fraude. Existe una discrepancia cada vez mayor entre lo que esperan los clientes y lo que decide su agente.
The figures below explain why fraud teams now treat agent orders as their own risk class instead of a variation of card-not-present fraud.
$42B Projected global chargeback cost to merchants by 2028 | 1 in 10 Consumers projected to routinely use AI agents to shop and pay by 2030 | 25% Rise in malicious bot-initiated transactions over the six months to November 2025 |
Sources: Mastercard, June 2025 (nearly half of the $42B is reported as fraudulent); Mastercard, September 2026; Visa, November 2025.
Real-World Scenarios Ben Is Already Seeing
Among merchants using agent-driven purchasing, several consistent patterns are emerging. They appear in dispute reports, customer support threads, and fraud reviews, reflecting how quickly agentic commerce is changing post-purchase risk. Frank Frantz’s Money20/20 insights on agentic commerce and its impact on fraud and chargebacks show the same shift: AI-driven purchasing is already altering fraud and customer intent.
Four patterns show up most often:
A. IA que el cliente no puede revocar
Many merchants are already experiencing disputes related to orders that were technically authorized but not consciously requested by the customer. An agent may reorder items based on past behavior, availability, or preference learning. Still, the customer may not remember granting that approval or may never notice the automation running in the background.
Cuando aparece el cargo, el instinto del cliente es negar cualquier implicación. Aunque el pedido sea legítimo, el comerciante no puede demostrar fácilmente la intención, ya que no fue una persona quien completó la transacción, sino el agente.
In most cases, confusion directly results in a chargeback. Because the cardholder genuinely does not recall the approval, it behaves like friendly fraud on a legitimate order.
B. Errores cometidos por terceros
Los agentes están diseñados para optimizar, no para interpretar el contexto humano. Pueden elegir un producto ligeramente diferente al esperado, seleccionar un comercio que el cliente no utilizaría normalmente o comprar una cantidad incorrecta en función de cómo hayan analizado la solicitud o los datos.
Instead of contacting support, many customers go directly to their issuer when the agent’s choice falls outside their expectations. The dispute becomes the customer’s way of correcting what they see as an error, even though the transaction was technically valid from the agent's perspective. These expectation gaps are also the main dispute driver for AI shopping assistants, covered in AI shopping chargebacks.
C. Uso indebido de las API de automatización
Los estafadores saben ahora que el tráfico automatizado se camufla mucho mejor que el tráfico humano o manual. Al falsificar los patrones de los agentes o aprovechar los puntos de conexión de la automatización, pueden generar transacciones que parecen estructuradas, coherentes y de bajo riesgo para los sistemas antifraude tradicionales.
Because these flows bypass many human indicators, to the merchant, the activity appears normal and in line with legitimate automation. Only after the dispute is filed does the pattern reveal itself as synthetic. This approach is gaining traction because it passes through the gaps created by agent-driven workflows. The attacker side of this problem, including spoofed agents and fake storefronts, is covered in the companion guide on malicious agents.
D. Los falsos positivos que dan lugar a futuras Contracargos
Algunos comerciantes se están enfrentando a disputas tienen su origen en fricciones que surgen dentro del sistema de detección de fraudes, más que en el fraude en sí mismo.
Los flujos gestionados por agentes a veces activan reglas de fraude, requieren una verificación adicional o son rechazados. El cliente se siente entonces confundido y frustrado con el proceso, sobre todo cuando el agente ha gestionado el flujo «fuera de su vista». Más tarde, cuando aparece un cargo legítimo, el cliente disputas simplemente porque ya se ha perdido su confianza en el proceso.
Son situaciones totalmente evitables, pero ponen de manifiesto lo fácil que es que el comportamiento de los agentes y las expectativas humanas dejen de estar en sintonía.
The table maps each pattern to how the dispute is usually framed and the first control that helps. Which reason code each scenario lands in, and what counts as an authorized agent purchase, is covered in who is liable when AI agents shop for your customers.
| Pattern | How the dispute is usually framed | First control that helps |
|---|---|---|
| A. Purchase the customer cannot recall | Unauthorized-transaction claim from a genuine customer | Customer confirmation before fulfillment, plus a stored mandate record |
| B. Delegated mistake | Not-as-expected claim, or a fraud claim to reverse the order | Order summary sent at purchase, mandate limits on quantity and price, a simple cancellation window |
| C. Spoofed agent traffic | True fraud using stolen credentials or accounts | Agent verification by signature and post-checkout scoring |
| D. False-positive friction | Fraud claim after a declined or challenged flow | Tune rules for verified agents and tell the customer when step-up happens |
Why Legacy Fraud Tools and Playbooks Break Down
La mayoría de los sistemas y herramientas contra el fraude en los pagos por adelantado se desarrollaron en una época en la que había una persona implicada en cada paso del proceso de compra del cliente. El comercio gestionado por agentes rompe con ese modelo, lo que significa que algunas de las herramientas más eficaces del conjunto de herramientas de un comerciante ya no funcionan como se esperaba.
Los modelos de riesgo basados en dispositivos pierden su sentido.
Los modelos tradicionales se basan en gran medida en las características de los dispositivos para identificar comportamientos sospechosos. Cuando el «comprador» es un agente que se ejecuta en servidores o entornos en la nube, los atributos del dispositivo ya no se corresponden con la identidad o la intención de una persona. Esto elimina un punto de referencia fundamental en la lógica actual de detección de fraudes.
Las reglas de velocidad empiezan a clasificar erróneamente los flujos automatizados.
Los agentes suelen trabajar según horarios o bucles lógicos que se repiten con una periodicidad predecible. Las reglas de velocidad tradicionales (por ejemplo, basadas en la hora real en que se realiza la actividad) están diseñadas para detectar comportamientos humanos repetitivos. Sin embargo, estas reglas clasifican erróneamente como sospechosa la actividad normal de los agentes, lo que genera falsos positivos que provocan fricciones, pérdida de ingresos y disputas posteriores.
El análisis del comportamiento no puede interpretar patrones no humanos.
Los modelos que se basan en el movimiento del ratón, el desplazamiento, el tiempo de pausa o la velocidad entre acciones pierden eficacia porque los agentes no se ajustan a las normas de interacción humana. Lo que parece sospechoso en un contexto humano puede ser totalmente legítimo cuando es un agente quien ejecuta el proceso.
La revisión manual se vuelve inmanejable.
Las transacciones gestionadas por agentes aumentan el volumen al tiempo que reducen la visibilidad. Los casos que antes requerían unos minutos de análisis ahora carecen de las señales humanas en las que se basan los revisores. La revisión manual no puede adaptarse al ritmo de la automatización y, aunque los equipos intenten hacerlo, los resultados son inconsistentes porque las señales subyacentes son incompletas. Tratar la gestión de las devoluciones como un sistema, y no como una situación de emergencia, da sus frutos.
La mayor diferencia se aprecia durante disputas».
Incluso cuando un comerciante sabe que una transacción es legítima, demostrar la intención resulta mucho más difícil. Los emisores esperan pruebas que demuestren una conexión clara entre el cliente y la compra. En el comercio por poder, parte de esa acción se delega. Sin nuevos tipos de datos justificativos, los comerciantes pierden los litigios simplemente porque las pruebas no permiten resolver la controversia.
Los sistemas heredados no fallan porque sean deficientes. Fallan porque nunca se diseñaron para entornos en los que son los agentes, y no las personas, los que llevan a cabo gran parte del proceso de compra.
How To Verify a Legitimate AI Agent at Checkout
Because device and behavior signals no longer identify the buyer, verification moves to the agent itself. Five signals exist today. None is universal yet, so log each one and feed it into scoring instead of treating any single signal as a gate.
| Signal | What it proves | Cómo funciona | Status as of October 2026 |
|---|---|---|---|
| Signed agent request | The request comes from an agent registered with a card network program, not a spoofed bot | In Visa’s Trusted Agent Protocol, agents sign requests with HTTP Message Signatures (RFC 9421). You verify the signature against the published public key, check the timestamp (the specification uses an 8-minute window) and reject replayed nonces. | Published specification with reference implementations |
| Network-tokenized credential | The payment credential was issued to a registered agent instead of being a raw card number | Mastercard Agent Pay uses Mastercard network tokens and know-your-agent registration. Visa Intelligent Commerce adds spending limits and approval workflows to agent credentials. | Visa describes its program as still in deployment; Mastercard has not published rollout dates on its Agent Pay page |
| Recorded mandate | The customer authorized this agent for this kind of purchase, within set limits | The Agent Payments Protocol (AP2) defines checkout and payment mandates as verifiable credentials, in an open form (constraints) and a closed form (a specific authorized transaction). Mastercard’s framework similarly requires authenticated user intent and explicit consent. | AP2 is at version 0.2 and supports card payments |
| Shared payment token | Credentials reach you through the agent without exposing raw card data, and you stay merchant of record | The Agentic Commerce Protocol passes a shared payment token, and Stripe’s Shared Payment Token is the first compatible payment method. | Open standard; merchant discovery is still in development |
| Network agent probability score | An issuer-side likelihood that an AI agent initiated the transaction | Mastercard’s AI Transaction Probability Score helps issuers approve legitimate agent purchases and is paired with shared agentic trust and intelligence signals. | Rolling out for testing in the US (Mastercard, September 2026) |
When no signal is present, treat the order as an unverified agent order and log that no agent identity was presented. Do not decline it automatically, because that creates the false-positive disputes described in pattern D. Send it to the scoring step below instead. Authentication at mandate creation, such as a 3D Secure 2 challenge when the customer first authorizes the agent, also gives you an issuer-backed record of the customer’s participation. Network programs change quickly, so track them in agentic commerce regulation.
Scoring Signals That Still Work for Agent Orders
Once the agent is identified, score the order itself. These signals do not depend on a human device or mouse movement, so they stay usable on agent traffic. They sit on top of your baseline ecommerce fraud prevention controls such as AVS, 3D Secure and velocity limits.
| Signal | What to compare | Action when it fails |
|---|---|---|
| Order versus mandate | Cart total, quantity, merchant category and delivery date against the limits the customer set | Hold the order and confirm with the customer |
| Order versus customer history | Reorder cadence, typical basket, usual shipping address, account age | Verify before fulfillment when the order falls outside the pattern |
| Credential and account consistency | Token age, billing and shipping match, whether the login tied to the order is established | Treat a new account, new token and high value together as high risk |
Two more signals need data from outside your store: whether the same agent has produced clean, undisputed orders over time, and whether it or its credential has produced disputes at other merchants. Raise the review threshold for new or inconsistent agents and relax it for agents with a clean history. Replace velocity rules based on the hour of human activity with per-agent and per-credential velocity, so a scheduled reorder is not flagged as a burst.
The Move to Post-Purchase Intelligence (Ben’s POV)
A medida que crece el comercio gestionado por agentes, las señales más importantes suelen aparecer después de la transacción, no antes. Los controles previos a la compra se diseñaron para hacer frente al comportamiento humano y a las dificultades que surgen cuando la intención es compartida entre una persona y un agente. En este contexto, para evitar pérdidas es necesario contar con una mayor visibilidad de lo que solo queda claro una vez que el pedido ya se ha realizado.
La información posterior a la compra cubre las lagunas que dejan los sistemas tradicionales. Ayuda a responder preguntas que no se pueden resolver en el momento de la compra, entre ellas:
- ¿Tiene sentido este pedido teniendo en cuenta el comportamiento anterior del cliente, o es indicativo de confusión o de una automatización involuntaria?
- ¿Este agente goza de reconocimiento en una red de comerciantes más amplia, o es nuevo, no ha sido verificado o presenta un comportamiento irregular?
- ¿Se han producido disputas en otras tiendas a raíz de transacciones similares disputas indiquen un uso indebido o nuevas técnicas de fraude?
- ¿Existen inconsistencias en los atributos de identidad o del dispositivo que indiquen una manipulación detrás de la automatización?
Estas señales aportan un contexto que las herramientas previas a la compra no pueden ofrecer. Ayudan a determinar cuándo un agente ha actuado por debajo de las expectativas del cliente, cuándo se está haciendo un uso indebido de la automatización y cuándo es probable que un patrón habitual derive en una reclamación. El objetivo general es prevención eCommerce Contracargos en toda la tienda.
Hasta hoy, en muchos casos, la única forma fiable de comprender la intención con la suficiente claridad como para intervenir antes de que el emisor se vea involucrado ha sido el análisis posterior a la compra. Esto ofrece a los comerciantes la oportunidad de ponerse en contacto con el cliente, verificar la información, corregir errores o cancelar pedidos antes de que se conviertan Contracargos y, en el caso de los productos físicos, antes de que se envíen.
La inteligencia posventa es más que una simple mejora. Se trata de un cambio necesario en la forma en que los comerciantes protegen sus ingresos en un entorno en el que son los agentes, y no las personas, quienes inician cada vez más el proceso de compra.
A cancelled and refunded order never becomes a dispute, so it never counts toward your monitoring ratios: Visa’s VAMP flags merchants as Excessive at a 1.5% ratio from April 2026, and Mastercard’s ECM program starts at a 1.5% chargeback ratio with 100 or more chargebacks (see VAMP and ECM chargeback thresholds). Use a simple triage rule for every agent order:
| Condition | Acción | Cuando |
|---|---|---|
| Verified agent, order inside the mandate and the customer’s history | Approve and fulfill | Automatically |
| Verified agent, order outside the mandate or history (quantity, price, new category, new address) | Message the customer to confirm and hold fulfillment | Before shipment |
| Agent identity missing or signature fails, credential otherwise valid | Score on order and customer history, step up if risk is high | Before shipment |
| Agent identity fails and the order has other risk signals (new account, mismatched addresses, dispute history elsewhere) | Cancel and refund | Before shipment |
| Digital or instant-delivery goods | Delay the download link or credit grant until the score returns | Before delivery |
Dispute Readiness for Agent Transactions
Some agent orders will still be disputed, so capture the record at the time of purchase: the agent identifier and its verification result, the mandate or consent record (scope, limits, timestamp), the order confirmation sent to the customer and any reply, delivery proof, and the account and delivery-address history. The full checklist and templates are in the agentic commerce chargebacks evidence playbook.
Visa’s Compelling Evidence 3.0 can move liability back to the issuer on Visa 10.4 fraud disputes when you show at least two prior undisputed transactions made 120 to 365 days earlier, with matching data points such as IP address, device ID, account login and delivery address. Agent traffic usually runs from provider infrastructure, so IP and device matches may point to the agent instead of the customer. Capture the account login and delivery address on every agent order so the match still holds. Details are in Visa Compelling Evidence 3.0 explained.
How Chargeflow Prevents and Supports Merchants in Agentic Commerce
Aunque esta guía no se centra en los productos, es importante reconocer que los comerciantes necesitan herramientas que reflejen la realidad de las compras impulsadas por agentes. La automatización genera lagunas que los sistemas antifraude tradicionales nunca estuvieron pensados para gestionar, y muchos comerciantes buscan formas prácticas de subsanarlas sin añadir fricciones ni trabajo manual. Tal y como señala Mysterium VPN, una VPN residencial también puede facilitar un acceso remoto más seguro a la tienda al cifrar todo el tráfico del dispositivo en redes Wi-Fi públicas o compartidas, lo que ayuda a los equipos de los comerciantes a proteger los datos de inicio de sesión, las cookies y las sesiones de administrador cuando revisan pedidos o disputas la oficina.
Chargeflow Prevent scans each order after checkout and before fulfillment. It scores the order with post-purchase signals and intelligence from a network of 20,000+ merchants, then cancels, verifies or approves the order before anything ships, with a false-positive rate under 0.1%. Pricing is $0.40 per scanned transaction, and the first 1,000 scans are free. It does not replace the agent-verification signals above. It adds the order-level and network-level view they cannot provide.
Each stage of the order lifecycle needs its own control:
| Escenario | Control | Chargeflow product |
|---|---|---|
| At checkout | Agent verification, tokenized credentials, mandate capture | Your payment stack and agent-protocol support |
| After checkout, before fulfillment | Order scoring, customer confirmation, cancel or approve | prevención |
| After a dispute notice, before it becomes a chargeback | Refund or resolve through card network alert programs | Alerts, $29 per deflected chargeback (how chargeback alerts work) |
| After a chargeback is filed | Evidence assembly and submission | Automation, 25% of recovered chargebacks (chargeback recovery) |
My goal is not to promote a specific solution, but to emphasize that merchants now need preventive layers that reflect how commerce is changing. Agent-driven transactions require a different type of visibility.
Preguntas frecuentes
What is agentic commerce fraud?
Agentic commerce fraud is any fraud, dispute or wrongful decline that occurs when an AI agent, not the cardholder, completes the checkout. It covers malicious or spoofed agents, and also legitimate orders that the customer later disputes because they did not expect or remember what the agent bought.
Why is agentic commerce important for fraud prevention?
Fraud tools built on device, behavior and velocity signals assume a human buyer, and agent orders break those signals. Legitimate agent orders also produce disputes from forgotten approvals and delegated mistakes that legacy tools cannot tell apart from fraud. Federal Reserve Governor Christopher Waller said in September 2026 that fraud models and rules will need to be recalibrated for agent payment patterns.
How do you prevent fraud in agentic commerce?
Verify the agent through signed requests, network-tokenized credentials and a recorded mandate. Score each order against the mandate and the customer’s history after checkout, confirm with the customer before fulfillment when the order deviates, and keep the agent ID and consent record as dispute evidence.
How do agentic payment solutions prevent fraud?
Card networks issue tokenized credentials to registered agents, attach limits such as spending caps and approval workflows, and let agents sign requests so merchants can verify them. These measures confirm who the agent is and what it was authorized to do. They do not remove disputes from forgotten or mistaken purchases, which is why post-checkout screening and evidence capture still matter.
How is agentic commerce fraud detected?
Detection shifts from device and behavior signals to agent identity, mandate match and history. Compare each order with the mandate limits and the customer’s past orders, track whether an agent has produced clean orders on your store, and use network-level dispute history. Run velocity rules per agent and per credential instead of per hour of human activity.
What should you look for in an agentic commerce fraud prevention solution?
Look for support for agent identity signals from the card networks, scoring that does not rely on device or mouse behavior, a decision before fulfillment, a low false-positive rate, and a path to evidence submission for disputes that still occur. Chargeflow Prevent scans orders after checkout and before fulfillment with a false-positive rate under 0.1%.
Who pays when a legitimate agent purchase is disputed?
Under existing card-not-present rules the merchant generally carries the chargeback unless a liability shift applies, and network rules for agent-specific cases are still being defined. The split between merchant, agent platform, issuer and customer is covered in the AI agent chargeback liability guide.

Contracargos?
Ya no es problema tuyo.
Recupera cuatro veces más Contracargos y prevención , hasta un 90 % de las entradas, gracias a IA y a una red global de 20 000 comercios.














.png)


.webp)