HD Wallet Derivation
One BIP39 master seed derives every merchant wallet across ETH, BSC, Solana and Bitcoin — nothing to store, just derive on demand.
Non-custodial HD-wallet payments across four chains, plus a card aggregator with automatic sequential fallback — all managed from a single, beautiful dashboard.
Wallets, monitoring, card routing and reconciliation — one platform instead of four integrations.
One BIP39 master seed derives every merchant wallet across ETH, BSC, Solana and Bitcoin — nothing to store, just derive on demand.
Workers poll RPC nodes at a fixed cost — eth_getLogs, a BTC block cursor and Solana signatures — regardless of merchant count.
Connect Stripe, a Forex PSP, or any webhook PSP. A decline retries on the next provider automatically, transparent to the customer.
Every PSP callback is verified, normalised to one event format, and forwarded to your endpoint with exponential-backoff retries.
Funds settle directly to merchant-derived addresses. The platform never takes custody — keys stay yours, end to end.
USD stable currency settlements and card payments in one ledger — reconcile volume, withdrawals and wallets without leaving the page.
Request an address per chain — derived on demand from your master seed. No pre-funding, no storage.
One call. POST /v1/wallets returns four addresses and the derivation index you can reconcile against later.
USD stable currency is watched on-chain to required confirmations; cards route through your PSPs with automatic fallback.
A decline is not a failure. The charge retries on the next provider in your chain until one authorises — the customer sees a single attempt.
A single normalised webhook fires to your endpoint, and funds sweep to your treasury above the threshold.
One event format. Card and on-chain settlements arrive on the same schema, signed, with exponential-backoff retries.
0x7a2f…b91cm/44'/60'/0'/0/70x7a2f…b91cm/44'/60'/0'/0/79xQe…7Vhkm/44'/501'/7'bc1q…04tam/84'/0'/0'/0/7POST https://acme.com/hooks/xlopay { "event": "payment.settled", "amount": "1000.00", "source": "chain:ethereum", "confirmations": 12 }
0xTREAS…9f21+$1,000.00The same gateway serves very different money flows — pick the rails that fit each product line.
Derive a wallet per seller and settle straight to them. No pooled balance to reconcile, no payout queue to babysit.
Same checkout for your customer. Very different exposure for your treasury.
Non-custodialThe platform can watch a payment and report it. It cannot move your money.
Addresses are derived from your seed; private keys are generated at use and never stored server-side or logged.
Every event carries an HMAC signature and a replay-safe timestamp, so your endpoint can reject anything it did not expect.
Per-chain thresholds decide when a payment counts as settled — 12 blocks on Ethereum, 2 on Bitcoin, finality on Solana.
Admin actions, PSP responses and sweep transactions are recorded with actor, timestamp and payload for every merchant.
Card providers, wallets, storefronts and back-office tools — connected through one API key.
Reconciliation, declines and payout delays are the three complaints that go quiet first.
We moved 60% of volume on-chain in six weeks. Settlement went from four days to about nine minutes, and our treasury finally reconciles itself.
The fallback routing paid for itself immediately — recovered roughly 11% of renewals that used to fail outright on a single acquirer.
One webhook format for cards and four chains. We deleted an entire normalisation service we had been maintaining for two years.
No. Payments settle to addresses derived from your own master seed, and card volume settles through your own PSP accounts. The platform reads chain state and reports it — there is no pooled balance under our control.
The charge is retried against the next provider in your configured chain, in order, until one authorises or the list is exhausted. The customer sees a single attempt; your webhook receives one final result plus the per-provider attempt log.
USD stable currency on Ethereum, BNB Chain and Solana, plus native Bitcoin. Each chain has its own confirmation threshold and its own derivation path, all from the same seed.
Balances above your threshold sweep automatically to the treasury address you nominate, and manual withdrawals are available from $5. Every sweep is recorded with its transaction hash.
Yes. The dashboard and the worker set run on your own infrastructure against your own RPC endpoints. The mock API mode lets your team evaluate the full UI before any keys exist.
Most teams ship a first payment the same day: derive a wallet, point a webhook at your endpoint, and connect one PSP. Sequential fallback and auto-sweeps are configuration, not code.
Spin up the merchant dashboard, connect a PSP, and derive your first wallet in minutes.