Building a Monero Receiving Address System: XMRWallet’s Subaddress Strategy for Merchants

A merchant selling digital services or physical goods faces a recurring problem: customers need a way to send payment, but accepting payments at a single address creates a permanent, visible link between transactions on the Monero blockchain. Even though Monero’s ring signatures and stealth addresses obscure transaction amounts and sender identity, a merchant who publishes one address and receives multiple payments establishes a cluster that observers can recognize as belonging to the same entity. This recognition does not reveal who the merchant is, but it does reveal that one entity is receiving many payments, and blockchain analytics can use that pattern to estimate revenue, identify high-value transactions, and correlate activity across time.

Subaddresses solve this problem by allowing a single wallet to generate thousands of unique, independently managed receiving addresses that are not linked on the blockchain. Each subaddress receives payments that arrive at the same underlying private key, but the addresses themselves are derived through cryptographic separation that prevents an external observer from recognizing them as belonging to one entity. For a merchant using XMRWallet, this means accepting customer payments through distinct addresses without exposing the relationship between transactions or requiring multiple separate wallets. The mechanism is part of Monero’s protocol design, but the practical setup, management, and reconciliation of subaddresses requires deliberate planning to deliver the intended privacy benefit.

Why subaddresses matter more than a single address

The distinction between receiving XMR at one address versus many subaddresses is not merely cosmetic. When a merchant posts a single address on their website, accepts payments at it for months, and the blockchain records all transactions to that address in a permanent, queryable form, any observer can build a profile. They can estimate when the merchant receives large payments, how frequently customers make purchases, when revenue dips or spikes, and whether transaction sizes suggest particular business models. This metadata does not identify the merchant by name, but it creates a statistical fingerprint that can be correlated with business announcements, hiring activity, or other public signals.

Subaddresses prevent this correlation by splitting the transaction history across multiple addresses. From the blockchain’s perspective, each subaddress is independent. A customer paying to subaddress #1 in February and another paying to subaddress #2 in March have no obvious on-chain relationship. An observer who later discovers that both subaddresses belong to the same merchant still cannot use blockchain analysis to link the transactions automatically; they would need additional information from other sources. This separation improves transaction fungibility because each payment is treated as a distinct event rather than a member of a recognizable set.

For a merchant, the operational benefit is equally important. Instead of manually reconciling customer payments against a single address and trying to remember which payment came from which customer, the merchant can assign a unique subaddress to each customer, invoice, or product. When payment arrives at subaddress #42, the merchant’s system immediately knows it corresponds to customer order 1000042. The Monero blockchain records the transaction, the merchant’s wallet receives it, and the customer cannot later claim they paid to the wrong address or that their payment was not received. The subaddress itself is the receipt.

Setting up XMRWallet for subaddress-based receiving

The first step is to create or import a wallet using the official XMR wallet interface. A non-custodial setup means the user (the merchant) generates a recovery seed locally and maintains full control over the private key. The wallet does not send this information to external servers; it remains on the user’s device. During creation, a new recovery seed is displayed—a list of words that can restore the wallet later. This seed should be written down and stored securely offline; losing it means losing access to the funds if the device is lost or reset.

Once the wallet is created, the merchant can view the main address—the primary receiving address associated with this wallet. However, the merchant should not distribute this main address to customers. Instead, the merchant will generate subaddresses from it. Each subaddress is derived from the same private key but functions as an independent receiving address. The wallet interface allows the merchant to generate new subaddresses on demand; there is no practical limit to the number that can be created, and creating them does not require any additional setup or interaction with external services.

The second step is to link subaddresses to customer identities or orders in the merchant’s system. If the merchant runs an online store, a database can map subaddress #1 to customer Alice’s order for a digital book, subaddress #2 to customer Bob’s order for a consultation, and so on. When a customer receives an invoice, they are told to send payment to their assigned subaddress. The merchant’s wallet receives the payment to that subaddress, the wallet software automatically increments the balance associated with that subaddress, and the merchant’s database can query the wallet API or logs to confirm that payment has arrived.

This mapping does not require the merchant to run complex software. A spreadsheet with columns for subaddress number, customer name, order description, amount expected, and payment status is sufficient for a small operation. A small business can implement this using basic accounting tools. The important requirement is that the merchant maintain the mapping and not reuse subaddresses across different customers or purposes. Reusing a subaddress defeats the privacy benefit, because it re-establishes the visible link on the blockchain.

Understanding stealth addresses and privacy preservation

