Tuga has a spot on the patio where she sits upright, facing the gate, looking for all the world like she is receiving customers. Nothing is being sold. No customer has ever arrived. But the posture is impeccable, and if trade ever did come through that gate she would be ready.

A lot of "we accept bitcoin" signage is exactly that: a posture, adopted once, never used, quietly removed a year later.

It doesn't have to be. Accepting bitcoin properly is a small amount of work with real benefits — and a handful of traps that are worth knowing before you put the sticker on the door.

1. Why Bother

Be honest about the reasons, because two of them are good and one is oversold.

• No chargebacks. This is the strongest argument and nobody talks about it. Card payments can be reversed months later, and for digital goods and small businesses that fraud risk is real money. A confirmed bitcoin payment is final. Your refund policy becomes something you choose rather than something a payment processor imposes.
• Low fees, especially internationally. Card processing takes a percentage plus a fixed fee, and cross-border adds more. Lightning costs a fraction of a cent. On small-ticket or international sales, that difference is your margin.
• Customers you wouldn't otherwise get. Modest, and real — particularly for digital products sold worldwide, where the alternative for some buyers is no payment method that works at all.

What it is not: a way to attract lots of new local customers. Most people will keep paying by card. Set the expectation accordingly and you won't be disappointed.

2. How to Actually Take the Payment

Three levels, same as everything else:

• A Lightning Address and a QR code. For a market stall, a service, a digital product — genuinely enough. Print the QR, let the customer scan, confirm the payment landed on your phone. Zero infrastructure.
• BTCPay Server. Free, open source, self-hosted. Generates invoices, handles the price conversion, plugs into common shop platforms, and — crucially — no third party ever holds your money. If you already run a node, this is the natural choice.
• A payment processor that converts to fiat. Some businesses genuinely don't want to hold bitcoin at all. A processor takes the payment, converts instantly, and deposits currency in your bank. You pay a fee and take on a counterparty. Legitimate, and a reasonable choice for a shop with tight margins and an accountant with opinions.

For anything under a few tens of euros, use Lightning. On-chain fees can eat a small payment alive, and nobody wants to wait for confirmations at a counter.

3. Pricing and Volatility

The rule is simple: price in your own currency, convert at the moment of checkout.

Never list a price in bitcoin. The number goes stale, and you end up either losing money or explaining exchange rates to someone who just wants a coffee. Every serious tool does the conversion automatically and locks the rate for the few minutes an invoice is valid.

Then decide, in advance and in writing, what happens to the coins:

• Convert everything immediately. No price exposure. You are using bitcoin purely as a payment rail — which is a perfectly coherent position.
• Keep a fixed percentage. A common approach: convert most, keep a slice as savings. Decide the percentage once and don't renegotiate it monthly based on the chart.
• Keep it all. Only if your business can absorb the volatility, which most small businesses cannot.

The failure mode is having no policy and deciding each time. That's not a business decision, it's trading with your revenue.

4. Refunds, Because Nobody Plans Them

Bitcoin has no chargebacks, which means refunds are entirely your process. Write the policy before your first sale:

• Refund the currency amount, not the coin amount. If someone paid the equivalent of €50 and you refund €50 worth at today's rate, that's fair and defensible. Refunding the same number of sats can mean giving back twice the value — or half.
• Get the refund address from the customer in writing. You cannot simply reverse a payment to where it came from; that address may not be theirs to receive at.
• Say all of this on the sales page. A customer who reads the policy before paying won't argue about it afterwards.

5. The Boring Part: Records

This matters more than any of the above, and it's where casual acceptance goes wrong.

In most countries, receiving bitcoin as payment is income at the value on the day you received it, and later converting it is a separate disposal that may create a gain or a loss. Two events, both of which need a number attached.

So: log every sale with the date, the amount in your currency, the amount in sats, and the rate used. Your payment tool probably exports this — turn the export on from day one. Reconstructing a year of it later is a weekend you will resent, and you'll get it wrong.

Rules vary a great deal, and this is the one part of the process worth one paid conversation with an accountant in your own country. Once, at the start.

The Point

The posture on the patio is free and achieves nothing. What makes it real is the boring apparatus behind it — the invoice that converts correctly, the policy for refunds, the row in the spreadsheet.

Accepting bitcoin isn't a statement; it's a payment rail with unusually good properties for exactly the businesses that get treated worst by card processors. Set it up properly, price in your own currency, write the refund rule down, and keep the records from the first sale.

Face the gate by all means. Just make sure something happens when someone walks through it. 🐾⚡

Not financial, legal or tax advice — I feed a cat and write about Bitcoin, which qualifies me for none of those. Tax treatment of crypto received as business income varies enormously by country; talk to someone qualified where you actually trade.