IXOPAY

ixopay.com ↗

Connect payment routing, tokenization and reconciliation tools

SI Score
80/100
Pricing
Subscription AI reading, not confirmed
Free plan
No AI reading, not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about IXOPAY

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the IXOPAY homepage

What it does

IXOPAY provides payment orchestration, processor adapters, tokenization, reconciliation and payment-intelligence services. Its TokenEx packages form part of the same platform offering. Businesses use configured merchant accounts and paid plans; free sandbox access is available to evaluate tokenization before a live agreement.

Configure a connector for each payment provider first. In the merchant's Connectors Overview, choose New Connector and then + New Meta-Connector to group the routes. Enter the base details, select a default connector and create the configuration.

Open Rules in Connector Details. Drag in a condition, such as customer billing country, and its Route to Connector action, then save. A second consecutive routing action can act as a fallback when the first provider returns a suitable decline code. The default handles cases where no action is defined.

Reconciliation checks a different part of the payment. IXOPAY compares provider settlement statements with recorded transactions and the fees entered in its fee-management tools. The reconciliation overview identifies missing data, unrecognized transactions and fee discrepancies for staff to resolve. Keep that financial review separate from a successful checkout result.

Test the integration in the sandbox before switching to production. The public tokenization evaluation page advertises plans starting at $1,000 per month; request the actual package, usage charges and module entitlements for the planned orchestration setup. Provider acceptance and bank-arrival times still depend on the connected services and merchant contracts.

Strengths

  • Provider files are normalized into a common structure for download or transfer to other systems.
  • Merchant web-user permissions can be limited to selected activities, including viewing transactions or changing payment templates.

Watch out for

  • Recurring charges stay with the original connector unless Re-route recurring transaction is enabled.
  • Sandbox and production accounts are separate, so existing production credentials cannot be reused for sandbox tests.
  • Mobile browsers have limited support for administration tasks such as Post-Processing and the Fast Editor.

Best for

  • Payment teams operating several processor connections
  • Finance teams investigating settlement and fee discrepancies

Sources