How a contractor could accept crypto on larger invoices

Picture an independent contractor who invoices for jobs in the hundreds to low thousands of dollars. Payments are infrequent but large, often paid days after the work, and clean records matter for both taxes and disputes.

This example follows how such a business might add crypto as an invoice option. The tradeoffs differ sharply from a coffee shop: here on-chain settlement is fine, and the Lightning speed story matters far less. Figures are illustrative.

At a glance

---

How they take payment today

Most clients pay by bank transfer or check after the job. Transfers can take days, checks can bounce, and card fees on a large invoice are steep. Crypto's appeal here is final settlement within the hour, not speed at a counter.

---

The pain points that started the question

• Waiting days for a transfer or check to clear.
• Card fees that are painful on four-figure invoices.
• The occasional bounced or delayed payment.

---

Why crypto came up

A confirmed crypto payment is final and typically settles within the hour, with a network fee that is trivial relative to a large invoice. For big, infrequent payments, that is the real draw.

---

The initial concerns

• "The amounts are large, is this safe to receive?" Receiving is the safe part; the care is in storage.
• "What about my books?" Resolved by recording dollar value at receipt and settling to dollars.
• "What if a client sends the wrong amount?" Handled with a clear invoice and a known process.

---

How they researched it

The owner read the Lightning versus on-chain comparison and concluded on-chain was perfectly fine for invoices, reviewed the taxes and bookkeeping topic for record-keeping, and read the wrong-amount article to have a process ready.

---

The decisions they landed on

• Method: on-chain Bitcoin, since speed per second is not the point.
• Custody: a processor that converts to dollars and produces records.
• Checkout: a payment link or QR embedded in each invoice.
• Terms: the invoice states the dollar amount and that crypto is settled at receipt.

---

The implementation, step by step

1. Chose an invoice-friendly processor with dollar settlement and clean reports.
2. Added a crypto payment option to the standard invoice template.
3. Wrote a one-line policy: amounts are in dollars, settled at the confirmed rate.
4. Tested with a small invoice before offering it on a large job.

---

Equipment and costs

No new hardware. The cost was the processor's conversion fee, which on a large invoice compared favorably with card fees. On-chain network fees were minor relative to the amounts. Illustrative and service-dependent.

---

Lessons worth keeping

• For big invoices, final settlement in an hour beats a multi-day wait.
• Recording the dollar value at receipt kept the books clean.
• Stating terms on the invoice prevented amount confusion.

---

Common misconceptions and pitfalls

• Misconception: contractors need Lightning. On-chain is fine for invoiced work.
• Pitfall: leaving large balances in a hot wallet. Move savings to safer storage.
• Pitfall: vague invoice terms about which amount governs.

---

Recommended next steps for a similar business

1. Take the readiness quiz with your invoice sizes in mind.
2. Read Lightning vs. on-chain to confirm on-chain suits invoices.
3. Review the taxes and bookkeeping topic before you start.
4. Compare invoice-friendly services in the Payment Solutions Center.

---

The CryptoLic resources used in this example

• Merchant Readiness Quiz
• Lightning vs. on-chain Bitcoin
• Crypto taxes and bookkeeping
• Customer sent the wrong amount
• Payment Solutions Center