“We accept crypto” tells customers that a business says it can receive some form of cryptocurrency payment. The phrase alone does not identify the supported asset, payment route, locations, fees, settlement currency or timing, or refund terms. Before using it, a business should verify its actual arrangements and describe only the payment options and conditions it can confirm.

What “we accept crypto” can mean

The statement can refer to different payment arrangements. In a direct payment, a customer sends crypto to a business-controlled destination. In another arrangement, an intermediary or service provider may take part in handling the transaction or providing the business with access to funds. These are distinctions a business must check in its own setup; the phrase itself does not tell customers which route applies.

A payment route may involve more than one party. For example, a U.S. convertible virtual currency kiosk operator may fulfill transactions by connecting to a separate exchanger or by drawing on crypto it holds itself, while maintaining sufficient crypto and cash balances. That is one documented kiosk operating model, not a description of all crypto-payment arrangements or a feature that every business offers.

The phrase also leaves the asset and network unspecified. A business may support some assets but not others, even where names or symbols look familiar. On Ethereum-compatible systems, the ERC-20 standard defines a common interface for token balances, direct transfers, and approvals that let another address spend up to an authorized amount. That technical interface does not establish a token’s backing, issuance policy, market value, compliance, or code safety—and it does not show that a merchant accepts the token.

Acceptance should not be confused with settlement currency or timing. A customer may be told that a business accepts crypto without being told whether the business receives the same asset, whether any conversion occurs, or when the business considers the payment complete. Those facts depend on the specific arrangement and its documented terms. Do not imply that a customer’s payment is settled in a particular currency or at a particular time unless the business has verified that detail.

Details customers need before they pay

A useful statement names the assets the business accepts and, where relevant, the network and token representation. It should also identify where the payment option is available and any circumstances that affect its use. The information should reflect the business’s current arrangement rather than an assumption that support for one asset or network extends to others.

Customers need to understand the amount they are expected to pay and how the business communicates whether the payment meets its terms. The business should verify whether the displayed amount is fixed, estimated, or subject to a documented time limit before describing it. The evidence available for this article does not establish a universal quote period, confirmation threshold, or settlement time, so none should be presented as a standard feature.

Fees also require care. Do not say that a payment is free, that the customer pays a particular charge, or that the business receives a particular amount unless current terms for that arrangement support the statement. Crypto-payment fees can depend on the transaction and network. For Bitcoin on-chain transactions, the fee can depend on transaction size and demand for block space rather than simply the amount transferred; that Bitcoin-specific point should not be generalized to other networks or intermediary charges.

Refunds and cancellations are another part of the customer-facing picture. Do not suggest that a crypto payment can always be reversed, refunded in the original asset, or returned on a particular schedule without verified terms for the specific arrangement. Where the business’s terms distinguish between circumstances, customers should be directed to those terms before paying. This explainer does not establish a universal refund policy.

A customer may also need to know which party to contact with a question about a payment. The phrase “we accept crypto” does not identify who handles customer support, what records are available, or how the business reconciles payments. Those are operational details for the business to verify; they should not be represented as service features without evidence.

Check what the business actually supports

Before publishing an acceptance claim, the responsible team should compare the proposed wording with current business and provider documentation. A practical review can ask:

  • Which assets, networks, and token representations are actually supported?
  • What payment route does the customer use, and which parties take part?
  • Where and under what circumstances is that route available?
  • What amount is presented, and what documented condition marks the payment as meeting the business’s terms?
  • What do current terms say about fees, conversion, cancellations, and refunds?
  • Which party handles customer questions, and how are payment records and reconciliation handled internally?

The checklist is a verification exercise, not a claim that any particular feature exists. The evidence here does not verify the payment options, operating locations, terms, or recordkeeping of any specific business. Confirm those details with the responsible business team and the relevant provider before making them public.

Keep the scope of the statement no broader than the verification. If documentation confirms support only for selected assets or circumstances, say that rather than implying that all crypto is accepted everywhere. If the route or terms are subject to change, avoid language that presents them as permanent or universal.

A business’s acceptance statement does not establish that crypto payments are legally available in every jurisdiction, or that the business has a particular regulatory status. This article makes no jurisdiction-specific legal or tax conclusion. A business should use current, authoritative sources relevant to its location or consult a qualified professional before making claims about legal availability, tax treatment, or compliance.

Do not turn a general payment description into an assurance about safeguards. Security and recovery arrangements depend on the particular setup. The evidence here does not establish that any business’s funds are protected, that a payment can be reversed, or that an account or transaction can be recovered. Such claims require documentation specific to the relevant arrangement.

Likewise, avoid fee or yield claims unless current evidence supports them for the exact payment setup. The available evidence does not establish payment costs, earnings, or other financial terms for any particular business. If a public statement cannot be substantiated, omit it rather than implying a guarantee.

Write a precise customer-facing statement

A precise statement names only the payment methods, assets, and locations the business has confirmed. For example, a business could state that it accepts a named asset through a specified route in confirmed locations, then direct customers to current terms for the amount due, transaction conditions, and refund policy. This is a wording pattern—not a claim that a particular business supports those details.

If the network, payment condition, or refund term is not confirmed, do not imply otherwise. State what the business has verified and direct customers to current terms for details that vary by transaction. Recheck the wording when the business’s arrangement or provider documentation changes.

The goal is not to make “we accept crypto” sound broader. It is to make the statement specific enough that customers can understand what payment option is available, what they still need to check, and what the claim does not promise.

Sources and references