Topic starter
11/11/2026 5:59 pm
TL;DR: Retail and marketplace controls are now colliding with agentic commerce, with Socure showing that legitimate shopping agents can look like hostile automation. That means trust has to move from traffic patterns to identity binding, authorization, and action-level risk.
Editorial analysis by NHI Mgmt Group, based on content published by Socure: “The Next Marketplace Customer Isn't Human. It’s an AI Agent.”.
Key questions
Q: How can persistent agent identity improve fraud controls?
A: Persistent agent identity improves fraud controls by letting each AI agent keep a stable identifier across sessions, so detection systems can correlate behaviour, permissions and transaction history instead of treating every action as anonymous.
Q: What is the best way to authorise AI agents for purchases?
A: The best way is action-level authorization, where the agent is permitted to perform only a specific purchase action with tightly scoped limits on amount, merchant, data use and approval path.
Q: How should e-commerce teams distinguish legitimate AI shopping agents from malicious automation?
A: E-commerce teams should use layered detection rather than a single signal.
Practitioner guidance
- Implement delegated-agent identity binding Create a persistent link between each AI agent and the human or business it represents so the same agent can be recognised across sessions and policy decisions.
- Classify agent activity by principal and intent Use identity, behavioural, and contextual signals to separate legitimate delegated commerce from counterfeit listings, promotion abuse, and other malicious automation.
- Apply action-specific authorization Allow search and purchase flows separately from refunds, account changes, and sensitive data access, with a decision made before each high-risk action completes.
Bottom line: AI shopping agents create a governance problem because marketplaces must distinguish delegated activity from malicious automation before they can safely permit transactions.
Glossary terms: Agentic Commerce, Persistent identity, Risk-based Authorization, Know Your Agent
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:08 pm
Agentic commerce turns delegated identity into a commerce control plane issue: marketplaces are no longer deciding only whether traffic is human or automated. They are deciding whether an agent is acting with valid authority on behalf of a principal, and that distinction determines whether trust can be extended without opening fraud paths. The governance problem is therefore identity binding plus action scope, not traffic suppression. Practitioners should treat agent activity as a first-class identity event, not a nuisance signal.
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: What should marketplaces log when AI agents complete transactions?
A: Marketplaces should log the policy decision, the agent identity, the transaction context, the resources requested, the authorisation outcome and the human or system that granted the decision. Those records support auditability, dispute handling and revocation, and they show whether the marketplace allowed the action under standing rights, delegated scope or a just-in-time exception.
👉 Read our full editorial: AI shopping agents force marketplaces to trust identity and intent