HyperPay POS Payment | Odoo Point of Sale Card Gateway | OPPWA Scan to Pay | MADA Visa Mastercard
by CODEerts https://www.codeerts.com$ 99.00
In-App PurchasesHyperPay POS Payment
Take HyperPay (OPPWA) card payments at the counter.
Scan to pay by MADA, Visa and Mastercard. No terminal hardware.
The cashier taps HyperPay, the POS shows a QR, the customer pays on their phone, and the order validates automatically.
|
3
Card Brands
|
Scan
To Pay
|
0
Terminals Needed
|
Refunds
From the POS
|
v19
Compatible
|
The counter-payment problem every Gulf shop knows
|
Shoppers want to pay by card
Cash-only at the till loses sales. Customers expect to tap MADA, Visa or Mastercard, and a POS that cannot take cards feels dated. |
Card terminals cost and break
Buying, renting and maintaining a physical terminal for every register is expensive, and a broken device stops you taking payment. |
Was the payment really made?
Marking an order paid without the gateway confirming it is a risk. You need HyperPay itself to confirm the exact amount before the sale closes. |
What this module does
HyperPay POS Payment adds HyperPay (OPPWA) as a Point of Sale payment method with a scan-to-pay flow. The cashier taps HyperPay, the POS creates a HyperPay checkout, and a QR code and link appear on screen for the customer to scan with their phone.
The customer pays by MADA, Visa or Mastercard on HyperPay's secure page. The POS confirms the payment with a server-side status check and validates the order automatically. No card terminal is needed, and POS refunds are sent straight back to HyperPay.
|
📱
Scan to pay, no hardware
The POS shows a QR the customer scans with their phone and pays by card. No terminal to buy, rent or maintain. |
🔒
Confirmed, then validated
The payment is confirmed by a server-side check against HyperPay, then the POS order validates automatically the moment it is complete. |
🔄
Refunds from the POS
Process a POS refund paid back with HyperPay and the module sends the refund to HyperPay against the original payment. |
|
💳 MADA, Visa & Mastercard
One provider takes local MADA cards alongside Visa and Mastercard, so shoppers at the till pay the way they prefer. |
📱 Scan-to-pay QR and link
The cashier screen shows a QR code and an Open payment page link, so the customer can pay from their own phone. |
|
🖥 Customer display mirror
The QR also appears on the POS customer display where your Odoo version supports it, so the shopper can scan without turning the screen. |
✅ Server-verified status
The POS confirms the payment with a server-side check before the line is marked done, so a closed tab alone can never mark a sale paid. |
|
🧾 Refunds sent to HyperPay
A POS refund paid with HyperPay is sent to HyperPay against the original payment, so returns are handled in the same flow. |
🧪 Test and live modes
Keep Test Mode on to trial with your HyperPay sandbox credentials, then switch it off to go live. No code change needed. |
|
🛡 System-only credentials
Your HyperPay Entity ID and Access Token are stored as system-only fields, hidden from ordinary POS users. |
🧩 Self-contained
Depends only on Point of Sale. It has its own HyperPay credentials and does not need the HyperPay website payment provider. |
What you get
|
💳
MADA
Local card scheme |
🌐
Visa & Mastercard
International cards |
📱
Scan to Pay
QR on screen |
🔒
Verified
Server-side check |
|
🧾
Refunds
Back to HyperPay |
🖥
Customer Display
Where supported |
🧪
Sandbox
Test then go live |
🛡
Secure keys
System-only fields |
Screenshots
See it in action, from setup to a validated POS order.
Add HyperPay as the integration on a POS payment method, then enter your Entity ID and Access Token and keep Test Mode on.
HyperPay appears as a normal Point of Sale payment method, right beside cash and bank.
The cashier taps HyperPay and the POS shows a QR code, an amount and an Open payment page link for the customer to scan.
The customer scans the QR and pays by MADA, Visa or Mastercard on HyperPay's secure page.
The POS confirms the payment server-side and validates the order automatically, then the customer returns the device to the cashier.
How it works
1 |
Add HyperPay to a POS payment method
Create or open a Point of Sale payment method, set the integration to HyperPay, and enter your Entity ID and Access Token. |
2 |
Add it to your registers
Assign the HyperPay method to the Point of Sale configurations that should accept cards, then open a session. |
3 |
The customer scans and pays
At checkout the cashier taps HyperPay, the POS shows a QR, and the shopper pays by card on HyperPay's page from their phone. |
4 |
The POS confirms and validates
The module confirms the payment with a server-side check against HyperPay and validates the order the moment it is complete. |
5 |
Refund when you need to
Process a POS refund paid back with HyperPay and the module sends the refund to HyperPay against the original payment. |
Technical information
|
Version
19.0
|
License
OPL-1
|
Editions
Community & Enterprise
|
Dependencies
point_of_sale
|
Technical name: codeerts_pos_hyperpay · Gateway: HyperPay (OPPWA)
Frequently asked questions
The cashier taps the HyperPay payment method and the POS shows a QR code and a link. The customer scans it with their phone, pays by card on HyperPay's secure page, and the POS confirms the payment and validates the order automatically. No card terminal hardware is needed.
Yes. The HyperPay payment page is configured for MADA, Visa and Mastercard, so shoppers in Saudi Arabia and the Gulf can pay with their local MADA cards as well as international cards.
No. Payment happens on the customer's own phone through HyperPay's hosted page, so you do not need a physical card terminal. The cashier only needs to show the QR code.
The module confirms every payment with a server-side status check against HyperPay before the payment line is marked done, then validates the order. A returning browser alone can never confirm a payment, and the status endpoint is never over-polled.
Yes. When you process a POS refund paid back with the HyperPay method, the module sends the refund request to HyperPay against the original payment.
Yes. HyperPay POS Payment is self-contained and depends only on Point of Sale. It has its own HyperPay credentials and does not require the HyperPay website payment provider.
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
|
90+
Published Apps
|
More from CODEerts
Other apps we build to make Odoo do more. Tap any card to open it on the Odoo Apps Store.
 FREE Archive Anything |  FREE Transaction Flow Visualizer |  FREE Smart Mail Rebrand |  FREE Duplicate Record Detector |
 AI Dashboard Builder |  Advance Payment Pro |  Dual Book & Tax Depreciation |  Smart Duplicate Detector |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 636 |
| Technical Name |
codeerts_pos_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