En
← All articles

An AI can pay for office supplies. Who approved the order?

Visa and Lianlian’s live B2B purchase shows what an agent-specific credential can do and which decisions remain with the buyer.

ColumnE-commerceAuthorOpen Market NotesTypeArticle
A corporate payment card and a purchase order marked approved in red.

A small company can give an assistant a clear-sounding instruction: replace the printer supplies we use every month. That is not quite a purchase policy. There may be three models of printer, an approved supplier list, a choice between original and compatible cartridges, a delivery deadline and a budget that includes tax. An assistant can make sense of the request; the business still has to decide which choices it is willing to delegate and how it will verify the resulting expense.

On November 18, Visa and Lianlian DigiTech said that XWorker, an AI agent registered in Visa’s Agentic Directory, completed a live purchase of office supplies using a tokenized payment credential designed specifically for an authorized agent. The companies distinguish this from an earlier live purchasing exercise with LoopX Pay. They also unveiled LianLian XCard: eligible clients could apply from November 18, with card limits and transaction thresholds among the disclosed controls. Customers can link an XPay wallet for agent payments within business-defined parameters. The announcement does not disclose the transaction amount, the full policy used for that purchase or the scale of subsequent deployment.

Identity, permission and payment are different records

An entry in an agent directory helps identify the software. A token substitutes for payment card details in the payment flow. The procurement mandate is a separate company decision about what the software may commit to. Visa’s developer documentation describes purchase instructions and transaction controls; it is a technical reference, not proof of the precise rules Lianlian used for the live purchase.

Suppose the business caps a supply purchase at $120 and expects it from an approved seller by Monday. A product listed at $105 may land at $128 after delivery and tax; one listed at $108 may ship after Monday. On a price-only test, the second could pass despite missing the operational goal. The rule that the payment system can apply at authorization may be narrower than the policy the procurement team checks before checkout. Useful designs distinguish where each rule is enforced and return changed terms for review when the permitted scope no longer fits. The figures are illustrative; they are not data from the Visa–Lianlian transaction.

A clean authorization is only the first accounting event

Procurement continues after payment. If the seller sends the wrong item or ships only part of the order, the accounts team still needs the original approval, the paid amount, the order and delivery records, and a link to any refund. A retry after a failed checkout can also produce a duplicate order if teams treat every attempt as a new instruction. Separate identifiers for the approved need, the checkout attempt and the final expense make it easier to spot the mismatch. The question is not whether every trace can be kept forever, but whether the business can reconstruct what happened without retaining more data than it needs.

Routine and reversible buying is an obvious place to gather this evidence. Compare how long staff spend approving an order, how often an agent goes outside the permitted scope, and what it takes to match receipts or unwind a purchase. Scale to broader procurement only when those outcomes are sufficiently visible. The November purchase documents a specific milestone: a recognized agent used its own type of credential for a live business purchase. It does not establish that authority, fulfillment and exception handling have all been automated.

Information only. No investment, legal, tax, or financial advice.