Embedded HyperPay COPYandPAY checkout for Odoo — mada, Apple Pay, STC Pay, 3DS2 — built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
应用清单
围绕您的工作流程构建
Embedded HyperPay COPYandPAY checkout for Odoo — mada, Apple Pay, STC Pay, 3DS2 — built, installed and supported by ECOSIRE.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Odoo 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
This is a build-to-order Odoo payment provider that ECOSIRE designs, builds, installs and supports for your specific HyperPay account and Odoo version — it is not an off-the-shelf instant download. Your buyers complete payment inside your own Odoo checkout using HyperPay's COPYandPAY embedded widget, so they never bounce to a hosted page and abandon the cart. We extend Odoo's native payment.provider and payment.transaction models with a dedicated HyperPay implementation that speaks HyperPay's REST API: the module prepares a checkout, renders the COPYandPAY brand widget through a QWeb-templated payment form, and on return queries the payment status so every order state in Odoo reflects the real result at HyperPay.
Under the hood we ship a clean, upgrade-safe addon: a proper __manifest__.py declaring dependencies on payment, sale and (where relevant) website_sale; Python models extending models.Model with the entity, access-token and secrets fields; @api.depends computes and constraints where they add safety; access control via ir.model.access.csv plus record rules so only authorized users touch credentials; XML/OWL views and settings screens for configuration; and a signed webhook controller for asynchronous notifications. We wire mada, Visa, Mastercard, Apple Pay and STC Pay through the correct HyperPay entity IDs, enforce 3DS2 / SCA where the card and issuer require it, and reconcile every transaction with both the webhook and an active status-query fallback so a dropped callback never leaves an order stuck.
Because it is a genuine payment.provider extension, the gateway works across Odoo eCommerce (website_sale), the customer portal invoice-payment flow, and Sales Orders — the same journal entries, provider states (draft / pending / authorized / done / cancel / error) and reconciliation you already understand. It runs on Odoo 17, 18 and 19, on Community or Enterprise, and is delivered as versioned source you own. ECOSIRE handles the HyperPay onboarding specifics — entity-per-brand setup, test vs live BASE_URL, IP allow-listing and webhook signing — and hardens it for production before handover.
A KSA or GCC retailer running Odoo eCommerce who already has (or is opening) a HyperPay account and needs mada, cards and local wallets accepted directly inside their storefront without redirecting shoppers to a hosted page.
Owns reconciliation and month-end close. Needs every HyperPay transaction to map cleanly to Odoo journal entries, invoices and refunds, with a reliable audit trail even when a webhook is delayed or dropped.
Responsible for a stable, upgrade-safe deployment. Wants a properly structured addon with real access control, sandbox testing, and someone who handles the HyperPay onboarding and security hardening rather than a risky DIY provider.
Focused on conversion and checkout completion. Values the embedded COPYandPAY flow, Apple Pay and STC Pay to reduce cart abandonment and serve the way Gulf customers actually prefer to pay.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Embedded COPYandPAY checkout (no redirect) | 包含 | Possible but you build and debug the widget integration yourself | Often a hosted-page redirect; embedded widget varies by vendor | |
| mada, Apple Pay & STC Pay via correct entity IDs | 包含 | You must research and wire each HyperPay entity | Sometimes; coverage depends on the specific listing | |
| 3DS2 / SCA handling | 包含 | Your responsibility to implement and test | Usually, if the module is maintained | |
| Dual reconciliation (webhook + status query) | 包含 | Rarely built — most DIY relies on webhook only | Webhook only in many modules | |
| Entity-per-brand configuration | 包含 | Buildable but adds significant scope | Not commonly exposed | |
| Built, installed & configured for your account | 包含 | You do all setup and HyperPay onboarding | 不包括在内 | |
| Runs on Odoo 17, 18 and 19 (Community or Enterprise) | 包含 | Depends on how you scope it | Varies; often locked to specific versions | |
| Named support window, training & documentation | 包含 | 不包括在内 | Vendor-dependent, often ticket-only |
No. This is a build-to-order module. ECOSIRE builds, installs and configures the HyperPay gateway specifically for your Odoo version and your HyperPay account — it is not a pre-packaged instant download and we never claim otherwise.
Typical lead time is 2 to 4 weeks from purchase, depending on your Odoo version, the payment methods and HyperPay entities you enable, and access to your staging environment and HyperPay credentials. We install on staging first, run a full test-order pass, then cut over to production.
Handover includes documentation, a training session and a defined post-launch support window for fixes and questions. Because you receive versioned source that extends Odoo's native payment framework, the module is upgrade-safe across Odoo 17, 18 and 19; we can quote ongoing maintenance or an Odoo-version migration separately when you need it.
No. The module uses HyperPay's COPYandPAY embedded widget rendered inside your Odoo checkout via a QWeb template, so shoppers complete payment on your own page. This avoids the redirect-and-abandon drop-off common with hosted payment pages.
mada, Visa, Mastercard, Apple Pay and STC Pay, each routed through the correct HyperPay entity ID, with 3DS2 / SCA challenge and frictionless flows handled per issuer and card scheme.
The module reconciles every transaction two ways: a signed asynchronous webhook and an active status-query fallback against HyperPay. If a callback is dropped, the status query resolves the real outcome so an order is never left stuck in a pending state.
Yes. It is a genuine payment.provider extension, so it works on both Community and Enterprise and across website_sale eCommerce, Sales Order payment links, and the customer portal invoice-payment flow on Odoo 17, 18 and 19.
Embedded HyperPay COPYandPAY checkout for Odoo — mada, Apple Pay, STC Pay, 3DS2 — built, installed and supported by ECOSIRE.