Five years ago, "accept Bitcoin Lightning" meant running your own node, watching channel liquidity, and explaining to your CFO why a 30-second outage cost you a $4,000 invoice. Today the operational story is different — but the question most service businesses ask is still the same: why bother?

The honest answer for most agencies, advisory firms, and SaaS companies isn't ideological. It's practical. Lightning solves three concrete pain points your billing stack already has.

1. Cross-border settlement without correspondent banking

If you invoice clients in Singapore, Lagos, and São Paulo, you already know the routine: 3-5 business day SWIFT, fees taken out at every hop, a wire that arrives as $4,847.32 on a $5,000 invoice. Lightning settles in seconds for fractions of a cent, and it doesn't care about your client's local banking infrastructure. For service businesses with international clients, that's not "alternative payment" — it's a faster wire.

2. Recurring micro-payments at SaaS scale

Card processing has a fixed-fee floor. A $0.30 fixed component plus 2.9% means a $5/month subscription bleeds 8% to fees. ACH is cheaper but slower and harder to internationalize. Lightning has neither of these problems — fees are a fraction of a percent of the transaction value, with no fixed floor — which makes per-seat or per-call pricing models that don't pencil on cards work on Lightning.

3. Subscription economics that match revenue

If you're a Bitcoin-native business — your treasury holds BTC, you pay vendors in BTC, your team takes some compensation in BTC — accepting payment in BTC means your billing flow doesn't have a foreign-exchange round-trip baked into it. The dollar your customer sends you doesn't have to become BTC tomorrow at a worse price.

What it looks like in practice

The version that works for service businesses isn't "rip out Stripe, become a Bitcoin company." It's add Lightning as another method on the same invoice your client already gets.

The flow:

  1. You create one invoice. Same template, same line items, same total, same due date. The invoice tool offers Lightning, on-chain Bitcoin, ACH, and card.
  2. The client picks how to pay. Most pay how they always pay — card or ACH. The clients who would pay in BTC if you let them, do.
  3. Funds settle to where they belong. Card / ACH to your bank account, Lightning / on-chain to your treasury wallet. Both flow into the same accounting view.

The mental shift is realizing this isn't an either/or. You don't pick "Bitcoin business" vs. "fiat business." You add a payment rail and let your clients self-select.

What you don't have to do

  • Run your own Lightning node. Custodial Lightning APIs handle channel management, liquidity, and routing. Self-custodial Lightning is great if you have the operational appetite — but it's not the cost of entry anymore.
  • Convert BTC to USD on receipt. If you want USD, the tool can convert. If you want to hold BTC as treasury, it doesn't have to. The decision is per-payment, configured once.
  • Renegotiate with clients. Most clients don't care which rails are on the back of an invoice. They click "Pay" and pick their card. The Lightning option exists for the clients who want it.

What to watch out for

Volatility on receivables

If your invoice is in USD and the client pays in BTC, the BTC amount is calculated at invoice creation. Between creation and payment, BTC can move 2-5% — which sometimes works for you, sometimes against. Most invoicing tools refresh the BTC amount on the payment page, so the client always pays the right USD value at the moment of payment.

Refunds

Lightning refunds are operationally different from card refunds. They're sender-initiated returns, not chargebacks. For service businesses with low refund rates this is fine. For e-commerce with consumer refunds, factor it in.

Tax and accounting

BTC payments received are still revenue, recognized at the USD value at the time of payment. Cost basis on the BTC starts there. FIFO cost basis applies the same way it does to BTC you bought.

The right question isn't "should we accept Bitcoin?" It's "would offering one more rail to the clients who want it cost us anything?" And mostly the answer is no.

Where to start

If you want to try Lightning without disrupting your existing flow:

  • Pick one client who has asked. Send them an invoice with Lightning enabled alongside their normal method.
  • See what the operational footprint actually feels like — settlement timing, accounting flow, treasury arrival.
  • If it feels normal (it will), enable it on every invoice and move on.

Most service businesses that adopt Lightning describe the experience the same way: "It just shows up in the treasury. We didn't do anything different." Which is the point.

Flash supports Lightning, on-chain Bitcoin, ACH, and card on every invoice — with payments flowing into your treasury automatically. See how Payments works or start free.