Monero’s stealth addresses are a core part of why subaddresses work as a privacy tool. When a customer sends XMR to a subaddress, the customer does not actually send it to the subaddress itself. Instead, the customer uses the subaddress to derive a one-time stealth address for that specific transaction. This stealth address appears on the blockchain, but it is unique to that one transaction. Even if an observer examines the blockchain and discovers ten stealth addresses that all belong to payments received by the same entity, they cannot prove this without access to the merchant’s view-only key.

The view-only key is a cryptographic component that allows viewing incoming transactions without the ability to spend them. A merchant can share a view-only key with an accountant, auditor, or bookkeeper, allowing them to see all incoming transactions without giving them the ability to withdraw funds. This is useful for verifying that payment has arrived without exposing the spending key. Because the view-only key is independent of the spending key (which controls actual fund access), this separation creates a useful transparency boundary.

Subaddresses add another layer to this scheme. Because each subaddress produces distinct stealth addresses, and the stealth addresses do not reveal their association to an external observer, the blockchain shows only opaque transactions to a group of addresses. Someone analyzing the blockchain can see that transactions are happening, but they cannot automatically link them or determine that they belong to the same entity without additional information. This is why a merchant using subaddresses gains privacy benefits that a merchant using a single address does not.

However, this privacy benefit depends on the merchant’s operational security. If the merchant receives payment to subaddress #7 and then immediately sends a large payment to a regulated exchange using that same wallet, an observer with visibility into the exchange can potentially correlate the subaddress with the merchant’s identity through the outgoing transaction. Similarly, if the merchant publicly announces “my subaddress #7 is for consulting work” in a forum post, the privacy benefit of the subaddress is negated by the public statement. Privacy in Monero is therefore a function of both the protocol’s design and the user’s behavior.

Reconciliation and accounting with subaddresses

A merchant accepting payments across multiple subaddresses must track which subaddresses have received payment and reconcile the amounts against expected invoices. XMRWallet provides transaction history that shows payments to each subaddress. The merchant’s system can poll this history or monitor incoming transactions using a script that queries the wallet’s JSON-RPC API, which is part of the official XMRWallet implementation.

The reconciliation workflow is straightforward: a customer is assigned subaddress #15, invoiced for 0.5 XMR, and the merchant’s system monitors for incoming transactions to that subaddress. When 0.5 XMR arrives, the wallet records it as a confirmed transaction after the blockchain reaches sufficient confirmation depth (typically 10 blocks for Monero). At that point, the merchant’s database is updated to mark the invoice as paid, and the customer’s service is activated or goods are shipped.

For larger merchants or those with high transaction volume, automated monitoring is more practical than manual checking. A webhook or polling script can query the wallet balance at regular intervals and alert the merchant when a payment is received. Some merchants use external Monero payment processors that abstract away these details, but a merchant using XMRWallet directly maintains full control and full responsibility for the reconciliation process. There are no refunds, reversals, or chargebacks on the Monero blockchain; once a transaction is confirmed, it is final. This immutability is a feature for preventing fraud, but it requires the merchant to be careful about address assignment and invoice amounts.

A critical operational requirement is to never reuse a subaddress. If a merchant assigns subaddress #20 to customer Alice for one transaction and then later assigns the same subaddress to customer Bob for another transaction, the two customers’ payments are visible on the blockchain as belonging to the same address. This destroys the privacy separation that subaddresses are designed to provide. Many merchants implement a policy of assigning incrementally increasing subaddress numbers to ensure that each subaddress is used exactly once, then archiving the mapping once the transaction is final.

Managing private keys and backup security

Because XMRWallet is non-custodial, the merchant’s private key is their responsibility. This is a fundamental difference from a centralized payment processor like PayPal or Stripe, where the processor holds the funds and the merchant relies on the processor’s security infrastructure. With XMRWallet, the merchant must ensure that the private key is secure, the device is protected, and the recovery seed is stored safely.

The recovery seed (also called the mnemonic seed or backup seed) is a sequence of words that can restore the wallet and all of its subaddresses if the device is lost, stolen, or fails. This seed is derived from the private key and contains all information necessary to reconstruct the wallet. A merchant should write down this seed on paper, store it in a secure location such as a safe or safety deposit box, and not store it on the internet or in cloud services. If a thief gains access to the recovery seed, they can restore the wallet on another device and steal all funds.

Device security is equally critical. If a merchant’s computer or phone is infected with malware, the malware could potentially read the wallet file, intercept the password, or transmit the private key to an attacker. Using a dedicated device for wallet management, keeping the operating system updated, running reputable antivirus software, and using a strong password to encrypt the wallet file are all standard security practices. For a merchant handling significant XMR volumes, a hardware wallet dedicated to signing transactions can provide additional isolation.

