HyperPay Gateway for Magento 2

主な機能

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

Encrypted backend storage of HyperPay entityId and access token via Magento config encryption, scoped per store view

Signed webhook controller that verifies HyperPay notifications and transitions order state through service contracts

Admin ACL resources so payment configuration and refunds respect Magento role permissions

GraphQL and REST checkout exposure so the method works in headless / PWA Studio storefronts, not just Luma

Partial and full refunds driven from Magento creditmemo back to HyperPay's refund endpoint

Configurable per-brand toggles, sandbox vs live mode switch, and order-status mapping in system.xml

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

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).

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.

得られるもの

Custom Magento 2 module (Ecosire_HyperPay) delivered as a composer-installable package with full source under app/code or vendor

Installation and configuration performed by ECOSIRE on your staging and production Magento instance

HyperPay sandbox verification: test transactions across mada, STC Pay, Apple Pay, cards and at least one installment brand

Apple Pay merchant domain verification and certificate setup completed for your domain

Admin configuration guide (system.xml fields, ACL, brand toggles) plus a short merchant operations note

Post-launch warranty window with bug fixes, and an optional support retainer covering Magento minor-version upgrades

これは誰のためのものですか

Saudi retail merchant on Magento

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.

Magento store manager / e-commerce lead

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.

In-house or agency Magento developer

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.

HyperPay Gateway for Magento 2 の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
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	含まれていない	含まれていない	付属	付属

HyperPay Gateway for Magento 2 に関するよくある質問

Is this an instant download from the Adobe Commerce Marketplace?

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.

How long until it is live (delivery / lead time)?

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.

What ongoing support and updates are included?

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.

Does it keep my store PCI-light?

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.

Will it work with a headless / PWA Studio storefront?

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.