Prepare staff, affiliate, player, or reward payouts without custody confusion.
Payout Hub is designed to organize payout batches, recipients, amounts, approval state, and transaction hashes while keeping signing and funds under the configured wallet flow.
Payout Hub helps merchants prepare and track payout batches. It is not a promise that XPayr holds merchant funds or executes every payout automatically across every rail.
Merchant creates a recipient batch with amounts and payout purpose.
Batch is reviewed against merchant policy and available route settings.
Authorized wallet flow signs supported transactions.
XPayr records payout status, transaction references, and operational notes.
Who pays gas?
Payout gas is paid by the wallet or relayer flow that signs and submits the transaction.
Operational limit
Execution depends on supported route, wallet, token, network, review state, and configured signing model.
FAQ
What problem does this XPayr flow solve?
Payout Hub helps merchants prepare and track payout batches. It is not a promise that XPayr holds merchant funds or executes every payout automatically across every rail.
Who pays gas or network fees?
Payout gas is paid by the wallet or relayer flow that signs and submits the transaction.
What should merchants not assume?
Execution depends on supported route, wallet, token, network, review state, and configured signing model.
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.