EDITORIAL ARTICLE
Worldpay Agentic Commerce: How Merchants Accept Agent-Initiated Payments
Product analysis · Sources reviewed October 28, 2026. Based on public information; no merchant integration or payment was tested.
A consumer asks an agent to buy shoes. After the agent finds the item and creates a cart, the merchant must confirm the amount, obtain a usable credential, seek issuer approval and fulfill the order. Worldpay operates on the merchant’s payment acceptance and processing side.
Worldpay is not the wallet holding the agent’s money in this example. It aims to connect agent checkout with a merchant’s existing payment APIs, risk rules and fulfillment processes.
Company background and product entry
Worldpay provides merchant payment processing and acquiring for online and offline transactions. Agentic Commerce connects existing merchant payment capabilities to AI shopping. Worldpay Agentic Commerce
Its developer documentation describes flows associated with OpenAI Instant Checkout and the Agentic Commerce Protocol (ACP). Merchants need an Access Worldpay checkout ID and API credentials along with product, cart, delegated-payment and payments APIs. Pay via AI Agent
An illustrative shoe order
This simplifies the documented roles. Credential creation, user authorization, card-network and fulfillment order depend on the merchant’s integration version. An agent need not hold a wallet balance; payment may use the user’s existing card.
What does a delegate token do?
Worldpay describes an agent creating a delegate token representing a payment method through the Sessions API, with restrictions including amount and expiry. The merchant uses it through the Payments API; Worldpay checks applicable limits before processing. Flow
| Question | What the flow addresses | What not to infer |
|---|---|---|
| Payment credential | Provides a delegated credential for merchant processing | The token itself is an agent balance |
| Amount and duration | Limits the payment’s permitted use | Every business rule is automatically enforced by the token |
| User authorization | Connects the user’s selected purchase to payment | Authentication and risk checks are no longer needed |
| Fulfillment | Returns payment results to the merchant order | Successful payment guarantees shipment |
A delegate token, x402 payment credential and AP2 authorization record are not the same mechanism. Their participants, formats and enforcement points differ.
Integration limitations
Worldpay’s delegate-token documentation lists feature scope and limitations. The reviewed material specifies restrictions involving guest cards, 3DS, SCA exemptions and token creation. These apply to that interface and version; do not infer identical restrictions for all Worldpay products.
Merchants should check:
- Whether the agent channel, products and merchant account qualify.
- Who calculates and confirms the final item, tax, shipping and amount.
- Whether cardholder authentication is required and how exceptions are handled.
- Whether authorization, capture, reversal, refund, dispute and fulfillment statuses can be linked.
- How to check an interrupted request and which retries are idempotent.
How does it make money?
Worldpay’s core business is merchant payment processing and related services. Agentic Commerce could help merchants retain existing payment capabilities as orders arrive from new channels; that is analysis, not separate disclosed agent-product revenue. We found no specific public price for this interface. Confirm payment method, geography, merchant contract and processing-stage costs with Worldpay.
Wallet, network and merchant roles
| Participant | Role in this flow |
|---|---|
| Consumer wallet or payment method | Provides funds or a credential the user authorizes |
| Agent platform | Discovers products, assembles cart and requests payment under authorization |
| Worldpay | Provides merchant credentials and payment processing |
| Issuer / card network | Participates in card transaction processing and approval |
| Merchant | Decides product, final order and fulfillment |
Begin with whether your merchant account, agent channel and payment method are supported, rather than whether Worldpay has an agent wallet.
Put payment status into the order lifecycle
After Worldpay returns an authorization result for the shoes, the merchant still checks inventory, captures funds under its own process, ships and may handle refunds.
| State | What the merchant must check | What not to assume |
|---|---|---|
| Cart created | Are price, shipping, tax and inventory still valid? | Cart creation means payment occurred |
| Delegate token created | Is it within amount and expiry limits? | The card transaction is already authorized |
| Payment request times out | Provider and order status | No response means no charge |
| Payment approved | Capture and fulfillment policy | Issuer approval means delivery |
| Customer requests refund | Original transaction, merchant refund and arrival to user | Every refund arrives immediately |
These are questions for the merchant, not a claim that every integration shares one state machine. Read the Payments API token limitations alongside the relevant region and merchant contract.
Who pays and who shapes the experience?
The chain includes a merchant, processor, issuer and card network. Merchants may pay processing fees; the agent platform and merchant both influence checkout; authentication and chargebacks follow applicable network and institutional rules. Without a Worldpay contract, one cannot calculate each party’s share or treat the payment amount as Worldpay revenue.
For procurement, ask for a fixed demonstration: one item, one successful payment, one expired credential and a status lookup after a timeout. Compare reproducible order and processing records with the existing acquiring setup.
Sources: Worldpay Agentic Commerce · ACP flow · delegate-token limitations.