Common merchant errors in Lightning Network payouts

Technical mismanagement creates friction

I find technical mismanagement creates the most friction for Lightning merchants. Merchants who run a Lightning cashier must ensure their service uses an idempotent settlement ledger to prevent the error of crediting a deposit multiple times if a node crashes during the payment process. They also make the mistake of treating the node as their primary ledger. This approach risks fund loss if the node fails. They should use a dedicated database to track balances. They lose funds.

Do not ignore inbound capacity.

A single production pilot through Voltage’s infrastructure processed 88.2 BTC across 237,000 payments. These payments averaged 1.86 seconds for end-to-end settlement. Routing fees stayed under $0.01 per transaction. However, merchants still fail when they ignore liquidity direction. They must size inbound and outbound capacity carefully. Active channel management is a requirement. Operators rebalance channels and monitor for force closes. Force closes lock funds for days or weeks. They also incur high on-chain fees during congested periods. Many node operators lose money due to force closes. The network holds 4,898 BTC in public capacity across 41,080 channels. Node counts fell from a 2022 peak of 20,700 to 17,438.

Routing and volatility risks

Payments fail.

Routing errors occur when no path provides enough liquidity. Invoices expire. Most BOLT11 invoices have a default lifespan of one hour. A user cannot pay an expired invoice. They must request a new one to settle the amount.

Merchants also fail when they hold invoices too long. This creates an expiry trap for the user.

You should check your channel rebalancing regularly to avoid these issues. Lightning requires both parties to remain online to detect and respond to malicious closures. If a counterparty uses an outdated state, the node must contest it within a window. This watchtower risk differs from on-chain Bitcoin.

Volatility creates additional headaches. Bitcoin price movements can destroy monthly profits for a merchant. In the United States, every Lightning payment is a taxable event.

Merchants also struggle with unsupported formats. If a user sends a BOLT12 invoice but the wallet lacks compatibility, the payment fails. Three implementations like Core Lightning, LDK, and Eclair support BOLT12 natively. LND still lacks native support. BOLT12 offers reusable, static payment identifiers. This replaces the one-time-use BOLT11 invoices.

Navigating the chargeback landscape

Merchants must prioritize dispute management to avoid losing revenue to fraud. First-party fraud accounts for 50% of all chargeback claims. Visa gives merchants 30 days to respond to a chargeback. Mastercard allows 45 days for representment. American Express provides only 20 days to respond to inquiries. Failure to meet these windows causes automatic forfeiture.

Visa applies time-based dispute fees. These fees increase as more days pass. Some Visa issues have a 75-day window. Mastercard cardholders have 120 days to file most chargebacks. American Express cardholders have 120 days to file. Discover cardholders also have 120 days to initiate chargebacks.

Effective defense requires compelling evidence. I recommend preparing documentation like delivery confirmations and CRM logs early. Do you have the capacity to handle manual investigations?