PayPack Review (2026): Pricing, Features & Honest Verdict

TLDR

PayPack is a developer-first payment API for Rwanda that lets you accept and disburse MTN, Airtel, and Tigo mobile money through clean cashin and cashout endpoints, with SDKs for Go, Python, PHP, and Laravel. It is a solid local fintech building block. Best for: Rwandan developers accepting mobile money. Price: Custom per-transaction fee, no public flat plan. Rating: 6.3/10.

What is PayPack?

PayPack is a payment platform built for Rwanda, with a developer-first pitch: give engineers a clean API and good SDKs so they can accept mobile money in their own apps without wrestling with each telecom’s separate system. In Rwanda, mobile money is how most people pay, with MTN Mobile Money and Airtel Money dominating daily transactions. The problem is that integrating directly with each provider is painful. PayPack abstracts that away behind a single API that covers MTN, Airtel, and Tigo.

We dug into its documentation and found a product clearly aimed at developers rather than marketers. The docs cover authentication, a payment flow, cashin and cashout endpoints, and SDKs across several languages, with a public status page and a community forum. Alongside the API, PayPack offers no-code pieces too: a merchant dashboard, payment links, a hosted checkout you can embed, and even consumer-facing bill payment. But the heart of the product, and the reason it shows up in a developer-tools category, is the API.

What Are PayPack’s Key Features?

One API for three mobile money providers

PayPack’s core value is unifying MTN Mobile Money, Airtel Money, and Tigo Cash behind a single integration. Instead of building and maintaining three separate connections, you integrate once and accept payments from any of them. For a Rwandan startup, that consolidation is the whole point: it turns a multi-week telecom integration slog into a standard API call, which is exactly what a payment abstraction layer should do.

Cashin and cashout endpoints

The API exposes both cashin (collecting money from a customer’s mobile money account into your PayPack account) and cashout (disbursing money from your account out to a mobile money number). That two-way capability matters because plenty of products are not just storefronts; they are marketplaces, gig platforms, or services that need to pay people out. Having disbursement in the same API as collection means you can build a full two-sided money flow without a second provider.

SDKs and developer experience

PayPack documents SDKs for Go, JavaScript, Laravel, Python, and PHP, plus cURL examples, with Bearer-token authentication on protected endpoints. That language coverage hits most of the stacks a Rwandan web or mobile team would actually use, and official SDKs cut the integration time versus rolling your own HTTP client. The docs are organized around a clear quickstart, which is a good sign for a developer tool: the faster a developer gets a test transaction working, the better.

Webhooks, payment links, and checkout

Beyond raw API calls, PayPack supports webhooks for event-driven notifications, so your backend can react automatically when a payment completes rather than polling. It also offers payment links you can share to collect a payment and an embeddable hosted checkout for sites that do not want to build the payment UI themselves. This range, from low-level API to no-code links, lets both engineering teams and less technical merchants use the same platform. Webhooks in particular are the feature that separates a real payment integration from a toy: mobile money payments are asynchronous, and you need a reliable callback when the customer finally approves the charge on their phone, sometimes a minute or two after checkout.

Merchant dashboard and bill payments

PayPack pairs the API with a merchant dashboard for managing funds, monitoring transactions, and reviewing sales history, so non-developers on your team can see what is happening without reading API logs. There is also a consumer-facing side, PayPack Bills, covering utilities like electricity, StarTimes subscriptions, and airtime. While the bill-payment app is aimed at end users rather than developers, it signals that PayPack operates a working money-movement network in Rwanda, not just a thin API wrapper, which is reassuring when you are deciding whether to route real revenue through it.

How Much Does PayPack Cost?

PayPack does not publish a pricing page. The model is a per-transaction fee rather than a flat subscription: the API returns a fee field on each transaction, confirming that PayPack takes a cut per payment, but the exact rate or percentage is not documented publicly. Because we will not invent a number, the honest answer is that you must confirm the current transaction fee with PayPack directly before building on it. That opacity is a real downside for anyone trying to model unit economics up front.

For context, the African payments market it competes in is fee-based across the board. Flutterwave, the pan-African gateway, charges percentage-based fees that vary by country and method. Local Rwandan gateways like Kpay and multi-country processors like DPO Pay also price per transaction. So PayPack’s per-transaction approach is normal for the category; the difference is simply that competitors are more transparent about the headline rate, while PayPack keeps it behind a conversation.

Developers can integrate and test before going live, which softens the risk, but production transactions carry fees. Our advice: get the cashin and cashout rates in writing, including any difference between collection and disbursement, before you commit to PayPack as your payment rail.

Who is PayPack Best For?

Use PayPack if you are a Rwanda-based developer, startup, or merchant who needs to accept and disburse mobile money programmatically. The single API for MTN, Airtel, and Tigo, the SDK coverage across common languages, and the two-way cashin and cashout support make it a strong local building block. It is especially good for marketplaces and platforms that need to both collect from buyers and pay out to sellers within one integration.

Skip PayPack if you operate outside Rwanda, since it is Rwanda-only with no card or international rails. Also think twice if transparent, public pricing is essential to your planning, or if you need the reassurance of a large, heavily reviewed vendor. PayPack is a smaller player with limited independent reviews, so you are partly buying on the quality of the docs and your own testing rather than a deep track record you can verify from outside.

The strongest fit is a lean Rwandan engineering team building something local: a delivery app, a marketplace, a SaaS billing in local currency, or a fintech that needs both collection and payout. For that profile, PayPack’s focused, developer-first API is faster to ship with than a sprawling pan-African platform, and the local mobile money focus matches how customers actually pay.

Best PayPack Alternatives

Flutterwave

Flutterwave is the pan-African payments heavyweight, supporting cards, mobile money, and bank transfers across many countries including Rwanda. It is far broader than PayPack and a better fit if you need multi-country reach or card payments alongside mobile money. The trade-off is that it is a bigger, more general platform, so a Rwanda-only team may find PayPack’s focused mobile money API simpler to integrate for the local use case.

Kpay

Kpay is a Rwandan online payment gateway that supports Visa, Mastercard, and mobile money, with PCI DSS certification. It is the closer local competitor for merchants who want both cards and mobile money in one gateway rather than mobile money alone. If your customers include diaspora buyers or tourists who pay by card, Kpay’s card support is an advantage PayPack does not match, though PayPack leans harder into developer experience.

DPO Pay

DPO Pay (by Network) is an established multi-country African payment processor with a long track record and broad method coverage, including mobile money and cards across the continent. It suits businesses that want a regional, well-known processor and may expand beyond Rwanda. It is heavier and more enterprise-oriented than PayPack, so for a lean local startup PayPack’s lighter, developer-first API is often quicker to ship with.

Final Verdict: Is PayPack Worth It?

PayPack earns a 6.3 because it solves a real, specific problem well: it gives Rwandan developers a clean, well-documented API that unifies MTN, Airtel, and Tigo mobile money, with SDKs in the languages local teams actually use and both collection and disbursement in one place. For building a payment flow in a Rwandan app, that is genuinely useful, and the addition of webhooks, payment links, and hosted checkout means it scales from raw API to no-code without switching tools.

The rating is held back by two things: undocumented pricing and narrow reach. You cannot model your costs without contacting PayPack, and the platform is useless outside Rwanda, with limited independent reviews to vet reliability. If you are building in Rwanda and need mobile money, PayPack is worth a serious test: integrate in sandbox, confirm the per-transaction fees in writing, and pressure-test reliability before going live. If you need cards, international payments, or transparent public pricing, look at Kpay or Flutterwave instead.