Prevenção de fraudes e do “ Chargebacks ” no comércio por agente

Chargebacks?
Não é mais problema seu.
Recupere 4 vezes mais chargebacks e PREVENÇÃO — até 90% dos e-mails recebidos —, com tecnologia de IA e uma rede global Rede de 20.000 Lojistas.
Resumo:
- 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.
Um guia prático de Ben, estrategista de Fraude e Chargeback do site “ Chargeflow” e mentor no MRC
O comércio agênico está redefinindo as regras do jogo em matéria de risco
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.
Os agentes de IA não estão apenas influenciando as compras, mas também começando a realizá-las. À medida que esses sistemas automatizados assumem cada vez mais o processo de compra, surgem novos problemas em relação à forma como Lojistas detecta fraudes, compreende a intenção do cliente e evita chargebacks.
Vejo essa mudança todos os dias. Dados do Disputa revelam uma tendência crescente de clientes contestarem cobranças resultantes de decisões automatizadas que eles não compreenderam totalmente ou não esperavam. Por meio do meu trabalho orientando equipes de combate à fraude, participando do Comitê de Fraudes do MRC e colaborando diariamente com as operações d Lojista , observo como tanto os clientes quanto os fraudadores estão se adaptando a essa nova forma de fazer compras.
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.
Como o comércio agênico muda a forma de lidar com fraudes
As ferramentas tradicionais de detecção de fraudes partem do princípio de que há um ser humano por trás de cada ação. Essa suposição começa a falhar no momento em que o comprador passa a ser um 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.
À medida que os agentes ganham maior controle, muitos dos sinais tradicionais perdem sua confiabilidade. Impressões digitais de dispositivos, padrões de perfis comportamentais, sinais de atrito e trajetórias de navegação têm origem em comportamentos humanos. Os agentes agora agem de maneiras previsíveis e “consistentes com o funcionamento das máquinas”, que os sistemas existentes não conseguem processar.
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.
O risco vai muito além da fraude. Há um descompasso cada vez maior entre o que os clientes esperam e o que o agente decide.
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. Compras feitas pela IA das quais o cliente não se lembra
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.
Quando a cobrança aparece, o instinto do cliente é negar qualquer envolvimento. Mesmo que o pedido seja legítimo, o Lojista não consegue demonstrar facilmente a intenção, pois não foi uma pessoa que concluiu a transação. Foi o agente quem o fez.
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. Erros cometidos por terceiros
Os agentes são projetados para otimizar, e não para interpretar o contexto humano. Eles podem escolher um produto ligeiramente diferente do esperado, selecionar um Lojista que o cliente normalmente não usaria ou comprar a quantidade errada, dependendo de como analisaram a solicitação ou os dados.
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 indevido das APIs do Automação
Fraudsters now understand that automated traffic blends in considerably better than human or manual traffic. By spoofing agent patterns or exploiting automation endpoints, they can generate transactions that appear structured, consistent, and low-risk to legacy fraud systems.
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. Falsos positivos que moldam o futuro Chargebacks
Algumas empresas de segurança de dados ( Lojistas ) estão enfrentando problemas de conformidade ( disputas ) decorrentes de atritos gerados dentro da estrutura de combate à fraude, e não da fraude em si.
Os fluxos conduzidos por agentes às vezes acionam regras de fraude, exigem verificação adicional ou são recusados. O cliente fica então confuso e frustrado com o processo, especialmente quando o agente conduziu o fluxo “nos bastidores”. Mais tarde, quando uma cobrança legítima aparece, o cliente a disputas a simplesmente porque sua confiança no fluxo já havia sido abalada.
Essas situações são totalmente evitáveis, mas mostram como é fácil que o comportamento do agente e as expectativas humanas fiquem em desacordo.
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
A maioria dos sistemas e ferramentas de combate à fraude em pagamentos antecipados foi desenvolvida numa época em que havia intervenção humana em todas as etapas da jornada do cliente. O comércio orientado por agentes rompe com esse paradigma, o que significa que algumas das ferramentas mais eficazes na pilha de soluções de um “ Lojista” não funcionam mais como esperado.
Os modelos de risco baseados em dispositivos perdem o sentido.
Os modelos tradicionais dependem fortemente das características dos dispositivos para Identifique ar comportamentos suspeitos. Quando o “comprador” é um agente que opera por meio de servidores ou ambientes em nuvem, os atributos do dispositivo deixam de estar associados à identidade ou à intenção humana. Isso elimina um importante ponto de referência na lógica existente de detecção de fraudes.
As regras de velocidade começam a classificar incorretamente os fluxos automatizados.
Os agentes costumam operar de acordo com cronogramas ou loops lógicos que se repetem em intervalos previsíveis. As regras de velocidade tradicionais (por exemplo, baseadas na hora exata da atividade) são projetadas para sinalizar comportamentos humanos repetitivos. Elas classificam erroneamente como suspeita a atividade normal dos agentes, gerando falsos positivos que levam a atritos, perda de receita e disputas a problemas em etapas posteriores.
A análise comportamental não consegue interpretar padrões não humanos.
Modelos que se baseiam no movimento do mouse, na rolagem, no tempo de pausa ou na velocidade entre as ações perdem eficácia porque os agentes não seguem as normas de interação humana. O que parece suspeito em um contexto humano pode ser totalmente legítimo quando um agente está executando o fluxo.
A revisão manual torna-se impossível de gerenciar.
As transações automatizadas aumentam o volume, ao mesmo tempo em que reduzem a visibilidade. Casos que antes exigiam apenas alguns minutos de análise agora carecem dos sinais humanos nos quais os revisores se baseiam. A revisão manual não consegue acompanhar o ritmo d Automação, e mesmo quando as equipes tentam fazê-lo, os resultados são inconsistentes porque os sinais subjacentes estão incompletos. Tratar a gestão dchargeback como um sistema, e não como uma resposta a emergências pontuais, traz resultados positivos.
A maior lacuna surge durante disputas.
Mesmo quando um “ Lojista ” sabe que uma transação é legítima, provar a intenção torna-se significativamente mais difícil. Os emissores esperam evidências que mostrem uma conexão clara entre um cliente e uma compra. No comércio por meio de agentes, parte dessa ação é delegada. Sem novos tipos de dados comprovativos, os “ Lojistas ” perdem os processos simplesmente porque as evidências não conseguem esclarecer o “ Disputa ”.
Os sistemas legados não estão falhando por serem fracos. Estão falhando porque nunca foram projetados para ambientes em que são os agentes, e não os seres humanos, que realizam grande parte do processo 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 | Como 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)
À medida que o comércio orientado por agentes cresce, os sinais mais importantes geralmente surgem após a transação, e não antes dela. Os controles pré-compra foram concebidos para lidar com o comportamento humano e as dificuldades que surgem quando a intenção é compartilhada entre um ser humano e um agente. Nesse contexto, evitar perdas exige uma maior visibilidade sobre o que só fica claro depois que o pedido é efetivado.
A inteligência pós-venda preenche as lacunas deixadas pelos sistemas legados. Ela ajuda a responder a perguntas que não podem ser resolvidas no momento da finalização da compra, incluindo:
- Esse pedido faz sentido, considerando o comportamento anterior do cliente, ou indica confusão ou um “ Automação ” não intencional?
- Esse agente é reconhecido em uma rede mais ampla Lojista Rede , ou é novo, não verificado ou apresenta comportamento inconsistente?
- Transações semelhantes em outros sites Lojistas resultaram em disputas que indiquem uso indevido ou novas técnicas de fraude?
- Existem inconsistências nos atributos de identidade ou do dispositivo que sugiram manipulação por trás do Automação?
Esses sinais oferecem um contexto que as ferramentas de pré-compra não conseguem fornecer. Eles ajudam a determinar quando um agente agiu de forma diferente das expectativas do cliente, quando um “ Automação ” está sendo usado indevidamente e quando um padrão familiar tem chances de se transformar em um “ Disputa ”. O objetivo mais amplo é “PREVENÇÃO ” o “eCommerce chargebacks ” em toda a loja.
Até hoje, em muitos casos, a única maneira confiável de compreender a intenção do cliente com clareza suficiente para intervir antes que o emissor se envolva tem sido a análise pós-compra. Isso dá ao Lojistas a oportunidade de entrar em contato, verificar, corrigir erros ou cancelar pedidos antes que se tornem chargebacks e, no caso de produtos físicos, antes que os produtos sejam enviados.
A inteligência pós-compra é mais do que uma atualização. Trata-se de uma mudança necessária na forma como os “ Lojistas ” protegem a receita em um ambiente em que são os agentes, e não os seres humanos, que dão início a grande parte do processo 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 | Ação | Quando |
|---|---|---|
| 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
Embora este guia não tenha como foco os produtos, é importante reconhecer que Lojistas precisa de ferramentas que reflitam as realidades das compras orientadas por agentes. Automação introduz lacunas que os sistemas tradicionais de combate à fraude nunca foram projetados para lidar, e muitos Lojistas estão buscando maneiras práticas de preencher essas lacunas sem causar atritos ou exigir esforço manual. Conforme destaca a Mysterium VPN, uma VPN residencial também pode proporcionar um acesso remoto mais seguro à loja, criptografando todo o tráfego do dispositivo em redes Wi-Fi públicas ou compartilhadas, ajudando as equipes de Lojista a proteger logins, cookies e sessões de administrador ao revisar pedidos ou disputas fora do escritório.
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:
| Palco | 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 | PREVENÇÃO |
| 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.
Perguntas frequentes
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.

Chargebacks?
Não é mais problema seu.
Recupere 4 vezes mais chargebacks e PREVENÇÃO — até 90% dos e-mails recebidos —, com tecnologia de IA e uma rede global Rede de 20.000 Lojistas.














.png)


.webp)