XPayr eliminates counterparty balance risk by never holding merchant funds or private keys. Every payment, webhook, software license, and AI agent intent is backed by publicly verifiable cryptographic proofs.
99.5% of every confirmed payment routes directly to the merchant destination wallet on-chain while 0.5% routes to XPayr. Browser callbacks are never trusted without independent on-chain RPC receipt verification.
Every webhook payload is signed with a merchant-specific 32-byte secret in X-XPayr-Signature, paired with deterministic event IDs for idempotent order processing.
Wallet-bound software and extension entitlements issue short-lived ES256 JWTs verifiable offline against /.well-known/jwks.json (kid: lk-c3a9478746f1) via @xpayr/extension-kit (v0.2.0).
Verify chain ID, token contract, transfer amount, recipient wallet, and block finality independently with open-source @xpayr/payment-evidence (v0.2.0).
AI agents authenticate with scoped agk_ credentials subject to per-transaction caps, daily rolling limits, network whitelists, and a human-in-the-loop approval queue.
Published vulnerability contact policy at /.well-known/security.txt, TLS 1.3 + HSTS preload headers, SafeShare secret sharing, and structured compliance review for regulated verticals.
Never. XPayr is 100% non-custodial. Merchants provide only public destination wallet addresses, and customers sign transactions directly inside their own wallets or send from exchanges.
Every webhook includes an X-XPayr-Signature HMAC-SHA256 header computed with your 32-byte endpoint secret. Every software license JWT is signed with ES256 (P-256) and verifiable offline against https://xpayr.com/.well-known/jwks.json.
Security researchers can inspect our machine-readable disclosure policy at https://xpayr.com/.well-known/security.txt and report findings directly through our SafeShare and security contact channels.