Custom Odoo Payment Gateway Integration with Edhi Foundation's Ecommerce for AssanPay

By advertising, 24 August, 2026
Client Case Study · Odoo · Payment Integration

How AALogics Integrated AssanPay with Edhi Foundation's Odoo Donation Platform

A client implementation showing how AALogics added AssanPay as a payment provider to Edhi Foundation's Odoo donation website, enabling donors to complete payments through the channels available within AssanPay.

Client Edhi Foundation
Industry Nonprofit / Social Welfare
Platform Odoo Website + Donations + ERP
Solution AssanPay Payment Gateway Integration
Services Odoo Development · Payment Gateway Integration · Custom API Integration
The context

1. The Context: Edhi's Odoo Donation Environment

Edhi Foundation is one of Pakistan's largest nonprofit social welfare organizations, supporting ambulance services, shelters, and donation-funded welfare programs across the country. Its digital operations include an Odoo-based website and donation environment used to support online contributions and related workflows.

As part of its ongoing Odoo ecosystem, Edhi already had several payment arrangements available for handling online transactions. These included PayFast, UBL, and bank or wire transfer arrangements. Each arrangement served its own purpose and remained separate within the broader payment environment.

AALogics was brought in to extend that environment by integrating another payment provider: AssanPay. The objective was not to replace Edhi's existing payment arrangements, but to add another payment option through an Odoo-compatible gateway integration.

The challenge

2. The Challenge: Adding Another Payment Provider Without Disrupting the Existing Setup

Edhi's Odoo donation website already supported multiple payment arrangements. Adding another provider therefore needed to fit into the existing Odoo payment environment without requiring the organization to replace the methods it was already using.

The practical challenge was to introduce AssanPay as an additional payment provider while keeping the existing payment arrangements available. The integration also needed to give donors a straightforward path from the Odoo donation checkout to the AssanPay payment flow and back to Odoo after the transaction.

Existing EnvironmentIntegration Requirement
Existing payment arrangementsAdd AssanPay without replacing existing options
Odoo donation workflowConnect the donation checkout to AssanPay
External payment processingRoute the donor into AssanPay's payment flow
Payment completionReturn the donor to Odoo after payment processing
Existing ecosystemMaintain compatibility with the current Odoo setup

The key requirement was additive integration.

AssanPay needed to be introduced as an additional Odoo payment provider, rather than replacing Edhi's existing PayFast, UBL, or bank-transfer arrangements.

The requirement

3. The Requirement: Connect AssanPay to Odoo's Donation Workflow

The requirement was to integrate AssanPay into Edhi's existing Odoo donation website so that donors could select AssanPay during the payment process and continue to the gateway's payment page.

This meant creating an Odoo-side connection to AssanPay rather than developing separate Odoo integrations for every individual payment option available through the gateway.

For Edhi's current implementation, JazzCash and QR payments are the enabled payment options available through the AssanPay flow. They are not separate Odoo payment-provider integrations.

01 Odoo: Donation checkout
02 AssanPay: Integrated payment provider
03 Payment Options: JazzCash + QR

Important distinction:

Donors select AssanPay within Odoo. JazzCash and QR payments are options available within the AssanPay payment flow, not separate payment providers integrated directly into Odoo.

AALogics approach

4. Our Approach: Integrating AssanPay with Odoo

AALogics approached the implementation by first understanding Edhi's existing Odoo payment environment and then integrating AssanPay into that existing workflow.

01

Payment Environment Analysis

The team reviewed the existing Odoo donation and payment environment to understand how AssanPay would fit alongside the payment arrangements already in place.

02

AssanPay Integration

AALogics connected Edhi's Odoo environment with AssanPay as an additional payment provider, creating the required path from the Odoo donation workflow to the external gateway.

03

Payment Flow Configuration

The AssanPay flow was configured around the payment options currently enabled for Edhi, namely JazzCash and QR payment.

04

Testing and Deployment

