How AALogics Integrated AssanPay with Edhi Foundation's Odoo Ecosystem to Simplify Payment Management

1. The Context: Edhi's Odoo Ecosystem

Edhi Foundation is one of Pakistan's largest non-profit social welfare organizations, running ambulance services, shelters, and donation-funded relief programs across the country. AALogics previously developed Edhi Foundation's Odoo-based website and eCommerce environment, migrating the organization's digital presence onto Odoo and building out its donation and content management workflows. That existing relationship put AALogics in a position to also work on the ERP side of Edhi's Odoo ecosystem, including how payment infrastructure was structured behind the scenes.

For an organization that depends on donations processed online, the payment layer is not a peripheral feature. It is one of the systems donors interact with directly, and it is one of the systems the finance team relies on to reconcile what has actually been collected. In Edhi's Odoo environment, several payment arrangements had accumulated over time to support different transaction needs.

2. The Challenge: Fragmented Payment Management

Before this project, Edhi's Odoo setup already had multiple payment arrangements in place, including UBL, Faysal Bank, and PayFast. Each of these had been integrated to support online transactions, but each also came with its own dashboard, its own transaction structure, and its own way of reporting what had been collected.

This is a common pattern in organizations that add payment providers incrementally rather than through a single, planned architecture. Each new provider solves an immediate need, but the cumulative effect is a payment environment that is harder to monitor and reconcile as a whole. AALogics' development team described the day-to-day reality of this setup as one that required logging into separate dashboards, working with different transaction charge structures, and manually piecing together how much money had actually come in across providers.

None of this made any single provider unreliable on its own. The problem was structural: as the number of payment arrangements grew, so did the operational overhead of managing them as a group. That overhead does not show up as a single dramatic failure — it shows up as recurring, low-level friction every time someone needs to answer a simple question like "how much did we collect this week, and through which channel?"

3. The Requirement: A More Centralized Payment Approach

Given this environment, the practical requirement was not "add one more payment provider." It was to reduce the fragmentation itself by routing new payment channels through a single gateway layer, rather than building a separate, standalone Odoo integration for every individual payment method Edhi might want to support in the future.

This distinction matters. Integrating each payment channel directly into Odoo, one at a time, means every new channel adds its own connection to maintain, its own edge cases to test, and its own dashboard to check. A gateway that can expose multiple channels through one integration point changes that equation: the Odoo-side integration work is done once, against the gateway, and additional channels can potentially be enabled through that same connection.

This is the reasoning that led to evaluating AssanPay as the gateway layer for new payment channels in Edhi's Odoo environment. It is worth being precise here: this decision addressed new payment channels being added going forward. It did not, on its own, require removing or replacing the UBL, Faysal Bank, or PayFast arrangements already in place.

4. Our Approach: Integrating AssanPay with Odoo

AALogics approached the integration in four stages.

5. The Solution: AssanPay Payment Gateway Integration

The core of the solution is straightforward: Edhi's Odoo ecosystem now connects to AssanPay as a payment gateway, and AssanPay in turn exposes the specific payment channels — JazzCash and QR payment — that Edhi has chosen to enable.

This is different from building a direct, one-off Odoo integration for JazzCash and a separate one for QR payments. By integrating at the gateway level, AALogics gave Edhi a single connection point that can, in principle, support additional AssanPay-enabled channels later without requiring a new ground-up integration for each one.

The practical benefit for Edhi's team is centered on the channels processed through AssanPay: transactions on those channels can be viewed and managed through AssanPay's own dashboard, rather than requiring a channel-specific system for each one. This does not change how the pre-existing UBL, Faysal Bank, or PayFast arrangements are managed — those remain separate, as before. What changes is that any transaction volume moving through JazzCash or QR now sits inside one additional, centralized layer instead of requiring its own dedicated integration.

6. Payment Workflow

At a conceptual level, the payment flow for AssanPay-enabled transactions in Edhi's Odoo environment works like this:

7. Current Payment Channels

It is important to be precise about what "AssanPay integration" means for Edhi today, because AssanPay itself supports more payment channels than what is currently live in this implementation.

Currently Enabled for Edhi

8. Business Outcome: Simplified Payment Management

Because this project addressed the channels processed through AssanPay specifically, the outcome should be described in those terms rather than as a blanket statement about all of Edhi's payments.

The UBL, Faysal Bank, and PayFast arrangements continue to operate as they did before. The change here is additive and specific: it simplifies management for the channels now running through AssanPay, and it gives Edhi a more scalable pattern for adding payment channels going forward.

9. Technical Highlights

10. Key Takeaways

The lesson from this project is less about any single payment channel and more about integration architecture. When an organization's Odoo environment accumulates payment providers one at a time, the operational cost is not the providers themselves — it is the number of separate systems someone has to manage in parallel.

Routing new payment channels through a single gateway, rather than integrating each one directly into Odoo, is one way to slow that accumulation of separate systems. It does not retroactively simplify arrangements that already exist outside the gateway, and it is not a guarantee that every future payment channel will fit neatly through the same connection. What it demonstrated in Edhi's case is a more centralized starting point for the channels it does cover, and a pattern that can be extended if Edhi chooses to enable additional AssanPay channels later.