Lightning Network Payment Integration for Your Website

Integrating Lightning Network payments into your website is the modern standard for crypto stores, streaming billing, and micro-payment platforms. The cost depends on the complexity of integration and required features.

On-chain Bitcoin works well for storage but not for daily payments: fees of $1–20 during congestion, confirmation times of 10–60 minutes. Lightning Network (LN) solves this—instant transactions for fractions of a cent. Lightning Network is 100x cheaper and 1000x faster than on-chain. Our team has extensive experience integrating LN into websites: we have launched 30+ projects for e-commerce, donation platforms, and DeFi applications. We guarantee stable channel operation and liquidity automation. For example, with 1,000 payments of $5 each, savings on fees amount to about $150 per month compared to on-chain.

Which architecture to choose: own node or custody?

The first decision is the level of control. An own LN node (LND or Core Lightning) gives full control, zero intermediary fees, and scalability. However, it requires managing channels and liquidity. Custody solutions (OpenNode, Strike, BTCPay Cloud) are simpler but you trust a third party. For stores with turnover >1000 sat/day, an own node pays for itself in 3–6 months. For production LND, a VPS with 4 vCPU, 8GB RAM, and 500GB SSD is required, plus Bitcoin Core and PostgreSQL. We use Ubuntu 22.04 LTS.

Why choose LND for production?

Lightning Labs is the most stable and documented LN daemon. In production we use LND with a Bitcoin full node and PostgreSQL for high availability. Example config:

# Minimal lnd.conf for production
[Application Options]
alias=MyShop-LN
color=#FF6600
maxpendingchannels=5

[Bitcoin]
bitcoin.active=1
bitcoin.mainnet=1
bitcoin.node=bitcoind

[Bitcoind]
bitcoind.rpchost=localhost
bitcoind.rpcuser=bitcoinrpc
bitcoind.rpcpass=strongpassword
bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

[protocol]
protocol.wumbo-channels=true

Managing LN channel liquidity

The main operational complexity of LN is inbound liquidity. A payment only succeeds if there are channels on the path with sufficient funds. Strategies:

1. Lightning Pool — buy inbound liquidity on the marketplace from Lightning Labs (cost 0.1-0.5% of the amount).
2. Loop In — submarine swap: on-chain BTC → LN, you get an inbound channel (fixed fee ~2000 sat).
3. Partner nodes — open channels with large players (ACINQ, Kraken), they often open inbound channels (0% fee, but requires negotiation).

Strategy comparison:

// Loop In to replenish inbound liquidity
const loopdClient = new LoopClient(LOOPD_HOST)

async function increaseInboundLiquidity(amountSats: number): Promise<void> {
    const quote = await loopdClient.loopInQuote({ amt: amountSats })
    console.log(`Loop In quote: ${quote.swap_fee_sat} sats fee, ${quote.miner_fee_sat} sats miner fee`)
    await loopdClient.loopIn({
        amt: amountSats,
        max_swap_routing_fee: quote.swap_fee_sat,
        max_miner_fee: quote.miner_fee_sat,
        external_htlc: false,
    })
}

Invoices and payment processing

LND provides a gRPC API. For Node.js we use @lightningpolar/lnd. Create an invoice linked to an order.

import { createLnRpc } from '@lightningpolar/lnd'

const lnRpc = await createLnRpc({
    server: 'localhost:10009',
    tls: fs.readFileSync('/home/bitcoin/.lnd/tls.cert'),
    macaroon: fs.readFileSync('/home/bitcoin/.lnd/data/chain/bitcoin/mainnet/invoice.macaroon'),
})

async function createInvoice(amountSats: number, orderId: string, expirySeconds = 3600) {
    const invoice = await lnRpc.addInvoice({
        value: amountSats,
        expiry: expirySeconds,
        r_preimage: crypto.randomBytes(32),
    })
    await db('ln_invoices').insert({
        order_id: orderId,
        payment_hash: Buffer.from(invoice.r_hash).toString('hex'),
        payment_request: invoice.payment_request,
        amount_sats: amountSats,
        expires_at: new Date(Date.now() + expirySeconds * 1000),
        status: 'pending',
    })
    return {
        paymentRequest: invoice.payment_request,
        paymentHash: Buffer.from(invoice.r_hash).toString('hex'),
        expiresAt: new Date(Date.now() + expirySeconds * 1000),
    }
}

Tracking payment—use the SubscribeInvoice stream. Do not poll status: LND will notify you of the event.

Step-by-step LND setup for production

1. Install Bitcoin Core and wait for synchronization (IBD can take 2-3 days on good hardware).
2. Install LND, configure lnd.conf (as above), start.
3. Create a wallet via lncli create, save the seed.
4. Open channels: at least 2-3 channels with sufficient liquidity to receive payments.
5. Set up automatic liquidity management (e.g., via LND Autopilot or custom scripts).
6. Integrate API: invoice creation, WebSocket for notifications.
7. Monitoring: Prometheus + Grafana, alerting for low liquidity.

What is included in the work

• Deployment of Bitcoin Core + LND on VPS (4 vCPU, 8GB RAM, 500GB SSD)
• Channel setup and initial liquidity
• API endpoints for creating/checking invoices
• WebSocket payment notifications
• Operational documentation and monitoring (Prometheus + Grafana)
• 30 days of post-launch support

Contact us to evaluate your project. We implement turnkey: from hosting selection to UX with QR code and timer. Request a consultation—we will help you choose the optimal architecture for your business.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.