The payment workflow was tested against Edhi's Odoo environment before deployment to verify that the transaction could move through the expected payment flow and return to Odoo after processing.

The solution

5. The Solution: AssanPay Payment Gateway Integration

The core solution was to add AssanPay as a payment provider within Edhi's Odoo donation environment. This gives donors an additional payment route without requiring Edhi to remove or replace its existing payment arrangements.

The important architectural distinction is that Odoo connects to AssanPay as the payment provider. Once the donor enters the AssanPay flow, the payment options available through that gateway can be used to complete the transaction.

01 Edhi Odoo Donation website and payment checkout
02 AssanPay Integrated payment provider
03A JazzCash Enabled payment option
03B QR Payment Enabled payment option

For the transactions processed through AssanPay, the gateway provides the payment-processing layer and its associated transaction management. This should not be interpreted as a replacement for Edhi's other payment arrangements: PayFast, UBL, and bank or wire transfer remain separate from the AssanPay implementation.

How it works

6. Payment Workflow

At a conceptual level, an AssanPay-enabled donation follows this sequence:

01 Donor: Starts a donation
02 Edhi Odoo: Donor selects AssanPay
03 AssanPay: Payment processing begins
04 JazzCash / QR: Available payment option
05 Odoo: Donation confirmed after return

Technical scope note:

The internal API requests, callbacks, authentication mechanisms, and transaction-verification logic are not documented publicly in this case study. At a high level, the completed payment flow returns the transaction to Odoo, where the donation can be confirmed.

Current implementation

7. Current Payment Options Through AssanPay

AssanPay supports multiple payment channels, but it is important to distinguish the gateway itself from the payment options available within its flow.

Odoo payment provider AssanPay 

The payment gateway integrated into Edhi's Odoo donation environment.

Currently enabled JazzCash + QR Payment 

The payment options currently available through AssanPay for Edhi.

Currently Enabled for Edhi

JazzCash

JazzCash is currently available through the AssanPay payment flow, giving donors an additional local payment option after selecting AssanPay during the Odoo donation process.

QR Payment

QR payment is also available through AssanPay for Edhi's current implementation, providing another way for donors to complete an AssanPay-processed transaction.

Current-state clarification:

AssanPay supports additional payment channels beyond JazzCash and QR payment. However, only these two are part of Edhi's current AssanPay implementation. They should not be described as separate Odoo payment-provider integrations.

The outcome

8. Business Outcome: An Additional Payment Route Through AssanPay

The outcome of the project should be viewed specifically within the scope of the AssanPay integration. AALogics added another payment provider to Edhi's Odoo donation environment without requiring the existing PayFast, UBL, or bank-transfer arrangements to be replaced.

01

Additional payment option

Edhi's Odoo donation environment gained AssanPay as an additional payment provider.

02

One Odoo-to-gateway connection

Odoo connects to AssanPay rather than requiring separate Odoo integrations for each payment option available through the gateway.

03

AssanPay transaction visibility

Transactions processed through AssanPay can be managed through the gateway's transaction-management environment.

04

Scalable gateway foundation

The existing Odoo-to-AssanPay connection provides a foundation for potentially enabling additional AssanPay-supported payment options in the future.

Scope of the outcome:

AssanPay does not centralize all of Edhi's payment arrangements. Existing PayFast, UBL, and bank-transfer arrangements remain separate. The improvement described here applies to the transactions processed through AssanPay.

Development scope

9. Technical Highlights

01 Odoo + AssanPay Integration 

Connected Edhi's existing Odoo environment with the AssanPay payment gateway.

02 Donation Checkout Integration 

Connected the Odoo donation payment workflow to AssanPay so donors can select the provider during checkout.

03 Gateway-Based Payment Flow 

Used AssanPay as the Odoo payment-provider connection rather than building separate Odoo integrations for JazzCash and QR.

04 Payment Return to Odoo 

Supported the payment flow through AssanPay and the return to Odoo after transaction processing.

