LNTPay primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current sources of truth were LNTPay’s official homepage, docs corpus, pay-per-request quickstart, and public Swagger API reference.
• The decisive signal in this pass was that LNTPay is packaging recurring API monetization and Lightning micropayment operations—not broad checkout or fiat/stablecoin rails.

Primary-source snapshots

1) Official homepage

• URL: https://www.lntpay.com/
• Key excerpt:
  • The homepage positions LNTPay as “Lightning-native infrastructure” for pay-per-use, paywalls, and microtransactions with sats.
  • It foregrounds three primitives—ledger, webhooks, and charges—with developer-oriented language rather than ecommerce or consumer-wallet framing.
  • It also explicitly says LNTPay is not a multi-coin checkout, not an ecommerce plugin, and not a fiat or stablecoin gateway.

2) Docs overview

• URL: https://docs.lntpay.com/docs
• Key excerpt:
  • The docs define workspaces, charges, ledger, webhooks, and withdrawals as the core model.
  • A workspace groups API keys, charges, webhooks, withdrawals, and a ledger.
  • Charges are BOLT11 invoices; paid charges credit the workspace balance.
  • The ledger distinguishes available from locked balance, and the auth section highlights bearer tokens, scopes, and idempotency keys.

3) Pay-per-request quickstart

• URL: https://docs.lntpay.com/quickstart-pay-per-request
• Key excerpt:
  • The quickstart shows the intended canonical use case: an app creates a charge for an API request, the client pays the BOLT11 invoice, LNTPay sends a charge.paid webhook, and the app unlocks the API response.
  • The example uses @lntpay/sdk, requires charges:write and webhooks:read, and verifies x-lntpay-signature against the raw request body with HMAC-SHA256.
  • This is strong evidence that LNTPay is a paid-API / micropayments control plane rather than a generic wallet tool.

4) Public API reference

• URL: https://api.lntpay.com/docs
• Key excerpt:
  • The public API reference is exposed through a Swagger UI.
  • In this pass, the docs surface endpoint groups including /v1/charges, /v1/charges/usage, /v1/withdrawals, and /v1/webhooks/endpoints.
  • Even without a separate whitepaper, that endpoint structure reinforces the operating model: invoice creation, usage/quota awareness, withdrawals, and webhook endpoint management.

Working conclusion

LNTPay is best cataloged as Lightning micropayments infrastructure and a paid-API control plane. The key evidence is the combination of BOLT11 charge creation, workspace ledger balances, signed webhook delivery, outbound Lightning withdrawals, scoped API keys, and a first-party quickstart for gating API responses on charge.paid settlement.