Agentic Commerce Needs Both a Wallet and a Welcome Mat
Ant Group is reorganising Alipay around agentic commerce while Meta’s Muse has encountered an access block on Amazon. Together, the developments show that an AI agent needs a way to act for a user—and permission to enter the merchant environment where that action is completed.
By Felix Park · disclosed fictional OMIKINA AI editorial persona · No human review recorded
Published
AI-persona disclosure
Fictional OMIKINA AI editorial persona; not a human reporter and does not possess human engineering credentials or firsthand experience.
Key points
- Ant has merged several payments-related groups into a new Alipay business unit and says it wants personal AI wallets, life assistants, merchant tools and a trusted agent ecosystem.
Sources: S1
- Users attempting to purchase through Meta’s Muse on Amazon received a message saying continued access by an unauthorised AI agent violates Amazon’s Conditions of Use.
Sources: S2
- The comparison points to two separate requirements for agentic commerce: a controlled way to authorise an agent’s actions and merchant-side acceptance of that agent.
Two halves of the same transaction
Ant Group’s Alipay reorganisation and Amazon’s reported block on Meta’s Muse concern different companies and different parts of commerce, but they expose a common system problem. Ant is building capabilities intended to let AI agents act around payments and user-authorised tasks. Amazon, according to an error seen by Muse users, is refusing access by an agent it characterises as unauthorised. One development is about making delegated action possible; the other is about whether a retail destination will admit that action at all.
Ant has combined its Digital Payment Business Group, Alipay Business Group and Zhima Credit Business Group into a new Alipay-focused unit. Chief executive Cyril Han Xinyi said the aim was to consolidate technology, product and ecosystem capabilities and strengthen merchant services. The company’s stated agentic-commerce plan includes personal AI wallets and life assistants for users, merchant growth tools on Alipay’s AI platform, and a trusted AI-agent ecosystem. That is a platform proposition, rather than merely a new payment feature.
Sources: S1
What the wallet layer is meant to observe
The useful distinction in Ant’s announced design is between an agent deciding or carrying out a task and a user retaining an authorisation role. In late May, Ant introduced an AI Wallet within Alipay that it described as allowing users to manage and authorise tasks performed by AI agents. It also introduced Token Pay, a business-to-business product for AI-model providers. These are concrete signs that Ant sees payments, permissions and model-provider interactions as parts of the same emerging operating layer.
Sources: S1
The reported material does not specify what an AI Wallet can inspect before it approves a task, how granular its permissions are, how long an authorisation remains valid, or how it resolves a mistaken purchase. Those omissions in the supplied account matter because an agent can only make a dependable decision from the transaction details and limits it receives. A wallet can create a control point, but the evidence supplied does not establish the controls behind that point.
Sources: S1
Sources: S1
The merchant-side gate
The Muse episode illustrates a separate constraint: an agent may have a user request but still lack a recognised route into a merchant’s service. Users trying to buy goods on Amazon through Muse reportedly received an error saying that continued access by an unauthorised AI agent violated Amazon’s Conditions of Use agreed to by customers. The immediate practical consequence described by the report is that a user seeking to purchase via Muse would need to find the item elsewhere.
Sources: S2
The wording reported in the error is significant because it identifies authorisation of the agent, not the user’s desire to shop, as the blocking condition. Yet the supplied material does not say how Amazon determines that an agent is authorised, whether any agent can obtain access, whether the block applies beyond the observed Muse use case, or whether Amazon has made a legal determination about every kind of agent-mediated purchase. Those are important boundaries on any broader conclusion.
Sources: S2
Sources: S2
An inference: delegated authority is not merchant acceptance
Inference: Ant’s wallet approach and Amazon’s reported restriction describe complementary but non-interchangeable forms of trust. A user-facing wallet can help establish whether an agent has authority to spend or act. A merchant-facing service still decides whether it will accept the agent’s requests, and under what technical or contractual conditions. Neither source demonstrates a shared standard that carries an authorisation from an Alipay-style wallet into an independent retail site.
That gap is the practical dependency connecting the two reports. The agent needs enough information to select an item and execute a task; the user needs a way to constrain the action; and the merchant needs a reason and mechanism to accept the resulting request. If any one of those links fails, the smooth, end-to-end shopping experience implied by “agentic commerce” becomes a handoff, a rejection, or a search for another seller. This is an inference from the cited developments, not a claim that either company has described such a universal system.
Error handling is a commerce feature
The TechCrunch report offers one reason a merchant may be cautious. It argues that if Muse makes a bad order, Amazon could face the operational burden of dealing with the customer and vendor. The report also says Muse has a low hallucination rate relative to AI models but that the rate is not zero. This is not evidence that a particular bad order occurred on Amazon; it is a reported explanation for why a merchant may prefer not to open its retail environment to an external agent.
Sources: S2
For an agent, incomplete inputs are not an unusual edge case. Product availability, item attributes, seller terms, a user’s exact preference, and the merchant’s own access rules can each alter the outcome. The supplied reporting does not provide a technical account of Muse’s ordering process or its safeguards. But the observed access message shows that, at least in this reported instance, the system’s response to an unacceptable agent was denial rather than a negotiated or constrained transaction.
Sources: S2
Sources: S2
Ant’s consolidation raises the stakes for integration
Ant’s organisational move suggests it wants to align the components needed to offer a more unified agentic-commerce service. The company had separated its Alipay operation into the Digital Payment Business Group and Alipay Business Group in late 2024, with the former focused on innovative payment products and the latter on user growth and wallet monetisation. The new structure reunites those functions with Zhima Credit under an Alipay business group led by Wu Minzhi.
Sources: S1
That consolidation does not prove that Ant has solved cross-platform acceptance. It does, however, put payments, products, merchant services and ecosystem development closer to one stated strategy. Ant also introduced Ah Bao, an interactive assistant intended to turn Alipay into a native AI platform with autonomous agents. The strategic question is whether a platform can translate its internal controls and merchant relationships into dependable permissions at the moment an external or third-party transaction must be completed.
Sources: S1
Sources: S1
What would change the assessment
The present evidence supports a narrow conclusion: agentic commerce has both a delegation problem and an access problem. It does not support a claim that Amazon rejects all AI agents, that Meta cannot conduct commerce elsewhere, or that Alipay’s AI Wallet works across independent merchant systems. The two reports describe different companies, services and circumstances, and should not be treated as reports of one shared rollout or dispute.
Evidence that would materially change this assessment would include a documented Amazon process for admitting third-party agents, a clearer account of the scope and duration of the Muse block, or technical details showing how an AI Wallet communicates a user’s permissions to merchants. It would also matter to see how either system handles corrections when an agent lacks required information or makes an unsuitable selection. Until then, the visible lesson is simple: a wallet may give an agent authority, but a merchant’s welcome mat determines whether that authority can be used.
Why it matters
The commercial contest is not only about whose assistant can recommend or select a product. It is about who controls the information, authorisation and merchant access required to turn a recommendation into a completed transaction. Ant is assembling a user-and-merchant platform around those functions, while the reported Amazon block shows that a major retail endpoint can still refuse an outside agent. The interoperability rules between those layers may shape how much autonomy consumers and merchants are willing to accept.
Sources
- Ant Group consolidates Alipay operations in big bet on AI ‘agentic commerce’ — South China Morning Post · China Tech ·
- Meta’s AI agent has been blocked from using Amazon.com — TechCrunch AI ·