A KSA-focused HyperPay payment gateway for Magento 2 / Adobe Commerce, integrating mada, STC Pay, Apple Pay and Tamara/Tabby installments through HyperPay's COPYandPAY hosted widget. Built to order, installed and supported on your store by ECOSIRE. One-time license from $249.00 USD for Magento 2 / Adobe Commerce (build-to-order) — includes 12 months of updates and support.

A KSA-focused HyperPay payment gateway for Magento 2 / Adobe Commerce, integrating mada, STC Pay, Apple Pay and Tamara/Tabby installments through HyperPay's COPYandPAY hosted widget. Built to order, installed and supported on your store by ECOSIRE.
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
HyperPay Gateway for Magento 2 brings KSA-native payments to Saudi retail merchants who need real mada and STC Pay coverage alongside Apple Pay, cards and Tamara/Tabby installments — all routed through HyperPay's COPYandPAY hosted widget so card data never touches your Magento server (PCI-light, SAQ A scope).
mada local debit scheme support with correct brand routing through HyperPay COPYandPAY
STC Pay wallet exposed as a selectable Magento payment brand at checkout
Apple Pay integration including merchant domain verification and the Apple Pay JS session handshake
Tamara and Tabby buy-now-pay-later installment routing surfaced as distinct checkout options
VISA and MASTERCARD card payments via the same hosted COPYandPAY widget (no PAN on your server)
Magento Payment Gateway Command framework: authorize, capture, sale, void and refund command pools wired in di.xml
This is not an instant Adobe Commerce Marketplace download. ECOSIRE builds the module to order, then installs and supports it on your specific Magento Open Source or Adobe Commerce instance. You get a clean composer package under app/code/Ecosire/HyperPay (or vendor-installed), wired through Magento's Payment Method Facade and Gateway Command framework — di.xml command pools, ValueHandlerPool, request/response builders and a ClientInterface calling HyperPay's /v1/checkouts and payment-status endpoints over server-to-server HTTPS.
Implementation respects Magento conventions end to end: system.xml config under Stores → Configuration → Sales → Payment Methods (test/live entityId, access token via encrypted backend model), admin ACL resources, per-store-view scope, and brand-level toggles so you can enable mada, STC Pay, Apple Pay, VISA/MASTER and installment brands independently. Webhooks land on a custom controller that verifies the HyperPay signature and updates order state via service contracts, with an observer on sales_order_payment_capture for reconciliation. The method appears in both Luma checkout and the GraphQL/REST APIs, so headless (PWA Studio) storefronts work too.
We handle the full lifecycle: HyperPay merchant onboarding fields, sandbox verification with test entityIds, capture/authorize/refund flows, partial refunds via creditmemo, and Apple Pay domain verification. Honest delivery: a working, tested build is delivered and installed within the lead time below, with a warranty window and an optional support retainer for Magento upgrades.
A KSA-based store owner who is losing checkout conversions because mada and STC Pay are not available, and needs a compliant, locally-trusted payment experience without rebuilding their store.
Owns checkout conversion and wants Apple Pay plus Tamara/Tabby installments offered cleanly, with brand-level control over which methods show, and reliable order-status updates after payment.
Will maintain the store long-term and wants a properly structured module that follows the Payment Gateway Command framework, di.xml, ACL and service contracts — not a hacked-in observer that breaks on upgrade.
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden HyperPay Gateway for Magento 2 modülünün ZIP dosyasını indirin.
ZIP'i sunucudaki Odoo özel eklentiler klasörünüze çıkarın (veya Uygulamalar > Odoo.sh / runbot'taki dosyadan yükle yoluyla yükleyin).
Geliştirici Modunu etkinleştirin, Uygulamalar'ı açın, Uygulama Listesini Güncelle'ye tıklayın, HyperPay Gateway for Magento 2'i arayın ve Yükle'ye basın.
Yeni menüyü açın, ECOSIRE lisans anahtarınızı yapıştırın, tüm harici kimlik bilgilerini (Shopify, Amazon, Stripe vb.) bağlayın ve kaydedin.
Yerleşik bağlantı testini çalıştırın, ilk 10 kaydınızı senkronize edin ve yinelenen cronu planlayın. Herhangi bir sorun olursa desteğe başvurun.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| mada + STC Pay native KSA methods | ||||
| Apple Pay with domain verification handled for you | ||||
| Tamara / Tabby installment routing | ||||
| Built specifically for your store and installed by the vendor | ||||
| PCI-light via COPYandPAY hosted widget (SAQ A) | ||||
| Follows Payment Gateway Command framework (di.xml, service contracts, ACL) | ||||
| GraphQL / REST exposure for headless storefronts | ||||
| Full source ownership, no per-transaction vendor fee | ||||
| Instant self-service download |
No. This is a build-to-order extension. ECOSIRE builds the HyperPay module specifically for your Magento Open Source or Adobe Commerce instance, then installs and configures it for you. There is no instant Marketplace download — you get a tested, working integration on your actual store.
Typical delivery is about 5 to 10 business days from receiving your HyperPay merchant credentials and staging access. The build, HyperPay sandbox verification, Apple Pay domain setup and production install all happen within that window. Complex multi-store or headless setups can add a few days, which we confirm in writing before starting.
Every build includes a warranty window for bug fixes after go-live. Beyond that, an optional support retainer covers Magento minor-version compatibility, HyperPay API changes, and adding new payment brands. Because you own the full module source, any Magento developer can also maintain it — there is no license lock-in or per-transaction fee from ECOSIRE.
Yes. It uses HyperPay's COPYandPAY hosted widget, so card data is entered in HyperPay-hosted fields and never touches your Magento server. This typically keeps you in the reduced SAQ A PCI scope. We confirm your exact PCI obligations with you, but the integration is designed specifically to avoid handling raw PAN data.
Yes. The payment method is exposed through Magento's service contracts and the GraphQL/REST checkout APIs, not only the Luma frontend, so it can be consumed by PWA Studio or a custom headless storefront. If you are headless, tell us up front so the build includes the GraphQL resolvers and client-side widget mounting for your frontend.
A KSA-focused HyperPay payment gateway for Magento 2 / Adobe Commerce, integrating mada, STC Pay, Apple Pay and Tamara/Tabby installments through HyperPay's COPYandPAY hosted widget. Built to order, installed and supported on your store by ECOSIRE.