Zero hot-wallet pooling
0.5%flat gateway fee
16 Proofsoperational explainers
No custodydirect multisig & vault routing
Testnetbefore mainnet review
Route 99.5% of checkout revenue straight into corporate multisig and cold vaults.
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.
Multisig & Cold-Vault Routing means your checkout settlement address is your own institutional vault from second zero. Funds move directly from the buyer payment transaction into your 2-of-3 Safe{Wallet}, Squads v4 vault, Ledger address, or Fireblocks workspace — eliminating processor insolvency risk and secondary sweep gas.
01
Treasury team verifies vault deployment on each target chain (for example, deploying Safe on Base, Arbitrum, and Polygon separately).
02
Merchant configures the verified public multisig, hardware, or MPC deposit address inside XPayr Wallet Settings.
03
Customer completes checkout; 99.5% settles directly into the cold/multisig vault while XPayr records the deterministic receipt.
04
Finance exports balanced QuickBooks, Xero, or NetSuite ledger entries backed by @xpayr/payment-evidence.
Who pays gas?
Receiving funds into a Safe, Squads, Ledger, or Fireblocks address costs the merchant $0 in sweep gas; outbound treasury transfers pay standard chain gas when signers execute.
Operational limit
Smart-contract multisigs (such as Safe) are chain-specific — merchants must verify contract deployment on the exact Layer-2 Chain ID before enabling Mainnet.
FAQ
What problem does this XPayr flow solve?
Multisig & Cold-Vault Routing means your checkout settlement address is your own institutional vault from second zero. Funds move directly from the buyer payment transaction into your 2-of-3 Safe{Wallet}, Squads v4 vault, Ledger address, or Fireblocks workspace — eliminating processor insolvency risk and secondary sweep gas.
Who pays gas or network fees?
Receiving funds into a Safe, Squads, Ledger, or Fireblocks address costs the merchant $0 in sweep gas; outbound treasury transfers pay standard chain gas when signers execute.
What should merchants not assume?
Smart-contract multisigs (such as Safe) are chain-specific — merchants must verify contract deployment on the exact Layer-2 Chain ID before enabling Mainnet.
Verifiable Open-Source & AI Protocol Registry
Publicly 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.