Choose by operating model, not just feature count.
Cambie cuando el pago administrado, las rutas de las monedas estables, los registros del panel y el lanzamiento más rápido sean más valiosos que el autohospedaje.
Gateway comparison
Servidor XPayr y BTCPay
A direct comparison for merchants evaluating crypto checkout, liquidación de billetera, stablecoin rails, fees, API/webhooks, testnet evaluation, and operational payment records.
Fee comparison needs context.
Servidor BTCPay is open-source and self-hosted. There is no third-party processor fee, but the merchant operates the server, security, uptime, and infrastructure.
XPayr aplica una comisión fija de pasarela del 0.5% gateway fee per successful transaction before network gas, swap, bridge, or third-party route costs.
Servidor BTCPay documentationWhere each platform fits
| Decision area | XPayr | Servidor BTCPay |
|---|---|---|
| Infrastructure | Managed checkout layer with merchant wallet routing. | Self-hosted payment server operated by the merchant. |
| Cost model | 0.5% gateway fee per successful payment before chain gas. | No processor fee, but server, uptime, and maintenance costs remain. |
| Asset strategy | Stablecoin-focused coverage across supported EVM, TRON, and Solana routes. | Strong fit for Bitcoin-first self-hosted payments. |
| Best buyer | Teams that want faster launch and operational payment records. | Technical teams that want full self-hosted ownership. |
| 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. |
When XPayr is the cleaner choice
XPayr is stronger when the merchant wants wallet control without running and maintaining a payment server.
- Teams that do not want to deploy, secure, monitor, and maintain a payment server.
- Merchants that need stablecoin checkout routes beyond a Bitcoin-first setup.
- Businesses that want testnet checkout, dashboard records, and API/webhooks quickly.
- Operators that need recurring records, payout preparation, or route policy controls.
When Servidor BTCPay may still win
Servidor BTCPay can still be best for technical, Bitcoin-first teams that want open-source self-hosting and full infrastructure ownership.
- Merchants that want open-source self-hosting and full infrastructure ownership.
- Bitcoin-first teams that accept server maintenance as part of the operating model.
- Organizations that prefer 0% third-party processor fees and can handle hosting, security, and uptime themselves.
Questions before choosing
Is XPayr cheaper than Servidor BTCPay?
XPayr aplica una comisión fija de pasarela del 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 is stronger when the merchant wants wallet control without running and maintaining a payment server.
When might Servidor BTCPay still be better?
Servidor BTCPay can still be best for technical, Bitcoin-first teams that want open-source self-hosting and full infrastructure ownership.
Does XPayr support AI agents and the Model Context Protocol (MCP) compared with Servidor BTCPay?
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.