Understand exactly how XPayr moves from checkout to operational proof.
Clear explainers for merchants evaluating crypto payments across 16 blockchains: 0.5% fee split, non-custodial multisig & cold-vault routing, 1% Exchange QR tolerance, HTTP 402 JWKS paywalls, EU MiCA EURC scope, TRON/Solana checkout, webhooks, fee delegation, AI agent guardrails, and ES256 wallet licensing.
Answer the questions buyers ask before they trust a crypto payment stack.
How XPayr fee split works
XPayr applies a flat 0.5% gateway fee to completed payment sessions. Network gas is separate and depends on the selected chain, wallet, and token flow.
Read explainerHow non-custodial settlement works
XPayr is built as non-custodial payment infrastructure. Merchants keep wallet control while XPayr handles sessions, status records, routing context, and webhooks.
Read explainerHow TRON USDT checkout works
TRON USDT is useful for merchants whose customers already hold USDT on TRON. The key operational detail is energy/bandwidth cost visibility before the payment is attempted.
Read explainerHow Solana SOL, USDC, and USDT checkout works
Solana support lets merchants accept SOL, USDC, and USDT where the merchant rail and wallet route are enabled. XPayr records payment state and transaction references for reconciliation.
Read explainerHow webhooks update merchant systems
XPayr webhooks help merchant systems react to payment status changes without manually checking the dashboard.
Read explainerHow testnet evaluation works
Testnet evaluation lets merchants prove the payment flow, integration behavior, and operational records before mainnet activation.
Read explainerHow Player Deposits work
Player Deposits helps operators connect payment sessions to internal user identifiers without treating XPayr as a custody account.
Read explainerHow Payout Hub works
Payout Hub is designed to organize payout batches, recipients, amounts, approval state, and transaction hashes while keeping signing and funds under the configured wallet flow.
Read explainerHow Settlement Router works
Settlement Router stores merchant preferences for preferred settlement assets and active same-chain routes where supported.
Read explainerHow Fee Delegation works
Fee Delegation lets merchants configure sponsored-fee policies for supported permit-based token flows. Unsupported tokens fall back to normal wallet payment.
Read explainerHow AI Agent spend guardrails and MCP policies work
XPayr Agent Guardrails enforce per-transaction limits, daily rolling budgets, auto-approval thresholds, and chain whitelists across all 21 MCP tools.
Read explainerHow ES256 wallet-bound software licenses work
XPayr License Kit binds software, SaaS, browser extension, and plugin entitlements to the payer wallet and signs short-lived ES256 JWT tokens verifiable via public JWKS.
Read explainerHow 1% (max $0.50) Exchange QR underpayment tolerance works
XPayr Direct Exchange QR allows merchants to configure a strict 1% (capped at $0.50 USD equivalent) underpayment tolerance so minor centralized-exchange withdrawal fee deductions resolve automatically as payment.underpaid_accepted.
Read explainerHow HTTP 402 AI/API paywalls and offline JWKS verification work
XPayr pairs /.well-known/x402.json challenge headers with ES256 JWT access receipts verifiable offline against /.well-known/jwks.json across Cloudflare Workers, FastAPI, Express, and Next.js.
Read explainerHow direct settlement to Safe, Squads, Ledger, and Fireblocks works
Because XPayr never holds merchant private keys or pools balances in processor hot wallets, merchants can set Safe{Wallet}, Solana Squads v4, Ledger hardware addresses, or Fireblocks MPC vaults as their direct checkout destination.
Read explainerHow EU MiCA, EURC, and XPayr non-custodial software boundaries align
XPayr operates strictly as non-custodial technical checkout and webhook software — never safeguarding private keys, holding client funds, or operating an omnibus custodial exchange book.
Read explainerPublicly auditable SDKs, cryptographic evidence envelopes, and MCP registries.
Official 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.
Need to prove the flow before production?
Use testnet checkout, API docs, webhook guides, and operational explainers before asking for mainnet activation.