What Lightning payments are and why you'd add them to your gateway

Lightning Network is a layer built on top of Bitcoin that lets you send and receive payments in seconds instead of minutes, with fees measured in fractions of a cent. If your payment gateway currently handles credit cards, bank transfers, or stablecoins, adding Lightning means customers can pay you in Bitcoin without waiting for blockchain confirmation or paying the full on-chain fee.

You add Lightning to a gateway when you want to reach customers who hold Bitcoin, reduce settlement costs on certain transactions, or offer faster international transfers. Lightning doesn't replace your existing payment methods—it runs alongside them. A customer sees Lightning as one option among several at checkout, the same way they see Visa or PayPal today.

The integration itself is technical: you need a Lightning node (software that connects to the network), a way to convert Lightning payments back to your local currency if you don't want to hold Bitcoin, and an API connection between your gateway and that node. Most payment processors now offer this as a pre-built integration, which means you don't build it from scratch.

Key Takeaways

  • Lightning payments settle in seconds with fees under one cent, making them useful for small transactions and international payments where traditional fees eat into margins.
  • You can integrate Lightning through a hosted node service (easiest, you pay a monthly fee) or run your own node (more control, more technical work).
  • Major payment processors including BTCPay Server, Stripe (in select regions), and Square Cash now offer Lightning as a built-in option, so you may not need to code anything yourself.
  • You'll need to decide whether to settle Lightning payments in Bitcoin or convert them to fiat currency immediately, which affects your accounting and currency risk.
  • Lightning works best for transactions under $500 and for customers who already hold Bitcoin; it's not a replacement for card payments but an addition to your payment menu.

Choosing between a hosted node and running your own

A hosted node means a third party runs the Lightning infrastructure for you. You connect to their API, they handle channel management and liquidity, and you pay a monthly fee (typically $10 to $100 depending on volume). Examples include Voltage, Alby, and Umbrel Cloud. This is the fastest path to accepting Lightning because you don't manage server hardware, don't worry about node uptime, and don't need to understand channel mechanics.

Running your own node means installing Lightning software (like LND, Core Lightning, or Eclair) on a server you control. You manage your own channels, decide how much Bitcoin to lock into the network, and keep all routing fees. This costs less per transaction but requires technical knowledge: you need to understand port forwarding, firewall rules, channel rebalancing, and what happens if your node goes offline. Most merchants start with a hosted node and move to self-hosted only if they're processing enough volume to justify the work.

If you're already running a Bitcoin node for other reasons (mining, validation, custody), adding a Lightning node to the same server is straightforward. If you're not, a hosted node saves weeks of setup and troubleshooting.

Integration paths through existing payment processors

BTCPay Server is open-source software you install on your own server. It includes a built-in Lightning node, connects to your e-commerce platform (Shopify, WooCommerce, Magento), and generates invoices that customers pay via Lightning. You own the node, the payments, and the Bitcoin—no middleman takes a cut. Setup takes a few hours if you're comfortable with server administration; hosting costs $10 to $50 per month depending on the provider you choose.

Stripe added Lightning support in 2023 for merchants in the US and Europe. If you already use Stripe, you enable Lightning in your dashboard, and it appears as a payment option at checkout. Stripe handles the node, channel management, and conversion to your settlement currency. You pay Stripe's standard processing fee (around 2.9% + $0.30 for card payments), and Lightning transactions are typically lower. This is the easiest path if you're already a Stripe customer, but you have less control over the technical details.

Square Cash (now Block) offers Lightning through their Cash App for Business product. Customers can pay invoices via Lightning, and you receive the funds in your Square account. Like Stripe, this is managed for you, but it's only available in certain regions and only if you're already using Square's invoicing or point-of-sale system.

Smaller processors like Coinbase Commerce and OpenNode also support Lightning but with varying levels of integration depth. Check whether your current processor already offers it before building a custom integration.

The technical steps to connect Lightning to your gateway

If you're using a processor that doesn't yet offer Lightning, or if you want to run your own node, the integration follows this sequence:

  1. Set up a Lightning node (hosted or self-hosted) and fund it with Bitcoin. This creates your connection to the Lightning Network.
  2. Generate an API key from your node or hosted service. This key lets your payment gateway communicate with the node.
  3. In your gateway's settings, add the Lightning node's connection details (the API endpoint and key). Most gateways have a section for "alternative payment methods" or "cryptocurrency" where you paste this information.
  4. Test the connection by creating a test invoice and paying it with a small amount of Bitcoin. This confirms the node is reachable and invoices are being created correctly.
  5. Configure your settlement: decide whether Lightning payments should convert to fiat currency immediately (through an exchange API) or stay in Bitcoin in your wallet.
  6. Set a transaction limit. Lightning works best for payments under $500; larger amounts may fail if channels don't have enough liquidity. Your gateway should let you set a maximum or show a warning to customers.
  7. Enable Lightning at checkout. Customers now see it as a payment option alongside cards and bank transfers.

