Chapter 16

How Do I Get Paid in Bitcoin?

Getting paid directly in bitcoin can avoid an exchange or payment processor, but it does not eliminate the counterparty: the payer still has to pay the agreed amount. Someone who already has bitcoin sends a slice of it to your wallet. Receiving directly into a self-custodial on-chain wallet does not require an exchange account; choosing a custodial wallet or payment processor adds that service and its requirements. The practical questions are which rail to use, how a price gets agreed on, how to verify receipt, and who controls the funds afterward.

Chapter 16 of 24

What "getting paid" actually is

Strip away the payroll software or the invoice email, and getting paid in bitcoin reduces to one thing: someone else builds a transaction that sends value to an address derived from a key you hold, and broadcasts it. Chapter 8 already covered what a key is and why owning one is the whole game; Chapter 9 covered what actually lands in your wallet when that transaction confirms — a new, wholly yours UTXO, not a line-item added to some balance a company keeps on your behalf. Nothing about receiving a payment requires you to have signed up for anything. The sender needs a wallet. You need a wallet. That's the entire participant list.

Compare that to the three previous chapters. An exchange (its own chapter) needs an account and identity verification before it will let you trade. A broker sets a price and takes the other side of your trade. A mining pool needs your hardware plugged in and hashing. Getting paid needs none of that — which is exactly why it's the odd one out on this list, and also why it's arguably the most fundamental way bitcoin moves: it's simply what a payment is, with every other acquisition method just a more elaborate version of the same broadcast-a-transaction mechanic.

Two rails, chosen by amount and frequency

Chapter 10 already laid out why Bitcoin has a second layer at all: on-chain fees track bytes and confirmation slots, not dollar value, which makes a $4 tip and a $40,000 invoice cost roughly the same to settle on-chain even though one is a thousand times larger. That arithmetic decides which rail makes sense for getting paid, not personal preference:

Small, frequent amounts (tips, per-task gig pay, a coffee): → Lightning — near-instant, fee measured in fractions of a cent Large or one-off amounts (a freelance invoice, a sold asset, a salary): → On-chain — slower and costlier per transaction, but no channel liquidity to manage, and settles directly to a UTXO you control with nothing routed through in between

This site's own tip jar is a live example of exactly this choice: the Lightning address sits next to the on-chain BTC address specifically so a $2 tip and a $200 tip can each use the rail suited to their size, not the same one by default.

The arithmetic of agreeing on a price

Almost nothing is priced in bitcoin natively — rent, invoices, hourly rates, and paychecks are denominated in a local currency, so getting paid "in bitcoin" almost always means agreeing on a fiat amount first and converting it to satoshis at the moment of payment. That conversion is simple multiplication once both sides agree on which price and which moment, but both of those are real decisions, not formalities: a price quoted when the invoice is sent can differ from the price when it's actually paid, especially if bitcoin's exchange rate is moving quickly at that moment — the mechanics of exactly why it moves the way it does are a later chapter's subject, not this one's.

Illustrative example, not a live quote: Invoice amount: $75.00 Illustrative BTC price: $60,000 BTC to send: $75 ÷ $60,000 per BTC = 0.00125 BTC Amount to send: 0.00125 BTC × 100,000,000 sats/BTC = 125,000 sats

Round only at the end. Rounding the intermediate rate to 1,667 sats per dollar would turn this $75 invoice into 125,025 sats — 25 sats more than the exact conversion. Keep the full precision until calculating the final amount; if it contains a fraction of a satoshi, agree on a whole-satoshi rounding rule for an on-chain payment. This example excludes network and processor fees: agree separately who pays those, and check the amount the recipient must actually receive.

In practice, most invoicing tools and wallets do this multiplication automatically and lock in a quote for a short window (commonly 10–15 minutes) so neither side is exposed to a price move mid-transaction — but someone still had to decide whose price feed to trust and how long that quote stays valid, which is a real, if usually invisible, piece of the arrangement.

Settlement: when is it actually paid?

On-chain, "paid" isn't instantaneous — it's the same confirmation arithmetic Chapter 4 covered for any transaction: one confirmation arrives with the next block (roughly ten minutes on average), and larger amounts commonly wait for several confirmations before being treated as final, since a single-confirmation transaction is still (rarely, and increasingly expensively) reversible by a deep chain reorganization. Over Lightning, successful payments are typically fast, but attempts can remain pending, be delayed or fail. Check the receiving wallet or invoice's actual paid status before treating a payment as received; elapsed time or a pending status is not proof of payment. Do not resend an uncertain payment while its outcome is unresolved. Ordinary Lightning payments have no per-payment on-chain confirmation wait, which is different from a guarantee of immediate success. Core Lightning's xpay documentation, for example, describes retries and possible delays; other wallets may use different status labels. The channel-liquidity tradeoffs in Chapter 10 still apply.

On-chain — one confirmation ≈ one block sent 1 conf, ~10 min 6 conf, ~60 min many services treat 1 confirmation as enough for small amounts, 6 as final for larger ones Lightning — no per-payment on-chain confirmation wait check paid status Typically fast; pending, delayed or failed attempts are possible

Same payment event, two different settlement shapes: on-chain finality accumulates block by block over roughly an hour; successful Lightning payments are typically fast, but a pending attempt is not proof of receipt. Check the actual paid status.

Getting paid at business scale

An individual accepting an occasional tip or invoice just needs a wallet address. A business accepting bitcoin regularly usually adds a payment processor in between — a service that generates an invoice, watches for the incoming payment, and optionally auto-converts it to fiat immediately so the merchant never holds bitcoin's price exposure at all. Processors built specifically around Bitcoin and Lightning (OpenNode is one current example) and multi-coin processors that also support Bitcoin (BitPay is one) both exist in this space; this site doesn't currently have an affiliate relationship with either, and isn't recommending one over the other here — the point worth understanding is the auto-convert option itself, which turns "getting paid in bitcoin" into "getting paid in your local currency, with bitcoin as the payment rail" for anyone who wants the convenience of accepting it without taking on its volatility.

What happens the instant it lands

Whichever rail is used, the moment a payment confirms, the getting-paid question is already answered and a different one starts: the custody question. Chapter 12 covered the hot/cold, custodial/non-custodial choices that now apply to whatever just arrived — if the receiving address belongs to a non-custodial wallet, nobody but you can move that UTXO; if it belongs to a custodial service (an exchange account, a custodial Lightning wallet like this site's own tip jar, honestly disclosed as exactly that in Chapter 10), the received funds are subject to Chapter 8's whole warning about what "owning" bitcoin at a company really means. Getting paid is a single, complete event. What you do with it afterward is every other chapter in this book.

A direct payment can remove an intermediary, not the payer. Agree on the amount, verify receipt, and know who controls the receiving wallet.