Cowrie Research

lightning-enable

3 min read

Lightning Enable

  • Name: Lightning Enable
  • URL: https://lightningenable.com/
  • Category: Lightning commerce orchestration middleware / L402 payments infrastructure / agentic-commerce control plane
  • Tags: bitcoin-ecosystem
  • Summary: Lightning Enable is Lightning commerce middleware. It sits between the app and Strike or OpenNode, then sells the orchestration layer on top: L402 support, producer APIs, MCP tooling, and platform integrations. Useful because it packages the operator surface cleanly, not because it is a new payment rail.
  • What it does:
    • Connects platforms and APIs to Strike or OpenNode through a BYOA model so Lightning payments can be accepted without Lightning-node operations by the customer
    • Positions itself as middleware that forwards requests to the payment provider while the provider handles custody, settlement, and compliance
    • Supports both L402 and Machine Payments Protocol (MPP) flows for pay-per-request API monetization and machine-native authentication
    • Ships an open-source MCP server with 23 tools spanning wallet actions, L402 API access, producer flows, and Agent Service Agreement (ASA) tools for agent-to-agent commerce on Nostr
    • Offers platform integrations such as Shopify Commerce and Kentico Commerce in addition to the core API and dashboard surface
    • Uses subscription pricing rather than per-transaction fees, while the connected provider may still charge its own processing fees
  • Key claims:
    • The official site says Lightning Enable is “the infrastructure layer that turns payment into authentication,” which is a stronger clue that the product centers on orchestration and access control rather than custody
    • The docs introduction explicitly says Lightning Enable is a “commerce orchestration layer” that connects a platform to Strike or OpenNode and “never touch[es] your funds,” while the chosen provider handles payment processing, custody, and settlement
    • The product overview repeatedly frames the model as BYOA and says funds flow directly to the customer’s own provider account, which helps distinguish Lightning Enable from merchant-of-record or processor positioning
    • The product overview says both plans include REST API access, L402 support, MCP compatibility, and an L402 Producer API, showing the product is designed both for paying and for monetizing machine-facing services
    • The open-source MCP repository says the server exposes 23 tools, including 15 free wallet tools plus producer and ASA tools, which makes the consumer side of the platform materially broader than a simple checkout widget
    • The same repository documents support for Strike, LND, and Nostr Wallet Connect wallets such as CoinOS and Alby Hub, showing Lightning Enable is built as a wallet-agnostic agent-payment surface rather than only a hosted provider adapter
    • The official site and docs both emphasize flat subscription pricing with no per-transaction fee from Lightning Enable itself, reinforcing that the business model is middleware and product access rather than payment take-rate economics
  • Whitepaper: No canonical standalone Lightning Enable whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official site, the product/docs portal, and the open-source Lightning Enable MCP repository; see ../whitepapers/lightning-enable-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages

Graph View