05 Existing Ecosystem Compatibility 

Added the new payment provider alongside Edhi's existing payment arrangements without requiring those arrangements to be replaced.

What the project demonstrates

10. Key Takeaways

The Edhi implementation demonstrates that payment integration in Odoo is not simply about adding another button to a checkout page. The integration needs to fit the organization's existing payment environment, provide a clear donor journey, and connect the Odoo workflow with the external gateway responsible for processing the transaction.

In this project, AALogics added AssanPay as an additional Odoo payment provider. Donors can select AssanPay in the Odoo donation flow and continue to the gateway's payment process, where the payment options currently enabled for Edhi include JazzCash and QR payment.

Project Takeaways

  • AssanPay was integrated as an additional payment provider within Edhi's Odoo donation environment.
  • Donors select AssanPay in Odoo rather than selecting JazzCash or QR as separate Odoo providers.
  • JazzCash and QR payment are currently enabled within the AssanPay payment flow for Edhi.
  • Existing PayFast, UBL, and bank-transfer arrangements remain separate; the AssanPay implementation is additive.
  • The Odoo-to-AssanPay connection provides a potential foundation for enabling additional AssanPay-supported payment options later.
Frequently asked questions

Frequently Asked Questions

What's the difference between AssanPay and a payment option like JazzCash or QR payment?

AssanPay is the payment gateway integrated with Edhi's Odoo environment. JazzCash and QR payment are payment options available within the AssanPay payment flow. In other words, Odoo connects to AssanPay, and the donor can then use an available payment option within that gateway flow.

Does the donor select JazzCash or QR directly in Odoo?

No. In Edhi's implementation, the donor selects AssanPay in the Odoo donation checkout. The donor then continues through AssanPay's payment flow, where the currently enabled payment options include JazzCash and QR payment.

Did integrating AssanPay replace Edhi's existing payment arrangements?

No. The AssanPay integration is additive. Edhi's existing PayFast, UBL, and bank-transfer arrangements remain separate from the AssanPay implementation.

Does AssanPay centralize all of Edhi's payments?

No. AssanPay does not become a single dashboard for all of Edhi's payment arrangements. It provides the payment-processing and transaction-management layer for transactions processed through AssanPay. Existing payment arrangements such as PayFast, UBL, and bank transfer remain separate.

How does the AssanPay payment flow work on Edhi's Odoo website?

At a high level, the donor starts a donation on Edhi's Odoo website, selects AssanPay as the payment provider, and continues to the AssanPay payment flow. The donor completes the payment using an available option such as JazzCash or QR payment. After the payment process, the transaction returns to the Odoo environment and the donation can be confirmed.

Can additional AssanPay payment options be enabled in the future?

Potentially, yes. AssanPay supports payment channels beyond the options currently enabled for Edhi. Because the Odoo-to-AssanPay connection already exists, additional supported options may be able to use the same gateway integration rather than requiring a completely separate Odoo provider integration. Whether Edhi enables additional options is ultimately a decision for its team.

What does a project like this involve from a development perspective?

The implementation involved understanding the existing Odoo payment environment, integrating AssanPay as an additional payment provider, configuring the payment flow around the options required for Edhi, and testing the transaction journey before deployment. The exact internal implementation details are not publicly documented in this case study.

Need a similar integration?

11. Let's Solve Your Odoo Integration Challenge

Integrating a payment gateway into an existing Odoo environment requires more than connecting an external payment service. The integration needs to fit the existing checkout or donation workflow, handle the payment journey correctly, and work alongside the systems already used by the organization.

Need to integrate a payment gateway, API, or third-party service into your Odoo environment? AALogics develops custom Odoo integrations that connect business systems, payment platforms, and digital workflows, backed by an Odoo development and maintenance team that works with existing ERP environments rather than starting from scratch.

Contact AALogics  

Blog banner for the case study "Payment Gateway Odoo App"