HyperPay Payment Gateway for Magento 2

Key Features

HyperPay COPYandPAY hosted widget integration for reduced PCI (SAQ-A) scope, with optional Server-to-Server flow for full checkout control

mada and SADAD support for Saudi domestic debit and bank rails alongside Visa and Mastercard

Apple Pay and STC Pay wallet support wired into the Magento payment method renderer

Tabby and Tamara BNPL routing so eligible carts surface buy-now-pay-later at checkout

Admin-driven captures and refunds (full and partial) from Sales > Orders via gateway command pool, mapped to Magento invoices and credit memos

Clean module under app/code/Ecosire/HyperPay using Magento\Payment adapter, gateway commands, and service contracts — no core overrides

di.xml dependency injection and virtualType command configuration instead of class rewrites

Webhook + synchronous result-query reconciliation that drives Magento order and payment state machine transitions safely

System configuration with granular admin ACL, encrypted credential storage, and per-website/per-store-view config scope

Multi-currency and multi-store handling for SAR and other GCC currencies under standard Magento scope

Sandbox/test entity-id support with environment toggle for staging vs production HyperPay credentials

3-D Secure 2 / OTP redirect handling and order-status mapping for authorized, captured, failed and voided transactions

Structured logging of gateway requests/responses (sensitive fields masked) for reconciliation and dispute support

Compatible with Luma and Hyvä themes; checkout renderer adaptable to PWA Studio / GraphQL on request

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

HyperPay Payment Gateway for Magento 2 is a build-to-order integration that connects your Magento Open Source or Adobe Commerce checkout to HyperPay so GCC shoppers can pay with the methods they actually use: mada, SADAD, Visa, Mastercard, Apple Pay, STC Pay and Tabby/Tamara BNPL routing.

This is not an instant Marketplace download. ECOSIRE builds the module to fit your store — your themes, your checkout (Luma or Hyvä/PWA Studio), your existing payment mix and your HyperPay merchant configuration — then installs it on your environment and supports it. You get a clean module under app/code/Ecosire/HyperPay that follows Magento payment conventions: a Magento\Payment\Model\Method\Adapter gateway command pool, service contracts, di.xml wiring, system configuration with admin ACL, and proper dependency injection rather than core hacks.

We implement HyperPay COPYandPAY (hosted widget) by default for SAQ-A PCI scope, with Server-to-Server available where you need full checkout control. Webhooks and the synchronous result query reconcile order state through Magento's order/invoice lifecycle, and an observer on sales_order_payment_capture-style events keeps the magento ledger and HyperPay in sync. Refunds and captures run from the admin Sales > Orders screen via the gateway capture/refund commands — no console gymnastics.

Multi-store, multi-currency and multi-website setups are handled through Magento's standard config scope, so SAR storefronts and other GCC currencies behave correctly. Everything ships with deployment notes, a UAT pass on your staging environment, and a support window. You own the source; we keep it working against HyperPay and Magento updates.

What you get

Custom Magento 2 module (Ecosire_HyperPay) delivered as source under app/code, with composer-installable packaging on request

Installation and configuration on your staging and production Magento environment by ECOSIRE

HyperPay merchant onboarding assistance — wiring your entity IDs, brands and credentials into Magento system config

UAT test pass on your staging environment covering each enabled payment method and refund/capture flows

Technical handover documentation: configuration guide, payment-method matrix, and admin operating notes

Defined post-launch support window with bug fixes and compatibility maintenance against HyperPay and Magento patch releases

Who this is for

Saudi/GCC Magento merchant

An ecommerce operator on Magento Open Source or Adobe Commerce in KSA/GCC who already has (or is opening) a HyperPay merchant account and needs mada, SADAD and local wallets live at checkout to stop losing domestic shoppers to card-only flows.

Ecommerce / IT manager

The person accountable for checkout uptime and PCI scope who wants a properly engineered, ACL-controlled gateway with admin refunds and clean logs — not a fragile copy-paste integration that breaks on the next Magento upgrade.

Agency or systems integrator

A partner building a GCC client store who needs a maintainable HyperPay module under app/code following Magento payment conventions, delivered to spec with documentation they can support.

How HyperPay Payment Gateway for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
HyperPay mada, SADAD, cards, Apple Pay, STC Pay support out of the box	Included	Partial support	Partial support
Tabby/Tamara BNPL routing wired into checkout	Included	Partial support	Not included
Built, installed and supported on your own Magento environment	Included	Partial support	Not included
Clean app/code module with DI, gateway adapter, no core hacks	Included	Partial support	Partial support
Customised to your theme, checkout and payment mix	Included	Included	Not included
Admin captures and full/partial refunds from Sales > Orders	Included	Partial support	Partial support
Instant self-service download from Adobe Commerce Marketplace	Not included	Not included	Included
Defined post-launch support and Magento/HyperPay compatibility maintenance	Included	Not included	Partial support

Frequently Asked Questions about HyperPay Payment Gateway for Magento 2

How long until the extension is delivered and live on my store?

This is build-to-order, so it is not an instant download. Typical delivery is about 5 to 10 business days from kickoff, depending on which methods you enable (COPYandPAY vs Server-to-Server, BNPL routing, wallets) and your theme. The timeline starts once we have your HyperPay credentials/entity IDs and staging access. We confirm a firm date in writing before we begin and install on your staging environment first for UAT before going to production.

Do I need my own HyperPay merchant account?

Yes. ECOSIRE builds and installs the Magento integration; the commercial HyperPay merchant account, entity IDs and brand enablement (mada, SADAD, Apple Pay, STC Pay, Tabby/Tamara) are contracted between you and HyperPay. We assist with wiring those credentials into Magento and validating each enabled method during UAT.

What ongoing support and updates are included?

Every build includes a defined post-launch support window covering bug fixes and compatibility maintenance. If a HyperPay API change or a Magento security/patch release affects the integration, we update the module within that window. After it ends, you can extend support or request changes on a per-engagement basis. You own the source code, so you are never locked in.

COPYandPAY or Server-to-Server — which do you implement?

We default to HyperPay COPYandPAY (the hosted widget) because it keeps your store in SAQ-A PCI scope while still rendering inside your Magento checkout. If you need full control over the payment form or specific UX, we implement the Server-to-Server flow instead, which carries a higher PCI obligation. We will recommend the right one for your compliance posture during scoping.

Will it survive Magento and theme upgrades?

Yes — that is the point of building it properly. The module lives under app/code/Ecosire/HyperPay and uses dependency injection (di.xml), the Magento payment adapter and gateway command pool, service contracts, observers and admin ACL. There are no core file rewrites, so it upgrades cleanly. It supports Luma and Hyvä, and we can adapt the checkout renderer for PWA Studio / GraphQL on request.