TL;DR: Agentic orders rose to 5.3x their early-August 2026 level, signalling that commerce teams are no longer dealing with a future use case but an active traffic class, according to Forter. Checkout design, fraud controls and loyalty policy now need to distinguish human intent from agent behaviour.
Editorial analysis by NHI Mgmt Group, based on content published by Forter: “The 5 Pillars of Agentic Readiness”.
Key questions
Q: Why do guest checkout flows raise loyalty fraud risk?
A: Guest checkout raises loyalty fraud risk because the merchant has weaker identity assurance and fewer reuse signals, so attackers can open accounts, redeem points, or abuse welcome offers with stolen emails, disposable addresses, and scripted payment attempts.
Q: What is the difference between 3DS and decoupled authentication?
A: 3DS is an authentication flow that lets an issuer challenge a cardholder during an online card payment, usually to confirm the payer before authorisation completes.
Q: Why do AI shopping agents change return fraud governance?
A: AI shopping agents can generate high volumes of coordinated return requests, refund claims, and account activity far faster than manual review can absorb.
Practitioner guidance
- Define an agent acceptance policy Decide which AI shopping agents you will admit, challenge or block based on traffic source, transaction type and risk tolerance.
- Harden product discovery controls Audit robots.txt, network-level bot filtering and llms.txt so machine-readable discovery is intentional rather than accidental.
- Treat checkout APIs as governed assets Inventory the APIs that support agentic purchase flow, then apply authentication, authorisation and monitoring to each one.
Bottom line: Agentic commerce is collapsing the distance between browsing, authentication and payment, which turns checkout into an identity governance problem as much as a conversion problem.
Glossary terms: Agentic Commerce, Headless Checkout, Merchant-Initiated 3RI, 3DS
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Agentic commerce creates an identity boundary inside checkout, not just a new channel. Merchants are now deciding whether a purchase is being made by a person, a delegated agent or a fraudster using the same surfaces. That means trust decisions move from storefront heuristics into identity, token and transaction policy. The practical conclusion is that checkout governance has to classify the actor before it can classify the order.
A question worth separating out:
Q: What signals indicate agentic traffic needs extra review?
A: Agentic traffic needs extra review when it shows high request velocity, repetitive tool calls, unusual navigation paths, broad data retrieval, and access patterns that do not match a human session. Add step-up checks, per-agent allowlists, rate limits, and runtime policy enforcement when an AI agent uses tokens, APIs, or delegated permissions.
👉 Read our full editorial: Agentic commerce turns checkout, fraud and loyalty into identity problems