| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 2266 |
| Technical Name |
pay_za_payshap |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 2266 |
| Technical Name |
pay_za_payshap |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
South Africa PayShap Connector
BYOK PayShap proxy-pay and BankservAfrica instant-rail ISO 20022 reconciliation for South Africa
Instant proxy payments and bank-feed reconciliation
PayShap is South Africa's real-time low-value payment rail, operated by BankservAfrica under the SARB Rapid Payments Programme (RPP). It runs 24/7 and lets you pay or be paid by ShapID proxy (a registered cellphone number) instead of full bank details. This connector brings the full PayShap workflow into Odoo Accounting: build the ISO 20022 credit transfer, transmit it through your own bank or PSP API with your own credentials (bring-your-own-key), and automatically reconcile the inbound settlement feed against your open customer invoices.
Outbound proxy-pay (pacs.008)
- Pay a beneficiary by ShapID cellphone proxy or by account + 6-digit branch code.
- Generates a standards-correct ISO 20022 pacs.008 FI-to-FI customer credit transfer with the RPP service level and the
PAYSHAPlocal instrument. - South African cellphone numbers are normalised to the canonical
+27MSISDN automatically. - Enforces the published per-transaction scheme ceiling of R50 000.
- Stable end-to-end identifier so retries stay idempotent and status reports reconcile back to the right payment.
Inbound reconciliation (camt.054)
- Import the camt.054 settlement notification your bank/PSP delivers.
- Confidence-scored matching: by end-to-end id, remittance reference, payer ShapID / account, then payer name and exact amount.
- Registers an inbound account.payment against the matched invoice using Odoo's standard reconciliation.
- Scheduled action re-matches open entries and can auto-reconcile high-confidence matches.
- Idempotent ingest â re-importing the same feed never double-books.
Bring-your-own-key, no accreditation required
You stay the registered participant. The connector never bundles a credential or impersonates an accredited integrator: it generates the ISO 20022 message and transmits it through the endpoint and credentials you configure (OAuth2 client credentials, a static bearer token, or an API key). Every secret is stored encrypted-at-rest in your database and protected by the system group; secrets are redacted from the audit trail.
Supported ISO 20022 messages
| Message | Direction | Purpose |
|---|---|---|
| pacs.008 | Outbound | FI-to-FI customer credit transfer â the PayShap proxy-pay we build. |
| pacs.002 | Inbound | Payment status report â accepted / in-process / rejected, with reason code. |
| pacs.004 | Inbound | Payment return â flips a payment to Returned with the ISO return reason. |
| camt.054 | Inbound | Debit/credit settlement notification â the reconciliation feed. |
Built for Odoo 18 and 19
- Community-only dependencies:
base,mail,account. No Enterprise modules required. - Pure-Python ISO 20022 builder and parsers (standard library only) â fully unit-tested.
- Full audit log of every API call, with secrets redacted.
- Multi-company aware, with per-company PayShap connections.
Support
Questions or a feature request? Email gencbaris@outlook.com.tr.
Screenshots
Api Call Log
Connections
Import Settlement
Payments
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