Features
No marketing descriptions. Below is exactly how Gigva works, workflow by workflow, with the specific input and output at each step. Designed for Kenyan retail shops, logistics operators, and SMEs handling daily M-Pesa transactions.
From payment received to reconciled invoice, for retail shops processing 50–500 daily M-Pesa transactions
Your customer sends M-Pesa to your registered Paybill or Till number. Safaricom processes the payment and sends a C2B callback to Gigva within 3–5 seconds.
Gigva logs the full transaction: sender name, phone number, M-Pesa reference code, amount, and exact timestamp. This record is immutable: it cannot be edited, only supplemented.
Gigva compares the payment amount and reference against your open invoices. If the amount matches an outstanding invoice exactly, the invoice is marked paid and the transaction is marked reconciled automatically.
Partial payments, unrecognised references, and amounts that do not match any open invoice are flagged in your dashboard. Each flag includes the full transaction detail and a list of the closest matching open invoices.
For each flagged transaction, you choose: match to a suggested invoice, match to any other invoice manually, split across multiple invoices, or mark as other income. Every action is logged.
Pull a reconciliation report for any date range: all transactions, their match status, outstanding invoices, and a cash summary. Download as CSV for import into your accounting tool or PDF for filing.
How Gigva surfaces payment anomalies for logistics firms and SMEs before they become problems
Gigva learns your payment patterns during the first 30 days: typical daily volume, average transaction amounts, and which customers pay regularly. This baseline is used for anomaly detection.
Each incoming payment is compared against your baseline. Transactions with amounts significantly above or below your typical range for that customer are flagged for review.
Alongside anomaly scoring, fixed rules run every time: duplicate reference detection (same reference used twice), missing invoice check (transaction has no matching invoice after 24 hours), and configured revenue thresholds.
When a score or rule triggers, Gigva creates an alert that includes the full transaction detail, the specific rule or score that triggered it, and a suggested action (review transaction, chase invoice, check for duplicate).
Alerts appear in your dashboard notification panel and are sent to your registered email address. You mark each alert resolved or take the suggested action. Resolved alerts are logged with a timestamp.
Everything in Gigva right now. Updated when features ship.
Book a 30-minute walkthrough. We will demo each workflow using a dataset that matches your business: retail, logistics, or services.
Book a demo