Skipcash Payment Gateway Integration for South Africa

Introduction

We design and implement secure, scalable payment gateway integrations that connect merchants’ frontends (eCommerce, mobile apps, POS) with ERP systems (Odoo) and payment processors. Using Adyen and SkipCash as worked examples, this case study demonstrates how we deliver:

Multi-method checkout (cards, wallets, local schemes)
PCI-safe tokenization and vaulting
Pay-by-Link and QR-code flows for POS and remote sales
Automatic reconciliation inside Odoo to improve conversion rates and operational efficiency

(References: Odoo, Adyen, SkipCash)

Challenges (common across projects)

Wide payment-method coverage: support global cards, Apple/Google Pay, plus local options.
Multiple touch-points: eCommerce checkout, mobile apps, in-store POS, and remote sales (phone / delivery).
Security & compliance: tokenization, secure webhooks, PCI-DSS requirements.
Tight ERP sync: real-time posting to Odoo orders/invoices and automated reconciliation.
UX expectations: one-click repeat purchases, mobile-first flows, and contactless / QR-based payments.

Solution overview (what we deliver)

We implement a repeatable integration architecture composed of these layers:

1. Frontend payment UI

Hosted fields / drop-in components for card entry to reduce PCI scope (e.g., Adyen drop-in / hosted fields).
QR rendering for QR-first gateways (e.g., SkipCash) on checkout and POS screens.

2. Payment orchestration module (Odoo)

A payment-acquirer module that: creates payment requests, receives and validates webhooks, posts payments to orders/invoices, and triggers captures/refunds.
Uses Odoo’s payment acquirer framework for configurable, auditable flows.

3. Payment processor features

Adyen — tokenization, Pay-by-Link (create links via API), risk engine (3DS / velocity checks), and terminal support for POS.
SkipCash — QR-first and mobile-wallet flows, REST APIs/SDKs for create-payment, status checks, and webhook callbacks.

4. Security & compliance

Use processor tokenization (no PAN stored on merchant systems).
Validate webhook signatures, enforce HTTPS, rotate and protect API keys, and store minimal logs for audit.

5. POS & remote sales support

Generate payment links or QR codes from Odoo POS or backend; customer pays on device; webhook updates payment state and Odoo marks the order paid and updates inventory.

Integration Spotlight — Adyen (Global) + Odoo

Overview :

This global integration shows how we connect a full-featured payment provider (Adyen) with Odoo so online, mobile and in-store payments are secure, fast, and automatically recorded in the merchant’s ERP.

What it delivers:

Secure card & wallet checkout: Adyen provides ready-made checkout components for cards and digital wallets (Apple/Google Pay). Because Adyen handles the sensitive data, the merchant does not store card numbers.
Pay-by-Link and QR for quick payments: Sales staff or the POS can send a secure payment link or show a QR code; customers complete payment on their phone. No separate card terminal needed for remote sales.
Automatic ERP updates: When Adyen confirms payment, Odoo is notified and the order is marked paid, inventory is updated, and accounting entries are created.
Terminal option for physical stores: Where merchants use card terminals, Adyen terminal payments are also integrated into the same Odoo workflow.

Simple 3-step flow:

Cashier or website initiates payment (checkout, link, or QR).
Customer completes payment via Adyen (phone or terminal).
Adyen notifies Odoo → Odoo marks the order paid and updates stock/accounts.

Integration Spotlight — SkipCash (Regional, South Africa) + Odoo

Overview:

This regional spotlight shows how we integrate a QR-first gateway (SkipCash) with Odoo for fast, mobile-friendly payments suited to in-store and delivery use cases in South Africa.