SMTP Relay
Dedicated IP, managed warmup, FBL processing
When privacy on the payment rail itself matters. Ring signatures, stealth addresses, and RingCT mean nobody watching the blockchain can link the payment to you or to us. No third-party processor in the path.
Bitcoin is pseudonymous, not anonymous. Every transaction is visible on the public blockchain, with sender address, receiver address, amount, and timestamp. Chain-analysis firms like Chainalysis and Elliptic specialise in linking these public records to real-world identities through exchange KYC data, address clustering, and transaction-pattern analysis.
Monero solves this at the protocol level. Three cryptographic primitives work together. Ring signatures mix your transaction with ten decoys, so an outside observer cannot determine which input was the real sender. Stealth addresses generate a one-time receiving address for each transaction, so the receiver's public key never appears on the blockchain. RingCT (Ring Confidential Transactions) cryptographically hides the amount being transferred while still letting the network verify the math is consistent.
The result: a Monero transaction appears on the blockchain as a payment from an unknown source to an unknown destination of an unknown amount, with only the payment fee and timestamp public. Even with unlimited computational resources, the underlying parties cannot be derived from the on-chain data alone.
For an operator running email infrastructure, this matters when the payment rail itself is part of the threat model. If a regulator or investigator pulls subpoena records from a Bitcoin payment processor or exchange, they get a trail. With Monero, that trail doesn't exist on the chain side.
We run a Monero full node on dedicated hardware in our infrastructure. BTCPay Server (which also handles Bitcoin) has a Monero plugin that connects to our node and generates a unique subaddress for each invoice. Subaddresses let us reconcile payments to specific orders on our side without exposing a single static wallet address to the public.
The technical flow: you place an order, the invoice generates a subaddress derived from our wallet's master key. You see this subaddress in the invoice. Your wallet sends to that subaddress. Our Monero node detects the incoming payment to that specific subaddress (which only we can decrypt). Once detected with one confirmation, the invoice marks paid and provisioning begins.
No third party sits in this flow. There is no Monero equivalent of BitPay because Monero's design makes it hard to even build a custodial processor that competes with running your own node. We accept Monero because we already run the node, not because we contract with a service.
On the cold-storage side, Monero funds we receive go into an offline wallet on hardware never connected to the operational network. Wallet keys are managed under a strict access policy. Cold-to-hot rebalancing happens on a scheduled basis, again as an internal operation with no third-party custodian.
First, get Monero. The options are buy on an exchange (Kraken, Cake Wallet built-in DEX, peer marketplaces like LocalMonero or RetoSwap), atomic-swap from Bitcoin or Litecoin (which avoids exchange KYC entirely), or accept Monero in your own work. Each has tradeoffs on privacy and cost. For maximum privacy, atomic swaps or peer purchases give the strongest isolation from your fiat identity.
Pick a wallet. Cake Wallet runs on iOS, Android, and desktop. Feather Wallet is desktop-only with a strong privacy focus. Monerujo is Android-native. The official Monero GUI requires syncing the full blockchain (around 200 GB as of 2026) which is most private but takes time and disk.
Place your order on our site. Pick Monero as the payment method. The invoice shows a subaddress and the XMR amount, locked at the current conversion rate for fifteen minutes. Copy the subaddress to your wallet and send the exact amount.
Wait for confirmation. The invoice updates in real time as our Monero node sees the transaction propagate and confirm. At one confirmation the invoice marks paid. You can close the browser at this point; provisioning proceeds asynchronously.
For larger amounts where you want extra confidence, you can wait for ten confirmations (about twenty minutes total). At that point the payment is functionally irreversible. We do not require this for provisioning to start, but for our internal accounting it marks the payment as fully settled.
Dedicated IP, managed warmup, FBL processing
Iron-E3, E5, EPYC. Bare-metal, offshore
Tor hidden service, Monero-only billing, isolated infra