Accepting cryptocurrency can widen payment options, but a small business needs more than a wallet address. This checklist explains how to choose between direct wallet payments and a payment processor, set up Bitcoin or stablecoin invoicing, manage settlement and refunds, confirm transactions, protect funds, and keep records that support accounting and tax work.
Overview
Crypto payments are not one uniform method. A merchant can receive an asset directly into a business-controlled wallet, use a processor that creates invoices and monitors transactions, or combine both approaches. The right choice depends on the business’s tolerance for price movement, technical work, custody responsibilities, refund complexity, and local compliance requirements.
Start by defining what “accepting crypto” means for your business. You may want to:
- Accept Bitcoin or another asset and hold it for a period.
- Accept a stablecoin while limiting exposure to market-price changes.
- Let a processor receive the customer’s crypto and settle the merchant in local currency.
- Use crypto only for selected products, locations, or business-to-business invoices.
These choices affect fees, settlement timing, customer support, accounting records, and the risk of sending funds on the wrong network. Before launch, check the rules that apply where the business operates, including registration, consumer protection, invoicing, tax, anti-money-laundering, and payment-services requirements. Requirements vary by jurisdiction and can change. The crypto regulation research guide can help organize that review, but it is not a substitute for advice from a qualified local professional.
| Method | Best suited to | Key advantages | Key trade-offs |
|---|---|---|---|
| Direct wallet payment | A technically capable business willing to manage custody | Direct control of funds; no intermediary required | More responsibility for wallet security, confirmations, pricing, records, and refunds |
| Payment processor | A business seeking a managed checkout and support workflow | Invoices, payment detection, customer support, and possible conversion or settlement tools | Processing charges, account dependence, provider limits, and settlement terms |
| Stablecoin settlement | A business seeking a digital payment rail with less asset-price exposure | May simplify quoted prices and settlement planning | Network fees, issuer and platform risks, redemption limits, and regulatory considerations |
| Conversion to local currency | A business that does not want to hold crypto | Reduces exposure to market-price movement after payment | Conversion spreads, withdrawal timing, account reviews, and possible tax or accounting events |
Checklist by scenario
1. If you use a direct wallet
- Create a wallet used only for the business, not a personal wallet.
- Decide who can approve outgoing transactions and set a separation of duties for larger balances.
- Use a hardware wallet or another appropriate custody arrangement for funds that do not need to remain available for daily payments.
- Record the exact asset and network accepted. “Bitcoin,” a token on a smart-contract network, and a stablecoin issued on different networks are not interchangeable payment instructions.
- Display a fresh payment address or invoice for each sale where possible. Do not ask customers to rely on an address copied from an old message.
- Define the exchange-rate source and the time window during which an invoice remains valid.
- Set a confirmation policy. For low-value, low-risk transactions, a business may use a different process from large or unusual payments, but the policy should be written and consistently applied.
2. If you use a payment processor
- Verify the provider’s legal entity, supported countries, supported assets, supported networks, custody model, and account-closure or reserve policies.
- Review the complete fee schedule, including processing, conversion, withdrawal, network, chargeback-related, and foreign-exchange charges where applicable.
- Confirm whether the provider settles in crypto, local currency, or a choice of both, and identify the settlement schedule and minimum withdrawal amount.
- Ask how the provider handles underpayments, overpayments, late payments, duplicate payments, and payments sent on an unsupported network.
- Check what customer support can actually do when a payment is missing or a refund is requested.
- Enable strong authentication, restrict dashboard permissions, and set alerts for logins, withdrawals, API-key changes, and payout changes.
3. If you accept stablecoins
- Name the exact stablecoin and network in every invoice and checkout instruction.
- Confirm that the business and its provider can receive, hold, convert, and withdraw that specific asset.
- Do not assume that a stablecoin will always trade at its intended reference value or remain available on every platform.
- Evaluate issuer, custody, redemption, freezing, and depegging risks alongside ordinary wallet and network risks.
- Decide whether stablecoin receipts will be converted promptly or retained, and document the accounting treatment with professional advice.
4. For every payment and refund
- Create an invoice with the goods or services, local-currency price, accepted asset, network, quoted amount, expiration time, and refund terms.
- Give the customer one official payment instruction. Avoid changing wallet addresses through an informal chat or email.
- Check the transaction on the appropriate block explorer or provider dashboard. Match the asset, network, amount, destination, and transaction status.
- Mark the invoice as paid only under the business’s confirmation policy. A transaction broadcast to a network is not necessarily final.
- Save the invoice, transaction identifier, timestamp, exchange-rate evidence, fees, and settlement record.
- For refunds, verify the customer’s destination address through a trusted process and state who bears network costs. Test the refund workflow before launch.
What to double-check
Network compatibility: The same or similar asset name can exist on multiple networks. Sending funds to an address or network the recipient does not support may create a difficult or irreversible recovery problem. Put the network beside the asset name wherever customers and staff see payment instructions.
Pricing and volatility: Decide whether the customer’s price is fixed in local currency until an invoice expires or fixed in crypto units. A local-currency price with a short invoice window is often easier to reconcile, while holding an asset introduces market exposure. Record the rate source and the conversion time.
Settlement: “Paid” and “available for withdrawal” may be different events. Review confirmation requirements, processing holds, payout timing, minimums, and bank-transfer timing. Keep enough working capital outside the crypto system to cover ordinary expenses.
Accounting and taxes: Keep records of the sale’s local-currency value, the asset and quantity received, fees, date and time, transaction identifier, and any later conversion or disposal. The correct treatment depends on the jurisdiction and business structure. Ask an accountant how to handle sales tax or VAT, income, inventory, gains or losses, and processor statements.
Security: Protect seed phrases and private keys from screenshots, cloud notes, shared drives, and messaging apps. Use dedicated devices or accounts where practical, enable hardware-based authentication, limit staff permissions, and maintain an offline backup and recovery procedure. For broader wallet guidance, see this wallet security and backup checklist.
Scams and impersonation: Staff should never treat a customer’s screenshot, email receipt, or claimed transaction as proof of payment. Verify through the official wallet or processor interface. Be cautious of messages requesting a wallet-address change, urgent payout, seed phrase, remote access, or “verification” transfer. If a compromise occurs, follow an incident plan and consult the crypto scam response guide.
Common mistakes
- Accepting too many assets at launch: Start with the assets and networks the team can monitor and reconcile. More options increase operational complexity.
- Using a personal wallet: This mixes business and personal records and makes access control, tax reporting, and succession harder.
- Promising instant refunds: Onchain transfers may be irreversible, and a processor or bank conversion may add delay. Publish realistic terms.
- Ignoring small underpayments: Define a threshold and procedure. Staff should know whether to request the difference, refund the payment, or escalate it.
- Failing to test a complete sale: Run a low-value test from the customer view through confirmation, settlement, accounting entry, and refund.
- Assuming a processor removes all risk: A provider can simplify operations but does not eliminate account, custody, pricing, privacy, regulatory, or business-continuity risks.
- Changing tools without preserving records: Export transaction histories, invoices, payout reports, and fee data before closing or migrating an account.
When to revisit
Review the payment setup before each seasonal planning cycle and at least once during every quarter in which the business actively accepts crypto. Repeat the review whenever a provider changes its fees, supported assets, networks, settlement terms, custody model, or account policies; whenever the business adds a location, product line, employee, or payment channel; and after a failed, delayed, disputed, or misdirected payment.
Use this short audit:
- Confirm accepted assets, networks, invoice wording, exchange-rate rules, and confirmation thresholds.
- Recheck provider status, fees, payout timing, support contacts, and local legal or tax guidance.
- Review wallet access, authentication, backups, withdrawal limits, and staff permissions.
- Reconcile processor reports, wallet balances, bank settlements, fees, refunds, and accounting records.
- Run a controlled test payment and refund whenever the workflow or tools change.
- Record what changed, who approved it, and when the next review is due.
A small business does not need the most complicated crypto payment stack. It needs a clearly defined payment method, exact network instructions, reliable confirmation and refund procedures, disciplined records, and security controls that staff can follow under pressure.