Why Agentic Commerce Requires Multi-Tokenisation
21 October 2025
As artificial intelligence evolves, “agentic commerce” where autonomous agents buy, negotiate and transact on behalf of users, is rapidly moving from concept to early reality.
But while the idea sounds futuristic, one major hurdle stands in the way: how can these agents securely prove identity, authorise payments and manage transactions across multiple ecosystems?
Experts increasingly agree that multi-tokenisation, using several types of secure digital tokens for identity, payment, and authorisation, is essential to making agentic commerce both safe and scalable.
This article explains what agentic commerce is, why single-token systems aren’t enough, and how multi-tokenisation could underpin the next generation of autonomous digital payments.
Agentic commerce describes a system in which AI agents autonomously complete commercial tasks on behalf of people or organisations.
Unlike chatbots or recommendation systems, these agents can:
In short, the agent acts as a digital “buyer” or “assistant”, but autonomy creates new technical challenges, particularly in terms of identity and payments.
Tokenisation replaces sensitive data (like card numbers or personal IDs) with unique, non-sensitive symbols called tokens.
These tokens make transactions more secure, flexible, and revocable, which is why tokenisation is already embedded in card networks, mobile wallets and digital identity frameworks.
A single token can’t handle the full complexity of agentic commerce. That’s because an AI agent must navigate multiple domains, each with unique security, legal and operational requirements.
|
Domain |
Example |
Token Purpose |
|
Identity |
Who is this agent acting for? |
Verifiable identity token |
|
Merchant |
Which store or platform? |
Merchant-scoped token |
|
Payment Network |
Card or PSP system |
Network token |
|
Delegation |
What can the agent do? |
Authorisation / permission token |
An agent may interact with merchants, card networks, wallets, and APIs, all requiring different credentials. Multi-tokenisation lets each domain validate its part independently.
Tokens can be issued with specific scopes and lifetimes. If a payment token is compromised, it can be revoked without disabling the agent entirely.
Separate tokens let users safely delegate purchasing power to agents without losing control. A single global token would be too risky.
Different regions, PSPs and identity frameworks can operate in parallel. Multi-token setups allow interoperability across fragmented standards (e.g. PSD2, GDPR, PCI DSS).
An AI agent acting for a business might use:
At checkout, these tokens combine to authorise a transaction, all without exposing sensitive credentials or requiring human intervention.
If the business revokes the delegation token, the agent instantly loses permission to transact.
Implementing multi-tokenisation requires careful design across security, compliance and interoperability:
Card networks like Mastercard and Visa are already exploring “agentic token” models, while Stripe and OpenAI are developing shared agentic commerce protocols to ensure interoperability between payment ecosystems.
Despite progress, multi-tokenisation raises new questions:
Nonetheless, multi-tokenisation remains the most realistic path toward safe, scalable agent-driven payments.
Over the next few years, we’re likely to see:
If successful, multi-tokenisation could become the invisible infrastructure behind intelligent commerce, allowing AI agents to transact securely and responsibly on our behalf.
Agentic commerce represents a major evolution in how digital transactions are performed. But it can only function with secure, flexible ways to represent identity, intent, and payment authorisation.
Multi-tokenisation, the separation of credentials into specialised, interoperable tokens, provides exactly that foundation.
By addressing security, control, and interoperability in parallel, it paves the way for AI-driven transactions that are not only efficient but also compliant, transparent, and trustworthy.