A non-custodial checkout decision is not just a feature checklist. It is a choice about wallet control, operational records, payer gas boundaries, settlement preferences, and whether your business wants a payment layer or a full financial account.
XPayr focuses on payment sessions, links, widgets, API/webhooks, stablecoin routes, direct wallet settlement, and a flat 0.5% gateway fee. It is not trying to be a custody account, bank offramp, exchange, or self-hosted server project.
Cross-chain routing, auto-convert, gas sponsorship, and advanced settlement flows depend on active route, token, contract, liquidity, relayer, and merchant policy configuration.
Does the payment flow route to merchant-controlled wallets, or does it create a provider balance or account-led settlement model?
Can the team reconcile invoice amount, fee, token, network, transaction hash, status, and webhook event in one workflow?
Does the gateway support the stablecoin rails your buyers actually use, including payer-side gas expectations?
Can production activation stay review-controlled for regulated or higher-risk categories while testnet remains open?
Can developers test payment sessions, webhook signatures, and checkout behavior before production funds are involved?
Switch when checkout records, direct wallet settlement, and operational route control matter more than a very broad currency catalog.
Open comparisonSwitch when the operational goal is a lean checkout layer rather than a gateway-wallet-conversion suite.
Open comparisonSwitch when the merchant wants global checkout infrastructure without making Coinbase the central business account.
Open comparisonSwitch when direct wallet settlement and lower gateway fee clarity matter more than fiat-first payment-provider operations.
Open comparisonSwitch when managed checkout, stablecoin routes, dashboard records, and faster launch are more valuable than self-hosting.
Open comparison