A freelance designer in Europe receives invoices in fiat currency but needs to hold some income in Bitcoin for portfolio diversification. A podcast producer in Southeast Asia wants to accept listener donations in Monero without routing every contribution through a centralized exchange. A small e-commerce business in North America requires a Bitcoin wallet that handles customer refunds efficiently while maintaining clean transaction records. Each faces the same practical problem: they need a reliable, privacy-respecting way to receive, store, and manage cryptocurrency without surrendering control of their funds to a custodian or paying excessive fees for basic operations.

Most merchants and freelancers approaching cryptocurrency for the first time encounter a crowded field of wallets, each claiming security or convenience as a primary virtue. The distinction that matters for business use is whether the wallet provides both: genuine control over private keys combined with tools that make receiving payments and managing multiple addresses straightforward enough to sustain consistently. Cake Wallet addresses that requirement through non-custodial architecture, built-in privacy features, and a merchant-friendly interface that reduces friction without hiding the underlying cryptocurrency mechanics. Understanding what the wallet does, how to configure it for receiving payments, and what security practices ensure reliable operation is essential before making it part of a business workflow.

Why merchants need a non-custodial bitcoin wallet and monero wallet

Custodial exchanges and payment processors offer simplicity: a user creates an account, receives a deposit address, and the platform manages the rest. But that convenience trades away essential control. The platform maintains private keys, enforces withdrawal limits, may require identity verification for every transaction above a threshold, retains records of every payment received, and can freeze or restrict access based on regulatory pressure or internal policy. For a merchant or freelancer, that dependency creates operational risk.

A non-custodial bitcoin wallet and monero wallet eliminate the intermediary layer. The user generates and stores private keys locally; no external service holds them. Payments received go directly to addresses controlled by the wallet owner. Withdrawals, transfers, and account decisions remain entirely local unless the user explicitly chooses to interact with an exchange. This separation is particularly valuable for merchants whose business may involve customers in multiple jurisdictions or who prefer not to create permanent records of transaction amounts and timing with a third party.

Cake Wallet implements non-custodial architecture through open-source code available on GitHub. This transparency means technical users can audit the application, verify that no backdoors exist, and review how private keys are generated, stored, and used. For users without the expertise to read code, the open-source commitment at least provides a path to verification rather than asking them to trust closed-source claims about security. The wallet stores private keys locally on the user’s device, protected by the device’s encryption and any additional PIN or biometric lock the user enables.

For merchants receiving payments in Bitcoin or Monero, the non-custodial model also means that regulatory or compliance decisions remain within the merchant’s control. A frozen account, delayed withdrawal, or sudden policy change at an exchange cannot interrupt payment collection. The merchant owns the address and the funds; only technical loss, device compromise, or recovery phrase exposure poses a direct threat to asset security. That responsibility is substantial, but it also reflects the reality of accepting digital currency: control and liability are inseparable.

Downloading, installing, and initial configuration

The first step is obtaining a verified copy of the application. Cake Wallet is available for iOS, Android, and web platforms. Users should download directly from the official app store (Apple App Store or Google Play) or from the official website rather than relying on third-party mirrors or unofficial redistributors. A compromised installer or modified application can steal recovery phrases or redirect payments to an attacker’s address regardless of how strong the underlying cryptography is. The cake wallet download process should also be recorded: note the date, version number, and source location in case a future question arises about whether the installation was current when configured.

After installation, opening the application presents a choice: create a new wallet or import an existing seed phrase. For a merchant setting up for the first time, “create new” is the appropriate path. The wallet generates a recovery phrase (typically 24 words) that fully controls all assets in the wallet. This phrase must be written down by hand, stored offline, and protected from any photograph, cloud backup, or internet-connected device. The recovery phrase is the single point of failure; if an attacker obtains it, they can recreate the wallet on any device and transfer all funds. Conversely, if it is lost and the device breaks, the funds are permanently inaccessible. Many merchants treat this step too lightly, storing the phrase in a notes app or email. That is equivalent to printing the wallet’s master password and leaving it on a public desk.

The wallet then asks whether to enable additional security. Biometric login (fingerprint or face recognition) and a PIN code are available options. These do not encrypt the recovery phrase; they only gate access to the application on the current device. A compromised device, malware, or social engineering can still expose the phrase. However, they do raise the cost of casual access and prevent someone with momentary physical contact from immediately transferring funds. For a merchant who keeps the device on a desk in a shop or office, biometric lock is a practical addition to the baseline of device encryption.

