Quick facts
- Price
- $249.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 20160 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
HyperPay Payment Gateway for Odoo
Embedded HyperPay COPYandPAY checkout for Odoo — mada, Apple Pay, STC Pay, 3DS2 — built, installed and supported by ECOSIRE.
$249.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
COPYandPAY embedded widget rendered inside your Odoo checkout via QWeb so shoppers pay without leaving the page or hitting a redirect-abandonment drop-off
Full Gulf payment-method coverage: mada, Visa, Mastercard, Apple Pay and STC Pay, each mapped to the correct HyperPay entity ID
3DS2 / SCA challenge handling with automatic step-up and frictionless flows honored per issuer and card scheme
Entity-per-brand configuration so mada, cards and wallets can route through separate HyperPay entities from one Odoo provider record
Dual reconciliation: signed asynchronous webhook plus an active status-query fallback so a missed callback never strands an order
Native extension of Odoo's payment.provider and payment.transaction models — real provider states (draft, pending, authorized, done, cancel, error) drive order and invoice flow
Works across website_sale eCommerce, the customer portal invoice-payment flow, and Sales Order payment links
Test-mode and live-mode switching with separate BASE_URL, access tokens and entity IDs, so you validate in sandbox before go-live
Secure credential storage: HyperPay access token and entity secrets held in restricted fields, never exposed in logs or client-side widget config
Access control via ir.model.access.csv and record rules so only finance/admin roles can read or edit gateway credentials
Configurable capture behaviour (auto-capture vs authorize-then-capture) aligned to your operational and refund policy
Refund and partial-refund support driven from Odoo, posting the reversal transaction back to HyperPay and updating the linked invoice
Idempotent webhook controller with signature verification to reject spoofed or replayed notifications
Arabic and English customer-facing labels on the payment form for KSA/Gulf shoppers
Optional XML-RPC / JSON-RPC exposure of transaction status so external systems or your ERP integrations can query payment outcomes
Detailed transaction logging and a payment-status audit trail for finance reconciliation and dispute handling
About this Product
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.
Why Choose HyperPay Payment Gateway for Odoo
COPYandPAY embedded widget rendered inside your Odoo checkout via QWeb so shoppers pay without leaving the page or hitting a redirect-abandonment drop-off
Full Gulf payment-method coverage: mada, Visa, Mastercard, Apple Pay and STC Pay, each mapped to the correct HyperPay entity ID
3DS2 / SCA challenge handling with automatic step-up and frictionless flows honored per issuer and card scheme
Entity-per-brand configuration so mada, cards and wallets can route through separate HyperPay entities from one Odoo provider record
Dual reconciliation: signed asynchronous webhook plus an active status-query fallback so a missed callback never strands an order
Native extension of Odoo's payment.provider and payment.transaction models — real provider states (draft, pending, authorized, done, cancel, error) drive order and invoice flow
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.
What you get
- Complete, version-controlled Odoo addon source (the HyperPay payment.provider module) that you own, targeted to your Odoo 17, 18 or 19 edition
- Installation and deployment on your environment (staging first, then production) including addons-path wiring and module upgrade
- Configured HyperPay entities for your enabled methods (mada, cards, Apple Pay, STC Pay) with test-to-live cutover
- Signed-webhook endpoint set up and validated against your HyperPay dashboard, plus status-query reconciliation verified end to end
- Security review of credential storage, ir.model.access.csv rules and record rules before handover
- Configuration and admin documentation (how to switch modes, add an entity, read the transaction log, issue refunds)
- A live end-to-end test pass: a real sandbox order paid via COPYandPAY, reconciled, and refunded, demonstrated with your team
- Admin/finance training session and a defined post-launch support window for fixes and questions
Who this is for
Saudi/Gulf online merchant on HyperPay
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.
Finance / accounting lead
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.
Odoo administrator or IT manager
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.
eCommerce / operations manager
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.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the HyperPay Payment Gateway for Odoo module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for HyperPay Payment Gateway for Odoo, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How HyperPay Payment Gateway for Odoo Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| 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 |
Frequently Asked Questions about HyperPay Payment Gateway for Odoo
+Is this an instant download from the Odoo App Store?
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.
+How long does delivery take?
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.
+What support and updates are included?
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.
+Do customers leave my site to pay?
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.
+Which payment methods and security standards are supported?
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.
+What happens if a webhook is missed or delayed?
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.
+Does it work with Odoo Community, and with the customer portal?
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.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
Related Modules
Request a quote
HyperPay Payment Gateway for Odoo
Embedded HyperPay COPYandPAY checkout for Odoo — mada, Apple Pay, STC Pay, 3DS2 — built, installed and supported by ECOSIRE.
- COPYandPAY embedded widget rendered inside your Odoo checkout via QWeb so shoppers pay without leaving the page or hitting a redirect-abandonment drop-off
- Full Gulf payment-method coverage: mada, Visa, Mastercard, Apple Pay and STC Pay, each mapped to the correct HyperPay entity ID
- 3DS2 / SCA challenge handling with automatic step-up and frictionless flows honored per issuer and card scheme
- Entity-per-brand configuration so mada, cards and wallets can route through separate HyperPay entities from one Odoo provider record