For a business, “now accepting cryptocurrency” means customers can use specified digital assets through a defined payment process. Before announcing it, decide what assets and networks are supported, who handles payment monitoring and settlement, what happens to the funds, and which legal, tax, security, and recovery requirements apply to the business’s actual locations and operating model. The announcement itself does not establish those details.
What “now accepting cryptocurrency” means for a business
Acceptance is an operational arrangement, not just a statement that a business is open to crypto payments. A business needs a process for requesting payment, recognizing its status, recording the transaction, and deciding what happens to the funds afterward. Those functions may be divided among the business and service providers, so identify responsibility for each one rather than assuming that “acceptance” describes a single standard setup.
Receiving a payment and retaining it in cryptocurrency are separate choices. A business may need to decide whether funds remain in the received asset or are converted, and who is responsible for that decision. The relevant settlement arrangement should be clear: payment and settlement infrastructure needs to manage liquid resources sufficient to meet settlement obligations under normal and stressed conditions. This is a general operational principle, not a claim about a particular provider or crypto payment product. source
The phrase also does not define which assets, networks, customer locations, fees, or terms are supported. Those are arrangement-specific details. Confirm them before making any customer-facing statement, and communicate only capabilities the business has verified.
Map the payment flow before making the announcement
Start by tracing the customer and funds through the intended payment process. Determine who creates the payment instructions, how the customer receives them, and which party monitors whether payment arrives. Then identify how the business recognizes the relevant payment status and records it internally. These are business process questions; the particular tools or providers used to answer them are outside this article’s scope.
Next, define what counts as a completed payment for the business’s purposes. Specify how staff will handle a payment that appears incomplete, delayed, duplicated, or inconsistent with the requested amount. Assign an owner for investigating exceptions and for reconciling the business’s records with the payment information it receives. Without an agreed process, staff may not know whether to fulfill an order, wait, or investigate.
Finally, document what happens after the business treats a payment as settled. Decide whether the business retains the asset or converts it, who authorizes that action, and how the resulting amount is recorded. End-to-end financial asset arrangements can involve platform-based intermediation across multiple parts of an asset’s life cycle; responsibility and controls therefore need to be understood across the process, not only at the point where a customer pays. source
Set boundaries for assets, networks, and customer payments
Write down the intended scope before publishing an acceptance notice. Specify the assets and networks the business has confirmed it can handle, the locations where customers can use the option, and any relevant payment terms. Do not imply broader coverage than the underlying arrangement supports. Supported assets, networks, customer locations, and service availability require current confirmation for the specific business and payment flow; the available evidence here does not establish any particular coverage.
Set procedures for payment exceptions. Decide how the business will investigate incorrect, incomplete, duplicate, or delayed payments, who may approve a resolution, and how the customer will be informed. Define the business’s approach to refunds and explain any conditions clearly before a customer pays. Do not imply that a payment can be reversed or recovered unless the business has verified that capability and its limits for the arrangement in question.
Also determine how prices and costs will be shown. Confirm the actual fees and conversion terms that apply, then present customer-facing amounts and conditions clearly. Fees cannot be generalized from the fact that a business accepts cryptocurrency; they require current, arrangement-specific documentation. If the business cannot confirm a term, it should not promise it in an announcement.
Assess operational, security, and recovery risks
Assign named responsibility for monitoring incoming payments, reconciling records, managing access, and escalating incidents. Clarify which tasks sit with the business and which sit with another party. The word “provider” does not by itself answer who controls assets, who can authorize actions, or what happens when service is unavailable; verify those arrangements directly.
Assess custody and key management for the chosen model. Identify who can access or authorize movement of funds, how credentials and other access material are protected, and how access is reviewed. The appropriate controls depend on the actual arrangement, so do not describe a service as secure based on a generic label or an unsupported claim. Require relevant documentation about the controls and incident procedures that apply to the business.
Document recovery and continuity procedures before launch. Specify how the business will respond to lost access, service disruption, delayed payment information, and payment disputes. Record the limits of any recovery process rather than promising that funds or access can always be restored. The available evidence does not establish recovery capabilities for a particular service or arrangement, so these must be independently verified.
Verify legal, tax, and compliance requirements locally
Requirements depend on the business’s jurisdictions, customer markets, and specific operating model. Do not treat the availability of a payment service as proof that the business may offer every related activity or has met its obligations. Obtain qualified advice for the relevant locations and payment flow; this explainer does not provide legal, tax, licensing, or compliance advice.
For tax and recordkeeping, ask an appropriately qualified adviser what the business must record and how payments should be treated in each relevant jurisdiction. The evidence here does not establish a tax rule or recordkeeping duty for any particular business. Avoid adopting a generic policy based on another company’s process or on an assumption that cryptocurrency payments receive one uniform treatment.
Assess whether any identity checks, sanctions controls, licensing, reporting, or other compliance measures apply. As one U.S.-specific example, FinCEN generally considers certain convertible virtual currency kiosk operators that facilitate transmission between an exchanger and a customer wallet, or operate as an exchanger, to be money services businesses under the Bank Secrecy Act and subject to applicable requirements. That finding is limited to the described kiosk model; it is not a classification of every merchant accepting crypto. source
Use a pre-announcement readiness checklist
Before announcing acceptance, confirm that the business has:
- Defined the assets, networks, customer locations, and payment terms it can actually support.
- Mapped who creates payment instructions, monitors status, handles exceptions, reconciles records, and decides what happens to received funds.
- Verified current fees, conversion terms, refund conditions, and availability for the specific arrangement.
- Assigned responsibility for access control, security, incident response, and documented recovery limits.
- Obtained appropriate jurisdiction-specific advice on legal, tax, recordkeeping, licensing, and compliance questions.
- Prepared customer-facing language that describes only confirmed capabilities and terms.
If any item remains unresolved, narrow the announcement or delay it until the business can verify the relevant detail. “Now accepting cryptocurrency” is meaningful only when customers and staff can rely on a defined payment process and accurately stated terms.
Sources and references
- Tokenisation in the Context of Money and Other Assets — Committee on Payments and Market Infrastructures, Bank for International Settlements; retrieved 2026-10-19.
- FinCEN Notice on the Use of Convertible Virtual Currency Kiosks for Scam Payments and Other Illicit Activity — Financial Crimes Enforcement Network; retrieved 2026-10-18.
- Principles for Financial Market Infrastructures — Committee on Payments and Market Infrastructures; retrieved 2026-10-18.