How to accept crypto payments: the step-by-step guide

Step 1: Decide processor vs. raw wallet

You can technically accept crypto by posting a wallet address. Don't. A raw address gives you no way to match payments to orders, no underpayment handling, no confirmation tracking, no customer receipt, and no notification to your systems. The moment you have more than one customer, you're doing forensic accounting on a blockchain explorer.

A crypto payment processor like Flint does what card gateways do for cards: generates a unique payment request per order, watches the chain, handles amount-locking and confirmations, and fires webhooks your store can act on. For any real business, this is the baseline — and unlike card processing, there's no underwriting to pass, which is why it works even for high-risk industries.

Step 2: Set up your account and products

On Flint: create a free account, add a product with a name and USD price, and you immediately have a hosted checkout link. No processing history, no bank letters, no site audit. If you sell through Shopify, WooCommerce, or a custom storefront, you can place the checkout link as a payment option, or integrate the API for a seamless flow.

Price in your fiat currency, always. The processor converts to the crypto amount at payment time and locks the rate for the checkout session — your product costs $49, not '0.00071 BTC', and the customer sees exactly how much crypto settles it.

Step 3: Choose which coins to accept

Practical answer: Bitcoin and Ethereum for reach, plus USDT and USDC because stablecoins remove volatility from your side of the trade. A dollar-pegged payment for a dollar-priced product means your books match your price sheet. Many merchants steer customers toward stablecoins by default and keep BTC/ETH as options — customer preference varies by industry and region, so offering three or four options costs nothing and converts best.

Step 4: Wire up notifications (the part that makes it real)

The difference between a hobby setup and a business is what happens after payment. Flint sends signed webhooks when a payment is detected and again when it confirms on-chain. Your backend verifies the signature and then does whatever fulfillment means for you: sends the download link, provisions the license, credits the account, triggers shipping. For no-code setups, the dashboard shows every order in real time, and email notifications cover low volume fine.

One crypto-specific concept to internalize: detection vs. confirmation. A transaction appears on the network in seconds ('detected') but is final after block confirmations (usually minutes). Ship digital goods on confirmation; showing customers a 'payment received, confirming…' state in between is standard and keeps support tickets away.

Step 5: Handle refunds and disputes — on your terms

Crypto payments are push transactions with no chargeback mechanism, which changes your operational posture: nobody can reverse a payment out of your balance, and refunds are actions you take deliberately, sending funds back to the customer. Publish a clear refund policy, collect a return address when you refund, and honor your policy consistently — the absence of forced reversals is a feature for you, not an excuse for bad service. For merchants coming from card processing where disputes cost the sale plus $15–$100 every time, this is usually the single biggest economic difference.

Step 6: Sort out treasury and accounting

Decide what you hold: stablecoin-heavy merchants can leave revenue dollar-denominated; if you accept BTC/ETH, decide how much price exposure you want and convert the rest on your own schedule. For accounting, each payment has a fiat value at receipt time — your processor's records give you the per-order price, reference, and timestamp your bookkeeper needs. Crypto revenue is taxable revenue like any other; treat the fiat value at receipt as the sale amount and keep the export handy.

Common mistakes to avoid

A few errors show up repeatedly with merchants new to crypto checkout:

• Pricing in crypto instead of fiat — your margins shouldn't move with the market; let the processor convert at payment time
• Fulfilling on detection instead of confirmation — wait for on-chain finality before shipping anything irreversible
• Skipping webhook signature verification — an unverified webhook endpoint will eventually get spoofed
• Treating crypto as all-or-nothing — running it alongside your existing rails captures the upside with zero downside
• Forgetting the refund policy — no chargebacks means your policy is the whole story; write it before launch

The whole thing, compressed

Sign up, create a product, share the checkout link, verify a webhook, ship on confirmation. A developer can integrate the API in a day; a non-technical seller can take an order within the hour. If you're in a category card processors make life hard for, start with the guide for your industry — CBD, forex, or gambling — and see the pricing plans for what it costs at your volume.