Create a merchant account, add a payout wallet, choose network and token, then publish your payment link, widget, or button.
FAQ
XPayr FAQ Database
Find answers to common questions about setup, payments, and integrations.
Getting Started
Yes. Use testnet flows to validate checkout, wallet connection, and invoice behavior before production.
No. You can launch with no code tools from merchant dashboard and use API only when you need advanced integrations.
Most merchants publish their first crypto checkout flow in minutes.
Payments and Donations
Payment links are fixed checkout flows. Donation links are support focused flows for community contributions.
Yes. Reusable links can collect multiple payments over time based on your campaign flow.
Use widget for embedded checkout, button for branded call to action, and direct link for fast sharing in chats or social.
Yes. You can allow custom amounts or keep fixed amounts depending on the flow you configure.
Wallet and Networks
XPayr supports EIP compatible browser wallets and modern wallet connection flows.
The selected wallet is not registered for that chain in your merchant settings. Add and register it for the selected network.
Yes. Disconnect the current wallet and reconnect with the address you want to use before creating or confirming payment.
Open payout wallets in merchant panel, select network, paste wallet address, and save after validation.
Fees and Settlement
XPayr applies a transparent 0.5 percent gateway fee. Network gas fees are blockchain costs and vary by chain state.
Gas costs are paid on chain by the transaction sender according to network conditions and selected token flow.
After on chain confirmation, funds move directly into your configured wallet flow.
No hidden gateway fees. You see platform fee and network costs clearly in the flow.
Security and Compliance
Use 2FA, whitelist controls, and webhook signature validation to secure account and payout operations.
No. Core trust branding remains visible while your brand elements are shown in checkout header.
It restricts sensitive actions to approved IP addresses and reduces unauthorized admin actions.
Yes. Enable whitelist enforcement to allow payouts only to approved wallet and currency pairs.
API and Webhooks
Validate the signature header with your webhook secret before processing payload data.
API key identifies integration context. Secret key authorizes protected server side API requests.
Common statuses include pending, confirmed, failed, and expired with related update events.
Use idempotency in your backend and store processed event identifiers before applying business updates.
Troubleshooting
This usually means network mismatch, token mismatch, missing wallet registration, or contract validation rejection.
Verify invoice belongs to your merchant account and session data exists in current environment.
The session reached its time limit or was already finalized by a completed flow.
Check wallet extension is installed, unlocked, on correct chain, and popups are not blocked by browser settings.
Account and Team
Yes. Teams can share operational workflows while payment controls remain centralized.
Use forgot password flow and recovery steps, then update security settings after access is restored.
Open API Keys in merchant panel to create, rotate, and revoke credentials.
Yes. Admin users can bypass maintenance page while public visitors still see maintenance screen.