Stablecoin preference
0.5%flat gateway fee
16 Proofsoperational explainers
No custodydirect multisig & vault routing
Testnetbefore mainnet review
Prefer stablecoin settlement without hiding route and liquidity limits.
Settlement Router stores merchant preferences for preferred settlement assets and active same-chain routes where supported.
Settlement Router lets a merchant define settlement preferences such as receiving a preferred stablecoin. Live execution depends on the active route, supported network, deployed contract, token liquidity, and review status.
01
Merchant chooses accepted assets and preferred settlement asset.
02
XPayr checks active route configuration and supported rails.
03
Checkout runtime applies eligible same-chain route behavior where configured.
04
Merchant reviews records for accepted asset, route, net amount, and status.
Who pays gas?
Swap, routing, or bridge-related gas and liquidity costs depend on the route and are not part of the base 0.5% gateway fee.
Operational limit
Cross-chain routing is not automatic unless a verified route, liquidity path, and execution configuration are active.
FAQ
What problem does this XPayr flow solve?
Settlement Router lets a merchant define settlement preferences such as receiving a preferred stablecoin. Live execution depends on the active route, supported network, deployed contract, token liquidity, and review status.
Who pays gas or network fees?
Swap, routing, or bridge-related gas and liquidity costs depend on the route and are not part of the base 0.5% gateway fee.
What should merchants not assume?
Cross-chain routing is not automatic unless a verified route, liquidity path, and execution configuration are active.
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.