Topic starter
11/11/2026 6:02 pm
TL;DR: AI assistants are already placing orders at scale, and Forter reports that merchants are seeing more agent traffic without a shared policy model. Checkout now depends on deciding which software identities can act, what they may buy, and how identity is verified.
Editorial analysis by NHI Mgmt Group, based on content published by Forter: “The Agentic Commerce Conversations Merchants Are Having Now”.
By the numbers:
- Within the first three weeks, 40% of Instinct users gave it their credit card.
- Protocol-based journeys are 10x faster and use 5x fewer tokens.
Key questions
Q: Why do scraping agents create fraud risk in commerce?
A: Scraping agents create fraud risk because they can mimic shoppers, enumerate products or prices at scale, and automate account abuse, inventory hoarding, or credential stuffing.
Q: What is the difference between protocol-based agents and scraping bots?
A: Protocol-based agents use the merchant-defined interaction path, such as a documented API or structured feed, so their access is explicit and controllable.
Q: How should merchants handle AI agents at checkout without increasing false declines?
A: They should treat AI agents as delegated identities and pass agent metadata, permissions, and session context into fraud systems.
Practitioner guidance
- Define software-actor checkout policy Set explicit rules for which AI assistants, bots, or declared agents may browse, log in, and buy on behalf of customers, including the risk thresholds for step-up checks.
- Separate identity signals from device signals Require a policy decision that combines declared identity, request context, and session signals before checkout, rather than relying on fingerprinting alone.
- Instrument agent-specific checkout telemetry Log agent declarations, credential use, basket changes, payment attempts, and return requests so disputes can be traced back to a software actor.
Bottom line: Agentic commerce turns checkout into an identity and policy problem because software can now act with customer-like reach and speed.
Glossary terms: Agentic Commerce, AI Agents, Delegated authority, Web Scraping
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:07 pm
Identity is now the control plane for agentic commerce: checkout no longer starts with product selection and ends with payment. It starts with deciding whether a software actor is recognised, what delegation it carries, and whether the merchant will accept the action at all. That makes identity verification a business-policy decision, not just a fraud signal. Merchants that delay this choice until after the order is formed will keep reacting to traffic they should have governed earlier.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: When should loyalty rewards be delayed for automated buyers?
A: Loyalty rewards should be delayed when automated buyers can rapidly create, test, or resell accounts, or when purchase behaviour needs review for abuse signals. Holding periods let fraud controls inspect the order, device, payment instrument, and account history before points or benefits become redeemable, reducing abuse from scripted checkout flows and bonus harvesting.
👉 Read our full editorial: Agentic commerce turns identity into the checkout gate