Security & Trust
How Zyrox keeps your payments secure, why we never hold your funds, and how to verify everything independently.
Non-Custodial Architecture
Zyrox is non-custodial. This means:
- Payments go directly to addresses derived from your extended public key (xPub)
- We never have access to your private keys
- We cannot move, freeze, or withhold your funds
- You can independently verify every address and transaction on the blockchain
This is fundamentally different from custodial payment processors (like traditional payment gateways) where the processor holds funds before settling. With Zyrox, you have full control from the moment a payment is received.
Verify it yourself: Every payment address Zyrox generates can be independently verified against your xPub using any standard BIP-44 derivation tool or your own wallet software.
HD Wallet Address Generation
Zyrox generates a unique payment address for every invoice using Hierarchical Deterministic (HD) wallet derivation (BIP-32). This provides:
- No address reuse — Each invoice gets its own address, making it easy to track which payment belongs to which order and improving privacy.
- Deterministic generation — The same xPub always produces the same sequence of addresses. You can verify any address independently using your wallet software.
- Industry standard — BIP-32/44 is used by all major wallets: MetaMask, Ledger, Trezor, Trust Wallet, Exodus, and many others.
API Authentication
If you use the Stripe-compatible API integration, all requests are authenticated with an API secret key:
- API keys are merchant-specific — each merchant has its own key
- Keys are transmitted via the
Authorization: Bearer header (same as Stripe)
- You can rotate keys at any time from the dashboard
- All API requests use HTTPS (TLS 1.2+)
⚠️ Keep your API key secret. Do not expose it in frontend code, public repositories, or client-side applications. Use it only in server-side code.
Webhook Signature Verification
All webhook notifications include a Stripe-Signature header that you should verify to prevent fake webhook events:
// Node.js — verify webhook signature
const stripe = require('stripe')('YOUR_API_KEY');
app.post('/webhook', express.raw({type: 'application/json'}), (req, res) => {
const sig = req.headers['stripe-signature'];
try {
const event = stripe.webhooks.constructEvent(
req.body, sig, 'YOUR_WEBHOOK_SECRET'
);
// Event is verified — safe to process
handleEvent(event);
res.json({received: true});
} catch (err) {
// Signature verification failed — reject
res.status(400).send('Invalid signature');
}
});
The signature is computed using HMAC-SHA256 with your webhook signing secret. This ensures:
- Authenticity — the event was sent by Zyrox, not an attacker
- Integrity — the event data hasn't been tampered with in transit
- Replay protection — timestamps prevent old events from being replayed
Payment Detection & Confirmation
Zyrox runs dedicated worker processes that continuously monitor blockchain networks:
- Real-time indexing — Workers fetch new blocks every few seconds and index transactions to your payment addresses. Payment detection typically happens within seconds of the transaction appearing on the network.
- Confirmation tracking — Payments are confirmed after reaching the required number of blockchain confirmations, which varies by network. This protects against double-spend attacks.
- Multi-network support — Separate indexers for Ethereum, Bitcoin, Tron, and L2 networks (Arbitrum, Base, Optimism) ensure fast and reliable detection across all chains.
Data Security
- Encryption in transit — All communication uses HTTPS with TLS 1.2+. API endpoints, webhook deliveries, and the checkout page are all encrypted.
- Minimal data collection — Zyrox stores only what is necessary: invoice details, transaction IDs, and integration data. We do not store sensitive customer financial information.
- Password security — Account passwords are hashed with bcrypt. We never store plaintext passwords and cannot recover them.
Trust Verification Checklist
You don't have to take our word for it. Here's how to independently verify the security of your setup:
- Verify payment addresses — Derive addresses from your xPub using any BIP-44 tool (e.g., iancoleman.io/bip39 offline) and confirm they match what Zyrox generates.
- Check transactions on block explorers — Every payment has a transaction ID (txid) that you can look up on public block explorers like Etherscan, Blockchain.com, or Tronscan.
- Test with small amounts first — Use testnet networks (
test=true parameter) or small mainnet amounts to verify the full payment flow before going live.
- Verify webhook signatures — Always implement webhook signature verification in your backend. Never process unverified webhook events.
Have security concerns or questions? Contact us at [email protected].