Pouch.ph primary sources — 2026-05-01

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is Pouch.ph’s official homepage, app surface, and public API specification.

Primary-source snapshots

1) Official homepage

• URL: https://pouch.ph/
• Key excerpt:
  • The homepage says Pouch.ph is a Philippines-based payments company offering Lightning Network payment processing for fast, low-cost, and more connected transactions.
  • It says Pouch builds and runs Lightning-based payment systems for instant settlement, global interoperability, and practical use cases such as merchant payments and cross-border transfers.
  • It also says Pouch operates as a licensed Operator of Payment Systems under the Bangko Sentral ng Pilipinas.

2) Bitcoin Island positioning

• URL: https://pouch.ph/
• Key excerpt:
  • The homepage says Pouch supports the Bitcoin Island Project, described as a community-led initiative focused on real-world Lightning payments, education, and everyday usage across island economies.
  • This matters because it shows that merchant distribution and local adoption are part of the product story, not just a side marketing campaign.

3) App / gateway surface

• URL: https://app.pouch.ph/
• Key excerpt:
  • The app HTML identifies itself as Pouch.ph | Bitcoin Payment Gateway and Pouch Tip Link.
  • The dynamic PWA manifest also uses Pouch Web and scopes the app per path, which suggests shareable payment-link or merchant-facing web flows rather than only a generic account portal.

4) Public API specification

• URL: https://raw.githubusercontent.com/pouch-ph/public/master/swagger.yaml
• Key excerpt:
  • The OpenAPI document defines /v1 endpoints for creating invoices, paying invoices, and creating / listing / fetching / updating / deleting webhooks.
  • The schemas define invoice, transaction, sender, recipient, and webhook objects.
  • This is the clearest first-party evidence that Pouch exposes a merchant or application integration layer instead of only a closed consumer app.

5) Merchant checkout surface

• URL: https://pouch.ph/shop
• Key excerpt:
  • The shop page is a thin wrapper around an iframe that loads a BTCPay Server point-of-sale app hosted on a Pouch subdomain.
  • That is a strong operational clue that merchant acceptance and checkout tooling are part of Pouch’s real deployment surface.

6) GitHub organization surface

• URL: https://github.com/pouch-ph
• Key excerpt:
  • The public organization links back to https://pouch.ph and hosts the public repository containing the exposed API spec.
  • The repo surface is limited and somewhat sparse, but it still provides a concrete first-party integration artifact.

Working conclusion

Pouch.ph is best cataloged as a regulated regional Lightning payments control plane: merchant and gateway infrastructure first, with tip links, invoicing, webhooks, and local checkout surfaces layered around Lightning-based settlement. The strongest evidence is the combination of Lightning payment-processing claims, BSP OPS positioning, gateway / tip-link app labeling, BTCPay-backed shop infrastructure, and the public invoice-and-webhook API spec.