Home / Security

We can't touch your money. And you can check that yourself.

Zyrox is non-custodial by design. Payments go to addresses derived from your own wallet, we never hold your keys, and every claim on this page is something you can verify without trusting us.

🔑

No private keys

We only ever see your public key (xPub). It can generate addresses and watch payments, but it cannot sign a transaction.

🧊

Nothing to freeze

There is no balance on our side. Money lands in your wallet the moment the customer pays, so there is nothing for us to hold back.

🔍

Everything on-chain

Every payment has a transaction ID you can open in Etherscan, Tronscan or any Bitcoin explorer.

Non-custodial architecture

Why a custodial gateway can freeze you, and Zyrox can't

A custodial processor collects your customers' money into its own accounts and pays you out later. Between those two moments it can delay, hold or freeze the funds. With Zyrox that window does not exist.

ZyroxCustodial gateway
Where the payment goesYour walletGateway's account
Who holds the keysOnly youThe gateway
Payout delayNoneDays or weeks
Can funds be frozenNoYes
HD wallet addresses

A fresh address for every invoice, from your own key

Zyrox derives payment addresses from your xPub using the BIP-32/44 standard used by MetaMask, Ledger, Trezor, Trust Wallet and Exodus.

  • No address reuse. Each invoice gets its own address, so payments are easy to match to orders and harder to trace.
  • Deterministic. The same xPub always gives the same sequence of addresses, so you can re-create every one in your own wallet.
  • Seed phrase stays in your browser. If you derive the xPub from a seed phrase, it happens locally on your device. The phrase is never sent to our server.
Signed webhooks and API keys

Your backend knows the event really came from us

Every webhook carries a Stripe-Signature header, an HMAC-SHA256 signature made with your webhook secret. Verify it with the Stripe SDK in a few lines.

  • Authenticity: the event was sent by Zyrox, not an attacker
  • Integrity: the data wasn't changed on the way
  • Replay protection: timestamps stop old events from being replayed
  • API keys are per merchant, sent as a Bearer token and rotatable from the dashboard
// Node.js: reject anything that isn't signed by Zyrox
app.post('/webhook', express.raw({ type: 'application/json' }), (req, res) => {
  try {
    const event = stripe.webhooks.constructEvent(
      req.body, req.headers['stripe-signature'], WEBHOOK_SECRET
    );
    handleEvent(event);
    res.json({ received: true });
  } catch (err) {
    res.status(400).send('Invalid signature');
  }
});
Detection and data

How payments are tracked and what we keep

⚡

Real-time detection

Separate indexers for Ethereum, Bitcoin, Tron, Arbitrum, Base and Optimism fetch new blocks every few seconds.

✅

Confirmations first

A payment counts as complete only after the required number of confirmations for its network. No instant approvals, no double spends.

🔒

Minimal data

HTTPS with TLS 1.2+ everywhere, passwords hashed with bcrypt, and only the data needed to match payments to invoices.

Trust checklist

Don't take our word for it

Four checks any merchant can run before going live. None of them needs our help.

Questions about security? Write to support@zyrox.io.

  1. Match the addresses. Derive addresses from your xPub with any offline BIP-44 tool and confirm they match the ones Zyrox shows.
  2. Look up the transactions. Open each payment's txid in Etherscan, Tronscan or Blockchain.com and see it arrive in your wallet.
  3. Start small. Run the full flow on testnet or with a small mainnet amount first.
  4. Verify every webhook. Check the signature in your backend and drop anything unsigned.

Keep full control of your revenue

Free until the end of 2026, then 0.5% of successful payments. Your keys, your wallet, your money.