| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 607 |
| Technical Name |
paypercloud_servipay |
| License | OPL-1 |
| Website | http://www.dphi.be |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 607 |
| Technical Name |
paypercloud_servipay |
| License | OPL-1 |
| Website | http://www.dphi.be |
| Versions | 17.0 18.0 19.0 |
PayperCloud / Servipay - API Tools (Odoo 19)
This module provides the technical base integration with PayperCloud / Servipay. It is designed to be used as a foundation for POS and accounting flows.
Overview
- Global API configuration
- API call tester wizard
- Operations history
- API request/response logs
Main Features
- Central settings for PayperCloud API access
- Support for API v2 endpoints
- Full API logging with metadata and optional payload bodies
- Operation records for traceability
Supported API v2 Endpoints
- Purchase
- Refund
- Void
- Reconciliation
- Operation status
- Operation result
- Operation cancel
- Operations list (daily/weekly)
- Last reconciliation
Requirements
- Odoo 19
- Valid PayperCloud / Servipay credentials
- Network access from Odoo server to PayperCloud API
Installation
- Copy module
paypercloud_servipayin your addons path. - Update Apps list.
- Install module PayperCloud / Servipay - API Tools.
Configuration
Open PayperCloud / Servipay > Configuration and fill:
- PayperCloud Base URL: demo or production endpoint.
- POS ID (posId / pos_pid): default POS identifier.
- POS API Key: global API key used as Bearer token.
- Default Terminal PID (pid / tpe_pid): default terminal identifier.
- HTTP Timeout (seconds).
- Verify SSL Certificates: keep enabled in production.
- Log Request/Response Bodies: disable only if payload content should not be stored in logs.
Usage
- Open
PayperCloud / Servipay > API Tester. - Select endpoint and fill required fields.
- Click Call API.
- Check response and, if relevant, open created operation.
Monitoring
PayperCloud / Servipay > Operations: business operation tracking.PayperCloud / Servipay > API Logs: technical call diagnostics.
Notes
- This module stores a global API key.
- If
paypercloud_servipay_posis installed, a POS-specific API key can override the global key.
Troubleshooting
- Authentication errors: verify API key and base URL.
- Timeouts: increase timeout and verify network/firewall.
- SSL errors: keep SSL verification enabled in production and install proper certificates.
- Unexpected API behavior: review API Logs and raw response payload.
Documentation (FR)
Ce module fournit la base technique d'integration avec PayperCloud / Servipay : configuration API globale, assistant de test, historique des operations et journaux des requetes/reponses API.
Il sert de socle pour les flux POS et comptables, avec parametrage centralise des acces API PayperCloud et tracabilite complete des operations.
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