Users should enable 2FA if available for the specific platform and version. The exact options vary by device type and application version, so reviewing the security section of the wallet after initial setup is important. Some users prefer to keep 2FA on a separate device rather than in a password manager on the same phone that holds the wallet, as a compromise between convenience and reducing the likelihood that one compromised device or account compromises both.

Setting up separate addresses for different payment contexts

A merchant receiving customer payments, referral income, and personal savings should not consolidate them into one address. This is true for both Bitcoin and Monero, though for different reasons. Bitcoin transactions are permanently recorded on a transparent ledger; using the same address for different payment sources creates a visible link between those sources and can reveal business volume or payment patterns to observers. Monero’s ring signatures and stealth addresses provide better privacy by default, but address reuse still reduces privacy by enabling an observer to associate multiple transactions with a single recipient.

Cake Wallet supports multiple accounts and subaddresses within a single wallet, controlled by the same recovery phrase. In Monero, subaddresses are a native feature: each is a separately derived address that can receive payments but is mathematically linked to the wallet’s main address. They are particularly useful for merchants because they allow separate payment streams without requiring multiple recovery phrases or separate wallet backups. A customer paying invoice #42 can receive a distinct subaddress; a referral partner can receive a different one; a personal savings fund can use another. All are recovered from the same phrase, but transaction monitoring and account segregation become much more feasible.

Bitcoin addresses in Cake Wallet follow a similar principle through HD (hierarchical deterministic) derivation. The wallet generates new addresses from a master seed, but unlike Monero subaddresses, each new Bitcoin address is a completely independent public key. This is standard behavior for most Bitcoin wallets, including those with privacy features like Silent Payments. A merchant should use a new address for each significant payment request. Many Bitcoin payment processors and invoicing tools integrate with wallet software to automate this: when an invoice is created, a fresh address is generated, and the wallet receives a notification when payment arrives. Cake Wallet supports this through hardware wallet integration and can also be used alongside an invoicing application through manual address management if the merchant prefers not to expose the wallet’s API.

Receiving payments and managing multiple cryptocurrencies

Once accounts are configured, receiving a payment involves generating an address and sharing it with the payer. For Bitcoin, the user taps “receive,” selects the Bitcoin account, and either copies the address or scans a QR code to the payer’s device. The address is unique to that transaction context; if the same customer pays again, a new address should be used. Cake Wallet displays the expected amount and can include a description, making it clear what each address is for.

For Monero, the process is similar but with an additional option: the user can generate a subaddress directly or use the primary address. Subaddresses are recommended for distinct payment sources. The subaddress is visually identical to the merchant’s perspective (it still begins with “8” for mainnet) but is cryptographically separate in the ledger. From the payer’s perspective, sending to a subaddress is identical to sending to any other Monero address; they do not need to understand or even know that it is a subaddress.

Payment notification depends on the device and network connection. Cake Wallet can synchronize in the background, meaning transactions may be detected automatically without the user opening the app. However, the speed of detection depends on whether the wallet is using its own node, a public node, or a proxy service. A user who needs real-time payment alerts should verify that synchronization is working reliably before relying on it in a business context. Testing with a small payment from another wallet is a sensible precaution. Once a payment is confirmed on the blockchain, it is final and cannot be reversed; the merchant owns it outright if they hold the private key, which they do with a non-custodial wallet.

Privacy tools for merchants who value discretion

Merchants in regulated industries or those dealing with large payments may need privacy beyond the wallet’s default behavior. Cake Wallet includes several tools that address different aspects of transaction privacy. For Bitcoin, Silent Payments allow a merchant to publish a single public code from which payers can deterministically generate unique addresses without any interaction from the merchant. This eliminates address reuse and reduces the visibility of payment patterns on the public ledger. PayJoin v2 changes the transaction structure so that the customer’s input and the merchant’s address are less obvious to chain analysis tools, further obscuring the payment relationship.

Coin control is another privacy feature available in Cake Wallet for Bitcoin and Litecoin. This allows the merchant to see and select which specific transaction outputs to spend when making a payment (a refund, a supplier payment, or a withdrawal). Without coin control, the wallet automatically selects outputs, and an observer analyzing the transaction can potentially infer the merchant’s decision-making logic or discover payments the merchant believed were unrelated. Coin control gives the merchant full visibility and choice; the trade-off is that it requires understanding UTXO (unspent transaction output) management, which is not intuitive for users unfamiliar with Bitcoin’s model.

For network-level privacy, Cake Wallet supports Tor on Android and can route connections through I2P on certain configurations. These options reduce the likelihood that an observer monitoring the network can see the merchant’s IP address or relate multiple transactions to a single user. They introduce latency and may make connections slower, but for a merchant who synchronizes the wallet periodically rather than in real time, the privacy benefit may outweigh the inconvenience. Using Tor or I2P is particularly valuable if the merchant is in a jurisdiction where cryptocurrency custody itself is scrutinized or if customers are sending payments from countries with restricted internet access.

