iGaming operations
0.5%flat gateway fee
No custodymerchant wallet control
Testnetbefore mainnet review
Webhooksoperational records
Map crypto deposits to player, order, or account references.
Player Deposits helps operators connect payment sessions to internal user identifiers without treating XPayr as a custody account.
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.
Need to prove the flow before production?
Use testnet checkout, API docs, webhook guides, and operational explainers before asking for mainnet activation.