A crypto payment fee model your finance team can explain in one line.
XPayr erhebt eine pauschale Gateway-Gebühr von 0,5 % auf abgeschlossene Zahlungssitzungen. Netzwerkgas ist separat und hängt von der ausgewählten Kette, dem Wallet und dem Token-Flow ab.
XPayr fee split means a completed crypto payment session records the invoice amount, the 0.5% gateway fee, the chain-level cost boundary, and the net merchant amount. For a $1,000 invoice, the XPayr-Gateway-Gebühr is $5 before network gas or external wallet costs.
Merchant creates a session with invoice amount, network, token, and customer reference.
Customer pays from a wallet on the selected network.
XPayr records status, transaction reference, gateway fee, and reconciliation fields.
Merchant reviews the invoice, fee, net amount, token, network, and webhook history.
Who pays gas?
Network gas is not included in the 0.5% gateway fee. It is charged by the selected blockchain and wallet path.
Operational limit
Fee records depend on completed payment sessions. Failed, expired, or abandoned sessions are not production revenue events.
FAQ
What problem does this XPayr flow solve?
XPayr fee split means a completed crypto payment session records the invoice amount, the 0.5% gateway fee, the chain-level cost boundary, and the net merchant amount. For a $1,000 invoice, the XPayr-Gateway-Gebühr is $5 before network gas or external wallet costs.
Who pays gas or network fees?
Network gas is not included in the 0.5% gateway fee. It is charged by the selected blockchain and wallet path.
What should merchants not assume?
Fee records depend on completed payment sessions. Failed, expired, or abandoned sessions are not production revenue events.
Publicly auditable SDKs, cryptographic evidence envelopes, and MCP registries.
Offizieller 21-Tool-MCP-Server
Registered as io.github.xpayrcom/xpayr-mcp-server on the Official Anthropic MCP Registry and published as @xpayr/mcp-server on NPM and ghcr.io/xpayrcom/xpayr-mcp-server:latest.
Merkle Payment Evidence & ES256 Tokens
Verify on-chain settlement envelopes with @xpayr/payment-evidence and offline-verifiable ES256 wallet licenses with @xpayr/extension-kit.
30 Open-Source Repositories & RFC 9116
Inspect all 20 REST API v1 schemas interactively at api-docs.xpayr.com, review our 30 repositories at github.com/xpayrcom, and check /.well-known/security.txt & /.well-known/jwks.json.
Müssen Sie den Ablauf vor der Produktion prüfen?
Nutzen Sie Testnet Checkout, API-Dokumente, Webhook-Anleitungen und Betriebserklärungen, bevor Sie eine Mainnet-Aktivierung anfordern.