Integrating cake wallet download with invoicing and accounting workflows

A merchant’s wallet is part of a larger business system: invoices must be generated, payments tracked, taxes recorded, and customer records maintained. Cake Wallet itself does not provide invoicing or accounting features; it is a wallet, not a business management platform. However, the wallet can integrate with external tools through address generation, transaction labels, and exported transaction history.

After a cake wallet download is installed and configured, the merchant can use the wallet’s address display feature to create invoices manually or import the addresses into an invoicing tool. Some merchants use a spreadsheet that pairs invoice numbers with Bitcoin or Monero addresses; others use dedicated cryptocurrency invoicing services that can generate addresses on demand. The wallet will display incoming transactions in its transaction history; this history can be exported for accounting purposes. Labels and notes can be added to transactions within the wallet, helping the merchant remember which payment was for which invoice or customer.

Tax compliance is a significant consideration. Many jurisdictions require merchants to track the fiat value of cryptocurrency received at the time of receipt, regardless of whether the crypto is converted immediately, held, or used directly to pay expenses. The merchant should record the received amount, the date, the customer identifier, and the equivalent fiat value on the day received. Cake Wallet displays transaction history and can export it; this record then becomes the basis for tax reporting. Working with an accountant familiar with cryptocurrency is advisable because the rules vary widely and change frequently.

Securing the wallet against common merchant mistakes

A merchant wallet faces different threats than a personal savings wallet. It may receive payments in rapid succession, potentially on a mobile device in a business environment where security is less controlled. The wallet must remain accessible enough to use daily while remaining secure enough to withstand loss or theft.

The most critical mistake is inadequate backup of the recovery phrase. A merchant should write the phrase on paper, store it in a physically secure location (such as a safe deposit box), and keep a second copy in a separate location. The phrase should never be typed into a computer, photographed with a smartphone, stored in cloud services, or shared with any third party. If the merchant is uncomfortable with physical backup, they should consider a hardware wallet (Ledger support is available in Cake Wallet) that offers additional isolation, though hardware wallets themselves require a recovery phrase and careful backup.

Device security is the second priority. The device on which the wallet is installed should be kept up to date with security patches, should not install applications from untrusted sources, and should use strong device-level passwords or biometric locks. If the device is shared with family or staff, the wallet should be protected with a PIN or biometric lock separate from the device’s main security. Importantly, a compromised device can expose the wallet through malware even if the recovery phrase is safely stored elsewhere; the malware may simply intercept payments or redirect them. Using a dedicated device for the wallet, if practicable, is a stronger security posture than using a primary phone for both personal and business purposes.

A third category is social engineering. A merchant who receives an email claiming to be from support, asking for recovery phrase confirmation, or requesting device access should treat it as fraud regardless of how official the message appears. Legitimate wallet providers never ask for recovery phrases, and Cake Wallet’s actual support does not operate through email links that request credentials. Merchants should verify support interactions through official channels: the GitHub issues page, official social media, or the official website.

Testing, monitoring, and ongoing maintenance

Before relying on a wallet for actual customer payments, a merchant should test it with small amounts. Create a test invoice, generate an address in Cake Wallet, send a payment from another wallet or exchange, and confirm that it arrives and is recognized by the application. Check that the address was correctly displayed, that the confirmation timing matches expectations, and that the transaction appears in the wallet’s history as expected. This test confirms that the setup is working before real money is at stake.

Ongoing monitoring involves checking synchronization regularly. Cake Wallet should update its balance and transaction history periodically; a merchant should verify that new payments appear within a reasonable timeframe (typically within minutes for Bitcoin, though confirmation can take longer during network congestion). If synchronization appears stuck, the merchant should check that the device has an internet connection, that the wallet is not in airplane mode, and that the configured node is operational. Switching to a different node may help if the primary node is unavailable.

Storage and spending decisions should be reviewed periodically. A merchant may decide to hold Bitcoin as a long-term asset, convert some Monero to fiat to cover operating expenses, or move a portion of received funds to a hardware wallet for additional security. These decisions should be intentional and documented, not ad hoc. If a merchant keeps a large balance in a mobile wallet, they should consider moving some to cold storage (a hardware wallet or paper backup) to reduce exposure to device loss or compromise. Balancing accessibility and security is an ongoing trade-off; the right answer depends on the merchant’s risk tolerance and how frequently they need to access the funds.