Operational records
0.5%flat gateway fee
No custodymerchant wallet control
Testnetbefore mainnet review
Webhooksoperational records
Turn on-chain payment status into clean order and finance events.
XPayr webhooks help merchant systems react to payment status changes without manually checking the dashboard.
XPayr webhooks send payment lifecycle events to a merchant endpoint so order systems, player ledgers, finance tools, or internal dashboards can update when a checkout session changes status.
01
Merchant configures a webhook endpoint.
02
XPayr signs and sends payment status events.
03
Merchant verifies the signature and idempotency key.
04
Merchant updates the order, player, invoice, or ledger record.
Who pays gas?
Webhooks do not create chain gas. They report off-chain status updates after payment activity.
Operational limit
Webhook receivers must handle retries, duplicate events, delayed confirmations, and signature verification.
FAQ
What problem does this XPayr flow solve?
XPayr webhooks send payment lifecycle events to a merchant endpoint so order systems, player ledgers, finance tools, or internal dashboards can update when a checkout session changes status.
Who pays gas or network fees?
Webhooks do not create chain gas. They report off-chain status updates after payment activity.
What should merchants not assume?
Webhook receivers must handle retries, duplicate events, delayed confirmations, and signature verification.
Need to prove the flow before production?
Use testnet checkout, API docs, webhook guides, and operational explainers before asking for mainnet activation.