iGaming-операции
0.5%фиксированная плата за шлюз
16 Proofsoperational explainers
Нет опекиdirect multisig & vault routing
Тестовая сеть (Testnet)перед проверкой основной сети
Map crypto deposits to player, order, or account references.
Депозиты игроков помогают операторам связывать платежные сеансы с внутренними идентификаторами пользователей, не рассматривая XPayr как счет депо.
Player Deposits means each payment session can carry merchant-side references such as player ID, account ID, order ID, or campaign source so operations can reconcile who paid and why.
01
Merchant creates a session with player or account metadata.
02
Customer pays through the selected route.
03
XPayr records the reference with amount, token, network, and status.
04
Merchant maps the confirmed event into its own player ledger or order system.
Who pays gas?
Gas follows the customer wallet and selected payment network. Player metadata does not change chain fees.
Operational limit
XPayr records payment references; the merchant remains responsible for account crediting rules, fraud controls, and licensed operations.
FAQ
What problem does this XPayr flow solve?
Player Deposits means each payment session can carry merchant-side references such as player ID, account ID, order ID, or campaign source so operations can reconcile who paid and why.
Who pays gas or network fees?
Gas follows the customer wallet and selected payment network. Player metadata does not change chain fees.
What should merchants not assume?
XPayr records payment references; the merchant remains responsible for account crediting rules, fraud controls, and licensed operations.
Verifiable Open-Source & AI Protocol Registry
Publicly auditable SDKs, cryptographic evidence envelopes, and MCP registries.
Официальный MCP-сервер с 21 инструментом
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.
Необходимо доказать поток перед началом производства?
Используйте проверку тестовой сети, документацию по API, руководства по веб-перехватчикам и пояснения по работе, прежде чем запрашивать активацию основной сети.