IXOPAY Launches IXO One, Building a Record of Consent and Intent for AI Agent Payments into Payment Orchestration
Payment infrastructure provider IXOPAY unveiled IXO One, unifying orchestration, tokenization and payments intelligence. We explain the three parts of its Agentic Suite for agentic payments and what merchants should check to prepare for disputes.
Key Takeaways
- Dallas-based payment infrastructure provider IXOPAY announced IXO One, a modular payments platform that brings together payment orchestration, tokenization and payments intelligence, with an Agentic Suite for AI agent payments built in. General availability of the unified experience is planned for early 2027.
- The core piece is Universal Tokens, which keep raw card data away from agents while storing the agent's identity, the customer's consent and the purchase intent alongside the payment record. The idea is to give merchants evidence they can use when an agent-initiated purchase ends in a chargeback.
- For merchants, the question that comes before "which protocol should we back" is whether they can store who authorized what for orders placed through agents. Supported protocols and pricing are not disclosed, however, so the offering cannot yet be fully evaluated.
What IXOPAY's IXO One Is
IXOPAY has unveiled IXO One, a modular, AI-native payments platform combining orchestration, tokenisation and payments intelligence, with agentic payment capabilities and general availability planned for early 2027.
thefintechtimes.comOn November 3, 2026, payment infrastructure provider IXOPAY, headquartered in Dallas, announced IXO One. It brings three products the company previously sold separately (payment orchestration, tokenization and payments intelligence) onto a common portal and developer experience.
Payment orchestration refers to bundling multiple payment service providers (PSPs) and acquirers behind a single API and routing each transaction along the best path. It is an area where the patchwork of connections easily turns into technical debt, especially for merchants that have added providers country by country and payment method by payment method.
IXO One's pitch is "buy what you need, build what sets you apart." Merchants can own their PSP connections through an Adapter SDK, and IXOPAY says they can add or remove components or switch PSPs without rebuilding their payment stack. The platform also includes IXO AI, an assistant that lets merchants query payment data in plain language and see what needs attention.
The company also shared figures on its scale. According to the official announcement, transaction count on its orchestration platform rose 80% year over year through October 2026, it has supported more than USD 200 billion in payment volume since 2018, and it connects merchants to more than 200 PSPs and 300 payment methods.
The rollout is phased. General availability of the first unified experience and a new flexible commercial model is planned for early 2027. Until then, customers continue to buy the existing orchestration, tokenization and intelligence products individually.
The Agentic Suite, Launched in September, Is the Real Story
One point is worth noting up front: the Agentic Suite for agentic payments is not new with this announcement. IXOPAY announced the Agentic Suite on its own on September 9, 2026, and IXO One repositions it as part of the unified platform.
The Fintech Times also describes the Agentic Suite as the "more forward-looking part" of the launch. Payment orchestration itself is a mature market. What IXOPAY wants to claim as new is that purchases started by AI agents rather than people can be accepted on existing payment infrastructure.
The Agentic Suite consists of three components.
| Component | Role | Main users | How the official announcement describes it |
|---|---|---|---|
| Payment Agent | Connects purchase requests from agents to existing payment infrastructure | Customer-facing buying channels | Connects merchant-owned agents, IXOPAY-powered experiences and supported third-party agents through a single integration |
| Universal Tokens | Protects card data while preserving transaction context | Payments, fraud and dispute teams | Links agent identity, customer consent and purchase intent to the payment reference |
| MCP Server | Gives AI assistants governed access to payment and tokenization tasks | Internal development and payment operations teams | Checks existing permissions, isolates API credentials from the AI client and logs each action |
Of the three, Payment Agent and Universal Tokens are the ones directly involved in customer purchases. MCP Server is a tool for internal development and operations teams and serves a different purpose. Below, we start with Universal Tokens, which matter most for merchants.
Universal Tokens and the Question of Who Authorized What
When a person enters a card number and buys something themselves, merchants rely on human signals such as device data, input behavior and login history for fraud screening and dispute handling. When an agent buys on the customer's behalf, many of those signals disappear.
IXOPAY's product blog lists four questions a merchant may have to answer if an agent-initiated transaction is disputed: which agent performed the transaction, what the customer authorized, whether the agent acted within the agreed limits, and what the intent behind the purchase was.
Universal Tokens are designed to keep the material needed to answer those questions attached to the payment record. They link the payment reference (the token) to "trust artifacts," namely agent identity, customer consent and purchase intent, creating a merchant-owned, auditable record. Raw card data is never handed to the agent, and the token can be used across PSPs and buying channels.
Tokenization here means replacing a card number with a meaningless substitute value for storage and use. On the relationship with network tokens issued by the card schemes, IXOPAY says Universal Tokens work alongside them rather than replacing them. Network tokens provide issuer-level trust and better approval rates, while Universal Tokens give merchants portability, policy control and visibility into the agent's authority.
Why does it matter that the record sits with the merchant? In an article on the hidden liability of agentic commerce, fintech analyst Sam Boboev points out that in every protocol currently proposed, from OpenAI to Google, the merchant remains the Merchant of Record, so the cost of returns and chargebacks when an agent buys the wrong item falls on the merchant. If the liability stays with the merchant, the evidence has to stay with the merchant too. That is the premise behind Universal Tokens.
IXOPAY CEO Ajoy Krishnamoorthy said in the September announcement that agentic commerce is a new growth channel, but taking advantage of it means balancing innovation with new questions around transaction liability. The view is that whether a merchant holds its own dispute evidence becomes a precondition for deciding to accept agent-initiated orders at all.
What "No Integration per Protocol" Actually Means
Payment Agent is a layer that sits between agents and the merchant's payment infrastructure. It interprets purchase requests and coordinates tokenization, authentication, routing and downstream processing. The product page describes three ways to use it.
The first is handling the payment side for a shopping agent the merchant has already built. The second is for merchants without their own agent: an IXOPAY-provided conversational shopping experience, connected to the product catalog, embedded on the merchant's site. The third is accepting purchase requests from supported third-party AI assistants and platforms.
In every case, IXOPAY argues, merchants avoid building a separate payment integration for each protocol. CTO Jill Willard said that agentic commerce "shouldn't force merchants to choose which version of the future they believe will win while the industry consolidates standards."
What is missing is a list of the protocols it actually supports. Neither the IXO One announcement, the September Agentic Suite announcement, the product page nor the product blog names ACP (OpenAI and Stripe's Agentic Commerce Protocol), AP2 (Google's Agent Payments Protocol), UCP, Visa Intelligent Commerce or Mastercard Agent Pay. The only protocol named is the Model Context Protocol used by the internal-facing MCP Server. The list of "supported third-party agents" is also not disclosed.
The publicly announced customer is Tilopay, a payments company serving merchants in Latin America and the Caribbean. Its co-founder Henry Nanne praised not having to re-engineer checkout every time a new agent or protocol appears.
MCP Server Is a Tool for Internal Payment Operations
The third component, MCP Server, is a governance layer that lets AI assistants such as Claude or ChatGPT perform payment and tokenization tasks. Before an action runs, it checks the instructing user's existing permissions and which token vaults they are allowed to access. API keys are never passed to the AI side, and every action is logged and tied to the user.
It does not touch the customer buying experience directly, but it is a useful example of a design that keeps AI permissions from exceeding those of the person who authorized it when payment teams automate routine work.
Caveats: Not Enough Information to Judge Yet
Some points cannot be settled from the vendor's account alone.
First, timing. General availability of the unified experience is early 2027, too late for the 2026 holiday season. The Agentic Suite itself has been available since September, but anyone evaluating IXO One as an integrated offering with unified pricing is looking at next year. The details of the new commercial model are also not disclosed.
Second, where the lock-in moves. IXO One promises to reduce dependence on PSPs, but in exchange the orchestration layer and token vault sit with IXOPAY. Even if Universal Tokens are "portable across providers," the public materials do not explain the terms for moving tokens from IXOPAY to a different orchestration provider.
Third, how much the evidence actually counts. Even with records of agent identity and consent, how far they are accepted as evidence in card scheme dispute processes depends on the schemes' rules. Boboev's article also argues that the allocation of liability for agent transactions is not yet settled. Holding the record is a necessary condition, but it does not guarantee winning a dispute.
There is also support for the direction of demand. Jordan McKee, Research Director at 451 Research, part of S&P Global, noted that payments have become a boardroom priority, that multi-processor setups are spreading, and that merchants want to plug into new commerce frameworks such as agentic commerce. He concluded that payment providers should prioritize modular and composable offerings.
What Merchants Should Check Now
Whether or not you use IXOPAY, this announcement offers a useful lens for reviewing your own payment stack.
The most important question is whether, for orders placed through agents, you can store which agent bought, under what permission from the customer, and with what intent, linked to the payment record. In most cases, today's order data and PSP transaction records have no place for these fields. It is worth reviewing, together with the team that handles chargebacks, what evidence you could submit in a dispute.
Next, ask your current PSPs and orchestration providers which agentic payment protocols they support and when. Even with a product that claims to be "protocol-agnostic," you cannot tell whether it works for your sales channels until you confirm which protocols it actually supports.
Conclusion
IXO One adds a "record of consent and intent" for agentic payments to unified payment orchestration, a product in an established market. The genuinely new part is the Agentic Suite released in September, and Universal Tokens in particular confront head-on the premise that liability for agent transactions stays with the merchant.
The next things to watch are the disclosure of supported protocols and the pricing at general availability in early 2027. Ultimately, the value of mechanisms like this will be decided by how card schemes treat records of agent identity and consent in dispute processing.
