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.

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.

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.

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.

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.