Flash primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest first-party sources were Flash’s self-custodial merchant docs plus the public GitHub repos for the broader Flash app/ecosystem.
• The marketing surfaces were fragmented in this pass: the merchant docs were concrete, while the broader product shape came through more clearly in the GitHub repos.

Primary-source snapshots

1) Merchant-docs welcome page

• URL: https://docs.paywithflash.com/
• Key excerpt:
  • Flash describes itself as a Bitcoin Lightning payments gateway.
  • The docs say every payment is processed in a self-custodial and peer-to-peer manner and sent directly to the merchant’s wallet.
  • The page foregrounds Flashes, subscriptions, and public APIs as the core monetization surface.

2) Merchant-docs ?ask= answer on products, settlement, and integrations

• URL: https://docs.paywithflash.com/readme.md?ask=What%20are%20Flash%27s%20core%20merchant%20products%2C%20how%20does%20self-custodial%20settlement%20work%2C%20and%20what%20API%20or%20integration%20surfaces%20are%20described%3F
• Key excerpt:
  • The answer groups Flash’s merchant surface into Checkouts, Subscriptions, and Stores.
  • It says self-custodial settlement means Flash does not hold merchant funds; payments go directly to the merchant wallet and Flash later takes a small fee transaction automatically.
  • It points to Nostr Wallet Connect plus supported wallets such as Flash Wallet, Coinos, and Alby, and it references WooCommerce, Shopify, Wix, and public APIs.

3) Checkouts overview

• URL: https://docs.paywithflash.com/products/checkouts
• Key excerpt:
  • Flash’s checkout layer includes payment links, donation widgets, page paywalls, video paywalls, and payment buttons.
  • The docs say these are copy/paste-friendly monetization tools rather than conventional storefront-only flows.
  • Payments are described as processing directly to the user’s wallet.

4) Subscriptions overview

• URL: https://docs.paywithflash.com/products/editor
• Key excerpt:
  • The subscriptions docs describe recurring Lightning payments with plan creation, checkout URLs, prefilled user data, authentication, API endpoints, and webhooks.
  • This is good evidence that Flash has an operator-facing recurring-billing surface, not only a one-time checkout flow.

5) Integrations overview

• URL: https://docs.paywithflash.com/integrations
• Key excerpt:
  • Flash documents integrations for WooCommerce, Shopify, and Wix.
  • The page repeatedly frames Flash as a non-custodial Lightning payment gateway with plugin and API surfaces.

6) awesome-flash ecosystem repository

• URL: https://github.com/lnflash/awesome-flash
• Key excerpt:
  • The repo describes Flash as a mobile-first Bitcoin Lightning wallet and open financial infrastructure designed for the Caribbean and global south.
  • It enumerates Flash Backend, Flash Mobile App, Flash POS, Flash Improvement Proposals, FlashCard, Flash Forge (Cashu mint), Flash Cash (Cashu web wallet), and several ecosystem integrations.
  • It also references Nostr, BTCPayServer, merchant rewards, and developer/community resources, which materially expands the project picture beyond the merchant docs alone.

7) Official website repository

• URL: https://github.com/lnflash/flash-site
• Key excerpt:
  • The repo calls Flash “Jamaica’s Bitcoin wallet and merchant rewards platform, powered by Lightning Network.”
  • It explicitly lists Flash Mobile, Flash POS, Flash Card, and a REST/WebSocket Flash API as core products.
  • The site structure also points to a Jamaica merchant map, merchant profiles, Lightning QR payments, and Nostr chat on merchant pages.

8) Backend repository

• URL: https://github.com/lnflash/flash
• Key excerpt:
  • The backend repo describes Flash as “an opinionated bitcoin banking platform” forked from Galoy.
  • It references GraphQL APIs, an internal ledger, BTC payments over Lightning and onchain rails, notifications, merchant maps, and broader operational components.
  • This suggests a thicker ledger-and-payments substrate than the merchant-checkout docs alone reveal.

Working conclusion

Flash is best cataloged as a regional Bitcoin wallet-and-merchant control plane or community-finance stack rather than as a simple wallet, donation button, or payment gateway. The decisive evidence was the combination of self-custodial merchant settlement docs, recurring-billing and integration surfaces, and a first-party GitHub footprint that expands the product into Jamaica-centered wallet, POS, rewards, API, Cashu, and Nostr layers. The main caveat is that the public surfaces are split: the merchant docs are the clearest source for settlement behavior, while the broader product breadth is easiest to recover from the project’s repos.