Open source · AGPL-3.0 · community-funded

Support PipraPay

Open-source payment infrastructure needs community support. Every contribution keeps the platform free, independent, and growing for everyone.

Support options

Choose how you contribute.

Two direct ways to support the continued development of PipraPay.

Open source ecosystem

GitHub Sponsorship

Support PipraPay directly through GitHub Sponsors — the open-source ecosystem's preferred way to fund maintainers. Monthly or one-time. Cancel anytime.

  • Recognized as a GitHub Sponsor
  • Monthly or one-time contributions
  • Direct support to the maintainers
Sponsor on GitHub
Bangladesh · Local

Support from Bangladesh

Local contributors can support PipraPay via EPS (Electronic Payment System) gateway. Fast, familiar, and available to anyone in Bangladesh.

  • bKash, Nagad, and bank transfer
  • Local currency — BDT
  • Any amount, no minimums
Support via EPS Gateway
Why it matters

What your support enables.

Hosting & Infrastructure

Servers, CDN, CI/CD pipelines, and the build infrastructure that keeps every release fast and reliable.

Core Development

Funding maintainer time to ship new features, fix bugs, and keep up with evolving payment standards and gateway APIs.

API Maintenance

Keeping integrations up-to-date as payment gateways change their APIs, webhooks, and authentication protocols.

Open Source Sustainability

Ensuring PipraPay remains free forever — no paid tiers, no telemetry, no lock-in. Community support makes this promise possible.

Plugin Ecosystem

Building documentation, SDKs, and the plugin marketplace that lets developers extend PipraPay with new gateways and integrations.

Community Growth

Moderation, documentation, tutorials, and outreach that helps more developers and businesses discover and adopt PipraPay.

Transparency

Where your money goes.

We believe in full financial transparency. Sponsorships go directly toward keeping PipraPay free and growing — not overhead.

A detailed breakdown is published in the project's GitHub Sponsors profile. If you ever have questions about how funds are used, open an issue or email us directly.

Allocation breakdown

Core development & maintainers 50%
Servers & infrastructure 30%
Community & documentation 20%

Percentages are approximate and may adjust as the project scales. We commit to publishing updates whenever allocation changes.

Contribute more than money

Code is contribution too.

Don't have the budget to sponsor? Open a PR, report a bug, improve the docs, or just star the repo. Every action makes a difference.