If you're using BTCPay Server, steps 1–3 are built in and happen during installation. If you're using Stripe or Square, you skip all of these—you just toggle Lightning on in your dashboard.

Managing liquidity and channel capacity

Lightning works by locking Bitcoin into channels between two parties. When you receive a payment, the Bitcoin moves through channels to reach you. If no channel has enough capacity, the payment fails. This is the biggest operational difference from card payments, where capacity is unlimited.

When you first set up a node, you create channels by sending Bitcoin to other nodes on the network. If you receive $1,000 in Lightning payments but only have $500 in channel capacity, the next customer's $600 payment will fail. You then need to either open a new channel (which costs a small on-chain fee) or rebalance existing channels (moving Bitcoin around to free up space).

Hosted node services handle much of this automatically. Voltage and Alby, for example, monitor your channels and suggest rebalancing or new channels when needed. If you run your own node, you manage this manually or use tools like Rebalance or Loop (a service that moves Bitcoin between channels without manual intervention).

For most merchants, starting with $5,000 to $10,000 in channel capacity is enough. As volume grows, you increase it. If you're processing less than $500 per month in Lightning, you probably don't need to think about liquidity at all.

Converting Lightning payments to fiat currency or holding Bitcoin

When a customer pays you in Bitcoin via Lightning, you have two choices: keep the Bitcoin or convert it to your local currency immediately.

Keeping Bitcoin means you're exposed to price swings. If Bitcoin rises 10% after a customer pays you, your revenue in local currency terms has risen too. If it falls 10%, your revenue has fallen. For merchants who believe in Bitcoin's long-term value, this is acceptable or even desirable. For merchants who need predictable revenue in euros or dollars, it's a risk.

Converting immediately means using an exchange API (Kraken, Coinbase, or your node provider's built-in exchange) to sell the Bitcoin seconds after you receive it. This locks in your revenue in local currency but costs a small fee (typically 0.5% to 1%). Most payment processors offer this as a checkbox: "Convert Lightning payments to USD automatically."

Your accounting software needs to record both the Bitcoin amount received and the fiat amount settled, because tax authorities treat them as separate transactions. If you're in the US, the IRS treats Bitcoin received as income at its fair market value on the date of receipt, then any gain or loss when you convert it as a capital gain or loss.

Handling failed payments and customer support

Lightning payments fail more often than card payments, usually because of liquidity or network issues, not customer error. A customer might see "Payment failed: insufficient channel capacity" or "Route not found." This is frustrating and requires clear messaging.

Your gateway should show customers why a payment failed and offer a fallback: either retry the Lightning payment, use a different payment method, or contact support. Most gateways do this automatically, but check your processor's documentation to confirm.

If a customer pays via Lightning but the invoice doesn't mark as received, the payment is still on the network—it just hasn't reached your node yet. This usually resolves in seconds, but if it takes more than a few minutes, the customer should contact you with their payment hash (a unique identifier for the transaction). You can look up the payment on a Lightning block explorer (like 1ML or Amboss) to confirm it was sent, then manually mark the invoice as paid.

Keep a support email or chat ready for Lightning-specific issues. Most customers who use Lightning are technical enough to understand "your node was offline" or "we're rebalancing channels," but some won't be. Have a simple explanation ready and a way to process refunds if needed.

Frequently Asked Questions

Can I accept Lightning payments without holding Bitcoin?

Yes. Enable automatic conversion to fiat currency in your gateway settings. Every Lightning payment converts to dollars, euros, or your local currency within seconds and settles to your bank account. You never touch Bitcoin; your node handles the technical side.

What happens if my Lightning node goes offline?

Customers can't pay you while it's offline, and any payments in transit may fail. If you use a hosted node service, their infrastructure is redundant and rarely goes down. If you run your own node on a home server, an internet outage or power loss will take you offline. Most merchants run their own node only if they can commit to keeping it online 24/7 or use a hosting provider.

Is Lightning safe, or can customers cheat me?

Lightning is cryptographically secured the same way Bitcoin is. Once a payment reaches your node, it's final—the customer can't reverse it or claim they didn't send it. The main risk is that a payment appears to succeed but doesn't actually reach you, which is why you should wait for confirmation before shipping goods or delivering services.

Do I need to understand Bitcoin to accept Lightning payments?

No. If you use a hosted node service or a processor like Stripe, you just enable it and let the software handle the details. You see Lightning payments in your dashboard the same way you see card payments. Understanding the basics helps with troubleshooting, but it's not required to get your free guide.

What's the difference between Lightning and accepting Bitcoin directly on-chain?

On-chain Bitcoin payments take 10 minutes to an hour to confirm and cost $1 to $10 per transaction. Lightning payments confirm in seconds and cost fractions of a cent. Lightning is better for small, frequent payments; on-chain is better for large, infrequent ones. You can offer both.