Gateway comparison

XPayr vs Plisio

A direct comparison for merchants evaluating crypto checkout, wallet settlement, stablecoin rails, fees, API/webhooks, testnet evaluation, and operational payment records.

TL;DR

Choose by operating model, not just feature count.

Switch when you want true self-custodial wallet settlement (no withdrawal step), white-label branding without a 1.2% markup, and AI/MCP developer tooling.

Pricing snapshot

Fee comparison needs context.

Plisio advertises a 0.5% base gateway fee for standard hosted crypto invoices and 1.2% for its white-label/custom branding plan, using Plisio-managed wallet balances and withdrawal flows.

XPayr charges a flat 0.5% gateway fee per successful transaction before network gas, swap, bridge, or third-party route costs.

Plisio pricing page
At a glance

Where each platform fits

Decision areaXPayrPlisio
Custody architecture 100% non-custodial direct merchant-wallet settlement. Gateway-managed wallet balances requiring outbound withdrawals.
White-label checkout fee Flat 0.5% gateway fee across hosted, modal, and branded flows. 0.5% standard hosted tier; 1.2% fee tier for white-label checkout.
Developer & AI stack OpenAPI 3.1.0, Node/PHP SDKs, ES256 License Kit, 21-tool MCP server. REST API, shopping-cart plugins, and dashboard wallet tools.
Best buyer Teams demanding zero-custody treasury control and flat 0.5% white-label UX. Merchants comfortable holding funds inside a processor wallet.
AI Agent & MCP Server Integration Official 21-tool Model Context Protocol server (@xpayr/mcp-server on NPM & Official Anthropic MCP Registry io.github.xpayrcom/xpayr-mcp-server), OpenAPI 3.1.0 playground (api-docs.xpayr.com), and policy-controlled AI agent commerce. Check official provider documentation for current AI agent or MCP protocol support.
XPayr fit

When XPayr is the cleaner choice

XPayr keeps the flat 0.5% fee without charging 2.4x extra for white-label UX, routes 99.5% directly to your own self-custodial wallet instead of a gateway wallet balance, and adds ES256 License Kit plus 21 MCP tools.

  • Merchants requiring immediate direct-to-wallet settlement instead of gateway withdrawal queues.
  • Brands wanting custom/white-label checkout UX at 0.5% rather than a 1.2% tariff.
  • SaaS & plugin authors issuing cryptographic ES256 wallet licenses (/developers/license-kit).
  • Teams using WooCommerce, Magento 2, PrestaShop, Shopware, OpenCart, or Zen Cart (/integrations).
Competitor fit

When Plisio may still win

Plisio can fit small stores that specifically want an internal gateway-managed multi-coin balance wallet.

  • Users who specifically want Plisio to generate and hold an internal custodial dashboard wallet for them.
Evaluation path: run a free XPayr testnet checkout, compare the invoice amount, 0.5% gateway fee, token/network, transaction hash, webhook event, and dashboard record against the flow you use today.
🛡️ Calculate Chargeback & Reserve Savings 🧮 0.5% Fee Calculator 📦 Batch Payout Planner 🔑 ES256 License Verifier ⚡ Live System Status
FAQ

Questions before choosing

Is XPayr cheaper than Plisio?

XPayr charges a flat 0.5% gateway fee per successful payment before chain gas or route costs. The right comparison depends on the competitor flow, conversion settings, network fees, settlement model, and merchant volume.

When should a merchant choose XPayr?

XPayr keeps the flat 0.5% fee without charging 2.4x extra for white-label UX, routes 99.5% directly to your own self-custodial wallet instead of a gateway wallet balance, and adds ES256 License Kit plus 21 MCP tools.

When might Plisio still be better?

Plisio can fit small stores that specifically want an internal gateway-managed multi-coin balance wallet.

Does XPayr support AI agents and the Model Context Protocol (MCP) compared with Plisio?

Yes. XPayr provides an official 21-tool MCP server (@xpayr/mcp-server on NPM and io.github.xpayrcom/xpayr-mcp-server on the Official Anthropic MCP Registry) plus policy-controlled AI agent payment intents with human-in-the-loop approval guardrails.