We're building the
open standard for payments
in the rest of the world.
PipraPay started in 2025 when a small eCommerce entrepreneur in Bangladesh struggled to manage manual payment confirmations and lost customer orders. Today, developers and merchants around the world use PipraPay to automate payments and run their businesses with full control.
Make payment infrastructure something the unsubscribed half of the world can own.
Stripe and friends have done remarkable work — for the markets they serve. PipraPay is for the other 100+ countries: open, self-hostable, no per-transaction fees from us, and built to interoperate with the rails that already exist on the ground.
Six things we'd defend in a hallway argument.
Open by default
If a decision affects users, the discussion happens in public. RFCs, retrospectives, even most architecture docs.
Verifiable claims
Every number on a marketing page should trace back to a chart, a benchmark, or a verifiable count. If we can't show it, we don't say it.
Built for the unserved
Default to the slow network, the unstable SIM, the obscure currency, the country you've never heard of. Wealthy markets work as a side-effect.
Boring infrastructure
Payment systems should be predictable, deterministic, and unsurprising. Excitement belongs in the dashboard, not the database.
Sustainable open source
Free forever doesn't mean unfunded. Foundation grants, a small seed round, and sponsoring deployments keep the lights on.
Slow hiring
We grow the team only when we'd be embarrassed not to. Headcount isn't a metric we celebrate.
Eight humans, four continents.
Plus 12 part-time contractors and the 380 contributors we owe everything to.
We're hiring slowly. Always.
4 open roles · remote-first · published salary bands · async-friendly