P

    PayMongo

    Powerful financial tools for fast-growing disruptors

    Founded
    2019
    Headquarters
    Taguig City, Philippines
    Stage
    Series B
    Total raised
    US$46M
    From recorded rounds
    Licences
    2
    BSP

    Overview

    PayMongo is a leading Philippine payments platform that lets businesses accept online and in-person payments — via cards, e-wallets (GCash, Maya), QR Ph, online banking and installments — through a single integration, plus payment links, invoices and checkout. Founded in 2019 (the first Philippine company backed by Y Combinator and Stripe), it is a BSP-registered Operator of Payment System, with an Electronic Money Issuer license held by its subsidiary PayMongo Payments, Inc. It has raised about US$46M to date, including a US$31M Series B in 2022.

    Mission

    We aim to enable Filipino businesses to thrive in the digital economy by providing secure, user-friendly, and accessible payment solutions.

    Products

    • Payment Gateway
    • Checkout
    • Payment Links
    • Invoices

    Serves

    MSMEsE-commerce businessesStartupsEnterprises

    Funding and ownership

    Total raised

    US$46M

    Sum of recorded funding rounds

    Stage

    Series B

    Investors and shareholders

    StripeY CombinatorFounders FundPeter ThielGlobal Founders CapitalJAM Fund (Justin Mateen)ICCP-SBI Venture PartnersKaya Founders

    Figures are calculated from the funding rounds recorded for this company.

    People

    • Francis PlazaCo-founder (former CEO)
    • Jaime Hing IIICo-founder (former CTO; now PayRex CEO)
    • Luis SiaCo-founder & Chairman
    • Edwin LacierdaCo-founder (now PayRex President)
    • Jojo MalolosPresident & CEO

    Licences and certifications

    Awards and recognition

    • Best Payment Gateway Philippines 2022

    Developers

    APIs available

    PayMongo's official entry point for developer and integration work. Depending on the company it may be public documentation, a sandbox, or a partnership contact.

    Developer and integration access

    Something out of date? Suggest a correction