HyperPay Payment Gateway | Odoo OPPWA Copy&Pay | MADA Visa Mastercard
by CODEerts https://www.codeerts.com$ 99.00
HyperPay Payment Gateway
Accept HyperPay (OPPWA) card payments inside Odoo.
MADA, Visa and Mastercard, confirmed by a server-side check.
Customers pay with the Copy&Pay widget on your own payment page. No external redirect. Refunds handled in the same place.
|
3
Card Brands
|
Copy&Pay
Inline Widget
|
100%
Server-Verified
|
Refunds
Full & Partial
|
v19
Compatible
|
The payment problem every Gulf merchant knows
|
MADA is not optional
Most local shoppers pay with MADA. A checkout that only takes international cards quietly loses those orders at the last step. |
Redirects lose customers
Bouncing the buyer to a separate payment site breaks trust and drops conversion. You want them to pay on your own page. |
Can you trust the confirmation?
A payment marked paid only because the browser came back is a risk. You need the gateway itself to confirm the exact amount. |
What this module does
HyperPay Payment Gateway connects your Odoo checkout to HyperPay (OPPWA) using the Copy&Pay payment widget. Customers pay by MADA, Visa or Mastercard right on your Odoo payment page, with no redirect to an external screen.
After the card is submitted, the module runs a server-to-server status check against HyperPay and only marks the order paid when the confirmed amount, currency and reference match. Issue full or partial refunds straight from the transaction, and switch between sandbox and live by changing the provider state.
|
💳
Pay on your own page
The HyperPay Copy&Pay widget loads inline in the Odoo payment page. Buyers enter their card and pay without leaving your checkout. |
🔒
Server-verified payments
Every payment is confirmed by a direct request to HyperPay. The amount, currency and reference must match the order before it is marked paid. |
🔄
Refunds from Odoo
Refund a full or partial amount straight from the confirmed transaction. The module sends the refund to HyperPay and records it against the original payment. |
|
💳 MADA, Visa & Mastercard
One provider accepts local MADA cards alongside Visa and Mastercard, so Gulf shoppers pay the way they prefer. |
🖥 Inline Copy&Pay checkout
The payment widget renders inside the Odoo payment page, keeping the buyer on your site through the whole flow. |
|
✅ Amount and reference matched
The server-side check compares the confirmed amount, currency and reference with the order, so a browser return alone cannot confirm a payment. |
🧾 Refunds against the payment
Full or partial refunds are sent to HyperPay and recorded as a refund transaction linked to the original payment. |
|
🧪 Test and live modes
Set the provider to Test to use the HyperPay sandbox endpoint, then switch to Enabled for production. No code change needed. |
🛡 System-only credentials
Your Entity ID and Access Token are stored as system-only fields, hidden from ordinary users on the provider record. |
|
🔗 Return URL and webhook
Both the browser return and the HyperPay webhook trigger the same verified status check, so payment status resolves reliably. |
🧾 Posts a real Odoo payment
A confirmed payment posts an account payment on your bank journal and reconciles the invoice, so it is marked Paid automatically. Fits eCommerce, sales orders and invoice payment links. |
What you get
|
💳
MADA
Local card scheme |
🌐
Visa & Mastercard
International cards |
🖥
Copy&Pay
Inline widget |
🔒
Verified
Server-side check |
|
🧾
Refunds
Full or partial |
🧪
Sandbox
Test then go live |
🔗
Webhook
Reliable status |
🛡
Secure keys
System-only fields |
Screenshots
See it in action, from setup to a reconciled, paid invoice.
Enter your Entity ID and Access Token, then choose Test or Live. No code.
Offer the cards your Gulf shoppers actually use, from a single provider.
The card form loads right in the Odoo payment page. No redirect to an external site.
The amount, currency and reference are matched against the order, then the transaction is confirmed.
Each confirmed payment posts an account payment on your bank journal, ready to reconcile.
The payment is linked to the invoice and reconciled, with the full trail in the chatter.
Search and audit all HyperPay payments and refunds in one list.
Refund the full amount or part of it straight from the transaction.
How it works
1 |
Add HyperPay as a provider
In Payment Providers, open HyperPay and enter your Entity ID and Access Token on the Credentials tab. |
2 |
Choose test or live
Set the state to Test for the HyperPay sandbox, or Enabled for production. Publish the provider. |
3 |
Customer pays with Copy&Pay
At checkout the buyer picks HyperPay and pays by MADA, Visa or Mastercard in the widget on your payment page. |
4 |
The payment is verified
The module asks HyperPay for the payment status and marks the order paid only when the amount, currency and reference match. |
5 |
Refund when you need to
Open the confirmed transaction and click Refund for the full amount or a partial amount. The refund is sent to HyperPay and recorded. |
Technical information
|
Version
19.0
|
License
OPL-1
|
Editions
Community & Enterprise
|
Dependencies
payment (core)
|
Technical name: codeerts_payment_hyperpay · Gateway: HyperPay (OPPWA) Copy&Pay
Frequently asked questions
Add HyperPay as a payment provider, enter your Entity ID and Access Token, and enable it. Customers then see the HyperPay Copy&Pay widget on the Odoo payment page and pay by card without leaving your checkout.
Yes. The Copy&Pay widget is configured for MADA, Visa and Mastercard, so Saudi shoppers can pay with their local MADA cards alongside international cards.
Every payment is confirmed by a server-to-server status request to HyperPay. The returned amount, currency and merchant reference must match the order before it is marked paid, so a browser return alone can never confirm a payment.
Yes. Open the confirmed transaction and click Refund. You can refund the full amount or a partial amount, and the module sends the refund request to HyperPay and records the refund transaction against the original payment.
Yes. Set the provider to Test to use the HyperPay sandbox endpoint with your test credentials, then switch to Enabled to go live on the production endpoint. No code change is needed.
Yes. When a payment is confirmed, Odoo posts an account payment on the provider's bank journal and reconciles it against the related invoice, so the invoice is marked Paid automatically with the payment and transaction linked on it.
Use the version selector at the top of this page to pick your Odoo release. Each Odoo Apps Store listing installs the build that matches that version, on both Community and Enterprise.
The team behind this module
About CODEerts
Full-Service Odoo ERP Agency · Solutions That Scale
Every module in our store is built from real client work, tested in production and maintained long-term by a team of Odoo certified consultants. When you need more than an app, we deliver the full solution.
|
🏗️ Implementation
Full Odoo roll-outs from requirements to go-live, across any industry and company size. |
🧩 Custom Development
Bespoke modules, OWL components and business logic built precisely to your workflow. |
🔄 Migrations
Zero-data-loss upgrades from older Odoo versions with full custom module porting. |
|
🔌 Integrations
Payment gateways, shipping carriers, biometric devices, eCommerce and third-party APIs. |
🔍 Odoo Audits
Performance, security and code-quality reviews that surface risks before they become problems. |
🧑💻 Support & Training
Ongoing helpdesk, user training and monthly retainers so your team stays productive. |
|
Odoo
Certified
|
6+
Years
|
50+
Projects
|
10+
Industries
|
40+
Published Apps
|
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 392 |
| Technical Name |
codeerts_payment_hyperpay |
| License | OPL-1 |
| Website | https://www.codeerts.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module