A business preparing to accept cryptocurrency should decide which assets and payment routes it will support, whether it intends to receive crypto or fiat proceeds, who will control funds, and how payments will be recorded and handled when exceptions occur. Treat these as separate operating decisions: acceptance does not by itself determine custody, conversion, settlement timing, or the business’s legal and accounting obligations.

What accepting crypto means for a business

A crypto payment is not one single business function. The customer’s payment, the handling of the resulting funds, and any later conversion or transfer can involve different parties and records. A signature can authorize a Bitcoin transaction, but that fact alone does not establish who controls the destination in human or organizational terms, nor does it answer what the merchant should do operationally. source

Separate four decisions before selecting a route:

  • Acceptance: Which digital assets, networks, and transaction types will the business recognize as eligible payment?
  • Settlement: What event or condition will count as the business having received payment for its own operations?
  • Custody: Who controls access to the funds, and who is allowed to move them?
  • Conversion: Will the business retain the received asset or seek fiat proceeds through a separate process?

These decisions are connected, but they are not interchangeable. For example, a centralized exchange may take custody of deposited funds and record trades through its internal order book, but that describes an exchange model—not a universal payment route or an assurance about a particular merchant’s settlement arrangements. source

The business should map the intended flow in plain language: what the customer sends, where it is expected to go, who can access it, and what evidence the business uses to recognize the payment. Do not assume that every provider, asset, or jurisdiction supports the same arrangement. Availability and operational terms must be checked for the specific route being considered; the available evidence here does not establish a current provider’s asset list, fees, settlement timetable, or geographic availability.

Choose what payment acceptance must accomplish

Start with the customer and transaction requirements, rather than with a particular tool. Record the customer groups the business serves, the payment situations it needs to support, and the assets and networks it is prepared to review. A symbol or asset name alone is not an adequate operating specification: the payment route must identify the intended asset and network, and the business needs a procedure for a payment that does not match its instructions.

Next, choose the desired proceeds. A business may intend to receive cryptocurrency, seek fiat proceeds, or consider either outcome. That choice affects who handles funds and which records the finance team needs. The evidence supplied for this article does not establish that any particular route automatically converts payments, how quickly funds become available, or which fees apply. Treat those as questions to verify in current provider documentation and agreements, not as assumptions in a business plan.

Also establish operational constraints. Decide which employees review incoming payments, who answers customer questions, and who can authorize an exception. Specify how the business will handle incomplete, mismatched, delayed, or disputed payment information. This is a policy-design task; it is not a website checkout integration procedure. Keep the implementation details, including callbacks and transaction-status code, for the separate technical planning stage.

Plan settlement, custody, and accounting

Settlement needs a written business definition. State what the business considers sufficient evidence that a payment obligation has been met, who can approve fulfillment, and how exceptions are escalated. Do not infer a universal confirmation threshold or finality rule from the fact that a transaction has been signed or submitted. The permitted evidence for this guide does not establish network-specific confirmation behavior or a universal settlement standard.

Then decide who controls access to received funds. If the business uses a third party, identify the custodian’s role and the business’s own access and approval rules. If funds are transferred to an exchange, note that the centralized-exchange model typically involves transferring funds and custody to the exchange before trading on its internal order book; custody arrangements and legal ownership vary by platform and jurisdiction. source A business should therefore verify the exact arrangement rather than treating “exchange account” as a complete custody description.

Document responsibilities for access, approvals, reconciliations, and recovery. Name the staff roles allowed to authorize movement of funds, the review process for unusual activity, and the route for reporting an incident. The allowed evidence does not establish that a specific wallet or custodian has adequate security, insurance, recovery controls, or protections. Those claims require current, product-specific evidence and internal review.

Accounting should be planned alongside custody, not added after launch. Define what transaction and settlement records finance needs, how records will be matched to customer orders, and who reviews discrepancies. Obtain qualified accounting advice for the business’s circumstances; this guide does not determine accounting treatment or tax consequences. Likewise, set refund and exception policies before accepting payments, while verifying how the chosen route supports them. The available evidence does not establish a universal refund capability or process.

Set customer, security, and compliance controls

Customer instructions should identify the approved asset and payment route clearly, explain what the business expects the customer to do, and say how to seek help if the payment does not appear as expected. Establish who handles support questions and how staff confirm that a payment has been associated with the right order. Avoid promising a particular completion time or reversal outcome unless current, applicable documentation supports that statement.

For security, assign accountable owners for payment access, review, and incident escalation. Before launch, ask the relevant provider for current documentation of its custody model, access controls, recovery process, incident handling, supported assets, and settlement conditions. Distinguish a documented control from a guarantee: the evidence authorized for this article does not support a claim that any route is risk-free or that funds can always be recovered.

Compliance must be assessed for the actual business, route, and location. Do not assume one jurisdiction’s rules apply everywhere, or that accepting a payment alone determines whether a particular regulatory obligation applies. The evidence available here does not support general conclusions about licensing, consumer rules, sanctions, anti-money-laundering duties, privacy, or recordkeeping requirements. Verify each applicable question with current authoritative sources and qualified advisers before launch.

If operating in California, one specific receipt requirement provides a concrete example of jurisdictional variation: California requirements effective January 1, 2024 call for a kiosk receipt to include fiat and digital-asset amounts, fees, and the U.S.-dollar spread between the customer price and the referenced licensed-exchange price. This is a California kiosk example, not a general rule for merchants or other jurisdictions. source

Build a readiness checklist before launch

Use a written go/no-go review. The business should be able to answer each of these questions and identify an owner for the decision:

  • Which assets and networks are approved, and how will staff identify an unsupported or mismatched payment?
  • What is the intended payment flow, and does the business want to receive crypto, fiat proceeds, or either?
  • What business-defined condition permits fulfillment, and who reviews exceptions?
  • Who controls funds, who may authorize transfers, and what access or recovery procedures have been documented?
  • Which customer instructions, support contacts, refund policies, and exception procedures are approved?
  • What records does finance need, how will transactions be reconciled, and who resolves discrepancies?
  • Have current route-specific documentation and terms been checked for supported assets, location, fees, settlement conditions, custody, and recovery?
  • Have legal, accounting, security, finance, and operations reviewers assessed the obligations and controls relevant to the business?

A payment and settlement system also needs sufficient liquid resources for its obligations under normal and stressed conditions. The Committee on Payments and Market Infrastructures states this principle for designated financial market infrastructures; it is an operational planning reference, not a claim that every crypto product is such an infrastructure. source

Proceed only when the business has documented its decisions, confirmed the applicable requirements with appropriate sources, and assigned owners for routine operations and exceptions. If material questions about funds control, settlement evidence, records, customer handling, or applicable obligations remain unresolved, pause implementation planning until they are addressed. This checklist is a readiness framework, not legal, tax, or investment advice.

Sources and references