Paymob Gateway for Magento 2

Key Features

Paymob card payments via hosted iframe checkout, keeping sensitive PAN data off your Magento server and reducing PCI-DSS scope

Mobile wallet acceptance (Vodafone Cash, Orange, Etisalat and similar) surfaced as a selectable checkout method

Meeza national card scheme support for Egyptian domestic acceptance

Apple Pay through Paymob, with domain verification and the Apple Pay button wired into the Magento checkout

ValU and BNPL installment options presented at checkout with plan selection passed to Paymob's intention API

Implemented on Magento's gateway command pool (authorize, capture, void, refund) via CommandPoolInterface and di.xml — not hardcoded API calls

HMAC-verified server-to-server callback/webhook handling so order state is set from trusted Paymob notifications, not the browser redirect

Encrypted API key storage and sandbox/live mode toggle under Stores > Configuration, guarded by a dedicated admin ACL resource

Per-website / per-store-view scope configuration for multi-country MENA settlement and multiple Paymob accounts

GraphQL and REST compatibility for headless, PWA Studio or mobile-app checkout front ends

Automatic order status and invoice handling on successful capture, with failed/abandoned payment recovery to a recoverable cart state

Upgrade-safe architecture using plugins/interceptors and observers instead of core rewrites, compatible with Magento Open Source and Adobe Commerce

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Paymob is one of the dominant payment processors across Egypt and the wider MENA region, but there is no polished, officially-maintained Adobe Commerce Marketplace module that covers its full acceptance stack the way Egyptian merchants actually need it. This is a build-to-order extension: ECOSIRE engineers, installs and supports a production-grade Paymob integration tailored to your store, payment methods and settlement setup.

The module ships as a standard Magento 2 component under app/code/Ecosire/Paymob, registered through registration.php and module.xml. Payment methods are implemented against Magento's Magento\Payment\Model\MethodInterface and the gateway command pool (CommandPoolInterface, ValidatorPoolInterface) wired in di.xml, so authorize, capture, void and refund flow through Magento's native payment service contracts rather than brittle direct calls. The storefront uses Paymob's hosted iframe so sensitive card data never touches your server, keeping you out of heavy PCI-DSS scope.

The integration covers Paymob's intention/order API and HMAC-verified server-to-server callbacks (validated in an observer/webhook controller, never trusted from the browser redirect alone), card payments, mobile wallets, Meeza, Apple Pay, and ValU / BNPL installment options selectable at checkout. Configuration lives under Stores > Configuration with proper admin ACL (Ecosire_Paymob::config), encrypted API keys, sandbox/live toggles, and per-website scope for multi-country MENA settlement.

You get a clean, upgrade-safe codebase (plugins/interceptors over core rewrites), GraphQL and REST compatibility for headless or PWA Studio storefronts, and order-status automation. Because it's built to order, it fits your Magento version (Open Source or Adobe Commerce), theme and checkout flow precisely — and ECOSIRE owns installation, UAT against Paymob sandbox, and go-live.

What you get

Custom Ecosire_Paymob Magento 2 module installed in your codebase under app/code (or supplied as a Composer package) with registration.php, module.xml and di.xml

Full Paymob method coverage configured to your account: cards, mobile wallets, Meeza, Apple Pay and ValU / BNPL

Admin configuration section under Stores > Configuration with encrypted keys, sandbox/live toggle, per-website scope and ACL

HMAC-verified webhook/callback controller plus order-status automation and refund support from the Magento admin

Sandbox UAT sign-off: end-to-end test transactions against Paymob's test environment before go-live

Install, configuration and admin-usage documentation plus a short handover walkthrough

Production deployment support and a defined post-launch support/bug-fix window

Who this is for

Egyptian D2C / retail merchant on Magento

An Egypt-based online retailer who must accept local cards, Meeza and mobile wallets to convert domestic shoppers and can't rely on international-only gateways.

MENA multi-country store operator

A merchant selling across Egypt and GCC markets who needs per-website Paymob settlement and locale-appropriate payment methods within a single Magento installation.

Conversion-focused brand needing BNPL

A higher-ticket brand wanting ValU / BNPL installments and Apple Pay at checkout to lift average order value and reduce cart abandonment among MENA buyers.

How Paymob Gateway for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
Native Paymob support (cards, wallets, Meeza, Apple Pay, ValU/BNPL)	Included	Partial support	Partial support
Built on Magento gateway command pool & service contracts (upgrade-safe, no core rewrites)	Included	Partial support	Partial support
HMAC-verified server-side webhook/callback handling	Included	Partial support	Partial support
Installed, configured and UAT-signed-off by the provider	Included	Partial support	Not included
Per-website multi-country MENA settlement configuration	Included	Partial support	Partial support
GraphQL / REST / PWA Studio headless compatibility	Included	Partial support	Partial support
Tailored to your exact Magento version, theme and checkout flow	Included	Included	Not included
Defined post-launch support and version-compatibility updates	Included	Partial support	Partial support

Frequently Asked Questions about Paymob Gateway for Magento 2

How long does delivery take, since this isn't an instant Marketplace download?

This is a build-to-order extension, not a one-click Adobe Commerce Marketplace install. Typical delivery is around 10–15 business days from receiving your Magento details and Paymob account credentials, depending on how many methods (cards, wallets, Meeza, Apple Pay, ValU/BNPL) and how many country/website scopes you need. We confirm a firm timeline before starting and keep you updated through sandbox UAT and go-live.

What ongoing support and updates are included after launch?

Every build includes a defined post-launch support window for bug fixes and configuration help. Because the module is built on Magento's service contracts and avoids core rewrites, it upgrades cleanly with minor Magento patches. If Paymob changes its API, or you upgrade across major Magento/Adobe Commerce versions, we offer ongoing maintenance retainers and version-compatibility updates as a follow-on engagement.

Does the integration keep us out of PCI-DSS scope?

Card entry uses Paymob's hosted iframe, so cardholder data is captured by Paymob and never passes through or is stored on your Magento server. This keeps you in the lightest applicable PCI-DSS scope (typically SAQ A). You still complete the appropriate self-assessment, but the integration is designed so sensitive PAN data stays off your infrastructure.

Will it work with a headless / PWA Studio storefront?

Yes. The payment method is exposed through Magento's standard payment service contracts and is compatible with GraphQL and REST, so it works with PWA Studio, custom headless front ends and mobile apps. We tailor the checkout binding to your specific front end during the build.

Can it handle multiple Paymob accounts for different countries?

Yes. Configuration is scope-aware (per website / store view), so you can run separate Paymob accounts and method sets for different MENA markets within one Magento installation. This is set up during the build to match how your settlement and entities are structured.