Backup and recovery procedures should be tested before an emergency occurs. A merchant should practice restoring a wallet from the recovery seed on a test device to ensure that the seed is correct, that the restoration process is understood, and that funds can be recovered if needed. A merchant who has never tested their backup and later loses access to their wallet may discover too late that the backup is incomplete or was stored incorrectly.

Scaling subaddresses for high-volume merchants

For a merchant processing hundreds or thousands of payments per day, manually managing subaddress assignment becomes impractical. At this scale, automation is necessary. A merchant can implement a system where each order automatically generates a unique subaddress and an invoice with that subaddress embedded. The customer scans a QR code or copies the subaddress and sends payment. The merchant’s system monitors for incoming transactions and automatically processes them when they arrive.

Many merchants integrate XMRWallet with payment infrastructure like Monero payment processors or custom webhook systems. The processor maintains a connection to a wallet node and monitors for transactions. When a payment arrives to an assigned subaddress, the processor’s API notifies the merchant’s e-commerce platform, which then activates the customer’s purchase or updates the order status. This automation reduces human error and allows the merchant to scale without proportionally increasing operational overhead.

However, automation also creates dependencies. If the merchant’s system crashes, the monitoring process stops and payments may not be detected until the system is restored. A merchant should implement monitoring redundancy—multiple systems checking for incoming transactions or alerts if confirmations fall below expected levels. The merchant should also maintain regular backups of the subaddress-to-order mapping database, because losing this mapping means losing the ability to reconcile which customer paid for which order.

For very high-volume merchants, maintaining a separate wallet node specifically for transaction monitoring can improve reliability and privacy. A full node allows the merchant to verify transactions independently rather than relying on external services. This is technically complex but provides maximum control and ensures that no third party can observe the merchant’s incoming transaction patterns.

Privacy considerations and operational limitations

Subaddresses provide excellent privacy against observers examining the Monero blockchain, but they do not provide complete anonymity in all contexts. If a merchant publishes a subaddress in an unencrypted email or on a website not using HTTPS, an attacker could theoretically intercept the address. If a merchant sends funds from a subaddress to a known regulated exchange, the exchange’s know-your-customer (KYC) procedures could create a link between the subaddress and the merchant’s identity. If a customer can see which other customers are using the same merchant (through community discussion, social media, or other channels) and learns which subaddresses were assigned to them, the customer could correlate transactions on the blockchain.

These limitations are not flaws in the subaddress mechanism itself but rather boundaries of what cryptography can accomplish. Subaddresses prevent automatic linkage on the blockchain; they do not prevent linkage through social intelligence, commercial investigation, or user behavior. A merchant should not treat subaddresses as a solution to regulatory compliance, tax evasion, or other legal obligations. Monero’s privacy features are designed to provide financial privacy against passive observers, not to enable illegal activity.

A merchant should also be aware that some exchanges and services may refuse to accept XMR or may implement restrictions on Monero transactions due to regulatory pressure. This is not a technical limitation of Monero or subaddresses but a business decision by institutions that choose to comply with certain jurisdictions’ requirements. A merchant should verify that their intended use of Monero (including accepting payments through subaddresses and later converting to other assets if needed) is legal in their jurisdiction before implementing the system.

Integrating subaddress systems with existing business processes

A merchant migrating to subaddress-based receiving should plan the transition carefully. If the merchant currently uses a single address, customers’ expectations and invoicing systems need to change. Invoices should include the specific subaddress for payment rather than a generic wallet address. If the merchant runs an online store, the checkout flow should display the assigned subaddress along with the expected amount and a QR code for easy scanning by mobile wallet users.

Training staff or customer support to explain the subaddress system is helpful but not always necessary. Most customers simply need to know the address to send payment to; they do not need to understand how subaddresses work. However, if a customer mistakenly pays to the wrong address, explaining that the wallet is non-custodial and that the merchant cannot reverse transactions is important to manage expectations. A clear refund policy—whether funds are refunded, how long refunds take, and under what circumstances refunds are possible—should be documented.

Accounting and tax reporting may be simplified or complicated by subaddresses depending on the merchant’s existing practices. If the merchant is already tracking incoming payments by customer or order, the mapping between subaddress and order becomes part of the transaction history. If the merchant needs to report total XMR received to a tax authority, summing the balance across all subaddresses provides the total. The merchant’s accountant may need to be educated about how Monero and subaddresses work, but the basic accounting principle—tracking inflows by source and outflows by use—remains unchanged.