IXOPAY
A payment orchestration and tokenization company formed from IXOPAY and TokenEx, with routing across 200+ PSPs.
IXOPAY sells payment orchestration, TokenEx tokenization and payment analytics to enterprise merchants and to processors that white-label it. Routing runs through a meta-connector: rules are set up as a decision tree, can test risk score or a connector’s recent chargebacks, and can name fallback connectors tried in order. IXOPAY says it connects to more than 200 payment service providers and 300 payment methods. It describes itself as a PCI DSS Level 1 service provider and does not publish pricing.
- Website
- ixopay.com
- Infrastructure layers
- Payment orchestration, tokenization
- Products (as published)
- Payment orchestration (meta-connector routing, cascading, fallback, load balancing, reconciliation)
TokenEx tokenization (Universal Tokens, network tokens; Core, Connect and Alternative Payments packages)
Risk Management Engine (risk profiles and rules)
Payments Intelligence and IXONav (analytics, anomaly detection)
PCI compliance services (Aperia Compliance, PCI DSS Levels 3 and 4)
Agentic Suite (Payment Agent, MCP Server) - Client types
- Enterprise merchants, platforms, ISOs and payment processors (white-label)
- Regions served
- Global; offices in Tulsa, Lehi, Dallas and Vienna
- API documentation
- documentation.ixopay.com
- Date checked
- Profile type
- Standard
Questions
What is the link between IXOPAY and TokenEx?
Can IXOPAY routing rules be managed through an API?
Does IXOPAY publish pricing?
See also
Sources
- IXOPAY: TokenEx and IXOPAY merge (April 17, 2024)
- IXOPAY: merger with Aperia Compliance (December 4, 2024)
- IXOPAY: PCI DSS v4.0.1 shared responsibility matrix
- IXOPAY docs: smart transaction routing
- IXOPAY docs: connector routing
- IXOPAY docs: routing conditions
- IXOPAY docs: risk profiles
- IXOPAY: TokenEx packages (January 20, 2026)
- IXOPAY: Payments Intelligence and IXONav (June 2, 2026)
- IXOPAY: tokenization cost post (January 13, 2022)
- Checked September 27, 2026.
Source: each provider’s own documentation, product pages, official announcements and filings, and official registers for licences, as linked in each profile. Fields a provider does not publish stay empty. How we build profiles: methodology.