What do payment operators need for payments made by objects and AI agents?

Tokenized credentials bound to the device or agent, clear mandates and merchant-initiated payment handling. Network tokenization and a subscription engine for scheduled and stored-credential charges are the building blocks.

The new payer

A connected car paying for charging, a printer reordering ink, an AI agent booking a trip: the payment is initiated by something that is not the cardholder, at a time the cardholder did not choose. The schemes treat these as merchant-initiated or agent-initiated transactions, with their own rules on consent and authentication.

The building blocks

• Tokenized credentials: a network token bound to the device or agent, not a card number stored somewhere.
• Mandates: a record of what the customer allowed: amount limits, frequency, merchants, expiry.
• Stored-credential handling: the first authenticated transaction, then merchant-initiated charges that reference it.
• A kill switch: the customer must be able to revoke the device or agent in one place.

What operators should prepare

Most of this already exists for subscriptions: a mandate, a token, scheduled or triggered charges. The difference is scale and variety: many small payments, many devices, and agents that compare merchants before paying. Operators that run network tokenization and a subscription engine have the mechanics. The work ahead is on identity: proving which agent acted for which customer, under the scheme programs for agentic commerce that Visa and Mastercard are rolling out.