| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 376 |
| Technical Name |
payment_yoco_bq |
| License | See License tab |
| Website | https://sebenz.co.za |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 376 |
| Technical Name |
payment_yoco_bq |
| License | See License tab |
| Website | https://sebenz.co.za |
Yoco Payment Provider
Accept Visa, Mastercard & Amex in South Africa — hosted checkout, no PCI burden
Connect your Odoo 19 store to Yoco's hosted checkout — South Africa's leading card payment gateway. Customers pay on Yoco's secure, PCI-compliant page and are returned to Odoo automatically. No card data ever passes through your server.
What you get
💳 Hosted Checkout
Yoco creates a secure, branded payment page. Zero PCI-DSS scope on your side — your server never sees raw card data.
🔒 Signed Webhooks
Every payment confirmation is verified with HMAC-SHA256 before Odoo marks the order as paid. Replay attacks are rejected with a 3-minute timestamp window.
↩ Full Refunds
Issue full refunds directly from Odoo's accounting module. The refund is sent to Yoco's API in one click and reconciled automatically.
🔑 Separate Test & Live Keys
Store test and live API keys independently. Switching modes never overwrites the other set of credentials — safe to go live without reconfiguring.
🔌 Auto Webhook Setup
Click Connect Webhook and the module registers the webhook URL with Yoco and stores the signing secret automatically — no copy-pasting from the Yoco dashboard.
🌍 ZAR Only
Yoco only processes South African Rand. The provider is hidden automatically for any other currency — your customers outside ZAR are never affected.
Setup
Go to Accounting → Configuration → Payment Providers → Yoco.
Paste your Live Public Key and Live Secret Key from the Yoco Developer Console. For testing, fill in the Test Public Key and Test Secret Key and set the provider state to Test Mode.
Click Connect Webhook — the module calls Yoco's API, registers your server's webhook URL, and stores the signing secret. No manual configuration needed.
Set the provider state to Enabled. Yoco will appear as a payment method at checkout for all ZAR transactions.
Technical details
| Item | Detail |
|---|---|
| Odoo versions | 19.0 Community & Enterprise |
| Dependencies | payment, account |
| Currency | ZAR only (auto-hidden for other currencies) |
| Checkout API | POST https://payments.yoco.com/api/checkouts |
| Refund API | POST https://payments.yoco.com/api/checkouts/{id}/refund |
| Webhook endpoint | POST /payment/yoco/webhook |
| Signature algorithm | HMAC-SHA256 with replay-attack protection (3 min window) |
| Idempotency | UUID Idempotency-Key on every API call |
| Tokenisation | Not supported (Yoco hosted checkout only) |
Published by Bitquanta — sebenz.co.za — support@sebenz.co.za
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