| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1000 |
| Technical Name |
paypercloud_servipay_pos |
| License | OPL-1 |
| Website | http://www.dphi.be |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1000 |
| Technical Name |
paypercloud_servipay_pos |
| License | OPL-1 |
| Website | http://www.dphi.be |
| Versions | 17.0 18.0 19.0 |
PayperCloud Servipay - Point of Sale (Odoo 19)
This module connects Odoo POS payment terminals to Servipay through PayperCloud API. It extends POS configuration and payment methods so cashier payments can be sent to the physical terminal and tracked until final status.
Main Features
- POS payment terminal provider: Servipay (PayperCloud)
- POS-level configuration for POS ID, Terminal ID and API Key
- Terminal payment flow from POS screen
- Uses base client from module
paypercloud_servipay
Terminal Payment Flow
- Send purchase request
- Poll operation status
- Fetch operation result
- Cancel operation
Requirements
- Odoo 19
- Installed module
paypercloud_servipay - Installed app
point_of_sale - At least one working Servipay terminal
Installation
- Ensure module
paypercloud_servipayis already installed and configured. - Install module PayperCloud Servipay - Point of Sale.
Configuration
- Open Point of Sale > Configuration > Point of Sale.
- Open your POS and fill section Servipay (PayperCloud).
- Open Point of Sale > Configuration > Payment Methods.
- Create or edit a payment method used for terminal payments.
- Set Use a Payment Terminal = Servipay (PayperCloud).
- Attach this payment method to the target POS.
Servipay POS configuration fields:
- Servipay POS ID
- Servipay Terminal ID
- Servipay API Key
If POS API key is set, it is used first. If empty, the system falls back to the global
key from paypercloud_servipay settings.
Usage
- Start a POS session.
- Add products to an order.
- Select the payment method configured with Servipay (PayperCloud).
- Confirm payment request.
- Complete or cancel transaction on physical terminal.
- POS waits for terminal status and updates the payment line accordingly.
Recommended Rollout
- Configure and test in demo/sandbox environment first.
- Validate end-to-end payment/cancel scenarios on one POS.
- Deploy configuration POS by POS in production.
Closing Register - Z-Terminal button
At POS closing, a button Z-Terminal is displayed next to Close Register when Servipay is configured on the POS.
When clicked, it calls Servipay endpoint Create reconciliation for the terminal configured on the current POS.
- Uses Servipay POS ID and Servipay Terminal ID from the POS configuration.
- Uses Servipay API Key from the POS if set, otherwise falls back to global API key.
- Shows a success notification when the request is accepted.
- Shows an error dialog if configuration is missing or Servipay returns an error.
Troubleshooting
- Missing configuration on POS: ensure POS ID and Terminal ID are set on the POS configuration.
- Authorization failures: check POS API key first, then global key fallback.
- No response from terminal: verify terminal connectivity and PayperCloud endpoint access.
- Operation status unclear: check technical logs in
PayperCloud / Servipay > API Logs.
Documentation (FR)
Ce module connecte les terminaux de paiement Odoo POS a Servipay via l'API PayperCloud. Il etend la configuration du POS et les methodes de paiement afin d'envoyer les paiements au terminal physique puis de suivre leur statut jusqu'au resultat final.
Support
Company: DPHI SRL
Contact: cdu@dphi.be
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