Cowrie Research

pouch-ph

2 min read

Pouch.ph

  • Name: Pouch.ph
  • URL: https://pouch.ph/
  • Category: Lightning payments infrastructure / bitcoin payment gateway / Philippines OPS-regulated merchant-and-webhook control plane
  • Tags: bitcoin-ecosystem
  • Summary: Pouch.ph is a Philippines-focused Lightning payments operator. The substance is merchant processing, webhooked invoice flows, cross-border money movement, and local regulatory posture — not a generic wallet story.
  • What it does:
    • Operates as a Philippines-based Lightning payments company focused on real-world payment processing
    • Positions Lightning for merchant payments and cross-border transfer use cases with an explicit local-operator and compliance posture
    • Supports the Bitcoin Island Project as an adoption and merchant-enablement initiative around everyday Lightning usage
    • Runs a web application that identifies itself as a Pouch Bitcoin payment gateway and tip-link surface
    • Publishes an OpenAPI spec with /v1 invoice-creation, invoice-payment, and webhook-management endpoints for integrations
    • Embeds a BTCPay Server point-of-sale surface in its shop flow, which is a strong clue that the company is packaging merchant checkout operations rather than only a wallet front end
  • Key claims:
    • The homepage says Pouch.ph is a Philippines-based payments company offering Lightning Network payment processing for fast, low-cost, and more connected transactions
    • The homepage says the company builds and runs Lightning-based payment systems for instant settlement, global interoperability, and practical use cases such as merchant payments and cross-border transfers
    • The homepage says Pouch operates as a licensed Operator of Payment Systems under the Bangko Sentral ng Pilipinas, which matters because it frames Pouch as a regulated operational payments layer rather than only a grassroots Lightning app
    • The web-app HTML identifies the product as Pouch.ph | Bitcoin Payment Gateway and Pouch Tip Link, which is a useful first-party signal that checkout and shareable payment flows are core product surfaces
    • The public swagger.yaml spec exposes invoice creation, invoice payment, webhook creation/listing/update/deletion, and transaction / recipient / sender schemas, which is strong evidence of an app-facing integration layer
    • The shop page embeds a BTCPay Server POS app hosted on a Pouch subdomain, reinforcing that merchant acceptance tooling is part of the operating stack
  • Whitepaper: No canonical Pouch.ph whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official homepage, the payment-gateway web app, the BTCPay-backed shop surface, and the public API specification in Pouch’s GitHub org; see ../whitepapers/pouch-ph-primary-sources-2026-05-01.md.
  • Sources:

Internal linkages

Graph View