In this article
Setting up crypto payments means choosing between two fundamentally different arrangements: use a payment processor that handles the technical work for you, or manage payments directly from a wallet your business controls.
Both work. The right answer depends on your technical comfort level, your transaction volume, your accounting setup, and how much ongoing responsibility you want to take on. Neither option is obviously superior; they just ask different things of you.
The two paths, briefly
A payment processor is a third-party service that handles the technical side of accepting crypto: generating payment addresses, monitoring transactions, converting to dollars if you want, and integrating with your POS. You manage a business account with the processor. The processor manages the keys.
Self-custody means your business controls its own private keys. Payments go directly to your wallet: no intermediary holds the funds, no account to log into, no platform between you and your money. You're responsible for the wallet, the keys, and the security.
The line between them isn't always sharp. Some processors offer settlement options that give you more direct control; some "self-custody" setups rely on third-party infrastructure in ways that aren't obvious. But the core distinction holds: a processor trades some control for convenience, self-custody trades convenience for control.
Using a payment processor
Payment processors for merchants (services like OpenNode, Coinbase Commerce, Strike, or a self-hosted BTCPay Server) sit between your customer and your wallet. The processor generates a unique address for each transaction, monitors for incoming funds, and notifies you when payment is confirmed.
What you gain:
- Automatic fiat conversion: many processors convert crypto to dollars and settle to your bank account, so you never hold a volatile asset
- Clean transaction records and accounting exports
- POS integrations: many work directly with Square, Shopify, or WooCommerce
- Technical complexity handled for you: wallet management, network fees, and address formats are not your problem
- Invoicing, payment links, and checkout widgets available out of the box
What you give up or accept:
- A fee: processors typically charge between 0.5% and 1% per transaction, though some offer no-fee tiers
- Dependency: if the processor has an outage, so does your crypto payment option
- Account risk: your account can be suspended or frozen, the same as with a card processor
- Privacy: the processor sees every transaction your business makes
- Trust: you're relying on the platform to handle your funds correctly
For most small businesses getting started, a processor is the practical choice. It removes the technical barriers, produces clean records, and doesn't require you to learn how wallets work. The tradeoff is a small fee and a dependency on the platform, not unlike what you already accept with your card processor.
Self-custody
Self-custody puts your business wallet under your direct control. Payments go straight to your wallet the moment a transaction confirms. No platform holds them. No account to be suspended.
What you gain:
- No processor fees: you pay network fees to miners or validators, not a platform
- No single point of account failure: no one can freeze your access
- Direct control over your funds from the moment of payment
- Privacy from platforms that would otherwise track your transaction history
What you take on:
- Key management: you are responsible for securing your private keys. Lose the keys, lose the funds. There is no customer support line.
- Technical setup: generating addresses, managing UTXOs (for Bitcoin), understanding network fees
- Record-keeping: transaction records are on you, not auto-exported by a processor
- Conversion: if you want dollars, you sell the crypto yourself, which involves additional steps and tax events
- Backup and recovery: hardware wallets, seed phrases, and secure storage aren't optional extras; they're the entire job
Self-custody suits businesses where someone genuinely wants to learn the technical side, or where there's a specific reason to avoid a processor relationship. It rewards people who treat key management as a serious responsibility. Most merchants who've run into trouble with it underestimated that part.
Security comparison
Both approaches carry real security risks. They're just different risks.
With a processor, the main exposure is account compromise and platform risk. An attacker who gains access to your processor account can redirect or steal funds. If the processor is hacked or shuts down, your funds may be at risk depending on how the platform holds assets.
With self-custody, the main exposure is key loss and theft. Lose your seed phrase with a failed hardware wallet, and the funds are gone permanently. An attacker who gets your seed phrase cleans you out just as thoroughly. No recovery process exists.
Neither approach is inherently safer. A retailer with no technical background who self-custodies is probably at more risk than one using a reputable processor with two-factor authentication and a strong password. Flip it around: a merchant with a hardware wallet and disciplined key management is likely more secure than one who logs into a processor on a shared computer and never changes the password.
The security you get is proportional to how seriously you treat the requirements of whichever approach you've chosen. The Merchant Security Playbook goes into much more depth on both sides: wallet selection, hardware options, backup procedures, and a printable security routine for daily operations.
Compliance considerations
From a tax and accounting standpoint, both approaches create the same obligation. You've received income when a crypto payment is made, equal to the fair market value at the time of receipt.
Processors often make this easier in practice. They produce transaction reports with timestamps and amounts in both crypto and fiat, exactly what your accountant needs. Self-custody requires you to maintain those records yourself.
Processors that offer instant dollar conversion also simplify bookkeeping considerably. You received $X.XX of crypto income and immediately converted it to dollars. No capital asset sitting on your books, no conversion event to track later. Holding crypto introduces that additional complexity.
CryptoLic doesn't provide legal or tax advice. If you're starting to accept crypto payments, bring your accountant in early. The questions to bring them are covered in the LLC and Bitcoin article.
Which approach fits which business
No formula fits every situation, but the patterns are consistent enough to be useful.
A payment processor tends to fit:
- Businesses that want to get started without deep technical setup
- Owners who want automatic dollar conversion and accounting exports they can hand to a CPA
- POS environments where the processor integrates directly with existing hardware or software
- Higher transaction volumes where manually managing addresses doesn't scale
- Anyone who wants to accept crypto without making it a second job
Self-custody tends to fit:
- Businesses with a technically capable owner or team member who wants full control
- Specific situations where a processor relationship creates a problem: privacy concerns, unsupported asset types, or use cases processors don't serve
- Lower-volume situations where manual processes are manageable
- Businesses that want to hold crypto rather than convert on receipt
Many merchants start with a processor and move toward more direct arrangements once they've seen how the mechanics actually work in practice. Starting simple is almost always smarter than starting ambitious.
The Merchant's Guide includes a full chapter on this decision, the infrastructure matrix, walking through the real tradeoffs in detail and helping you identify which path fits your specific business setup.