Features
What Gigva does, step by step
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.
How M-Pesa reconciliation works
From payment received to reconciled invoice — for retail shops processing 50–500 daily M-Pesa transactions
Customer pays your Paybill or Till
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.
Transaction is recorded immediately
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.
System attempts to match to an open invoice
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.
Mismatches are flagged for review
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.
You resolve flags with one action
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.
Reports are available any time
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 smart alerts work
How Gigva surfaces payment anomalies for logistics firms and SMEs before they become problems
Baseline established over 30 days
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.
Every transaction is scored
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.
Rule-based checks run in parallel
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.
Alert created with context
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).
Alert delivered and resolved
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.
Complete feature list
Everything in Gigva right now. Updated when features ship.
Payments & Reconciliation
- M-Pesa C2B Daraja v2 webhook ingestion
- Real-time transaction feed (3–5 second capture)
- Auto-match by payment amount and customer reference
- Partial payment detection and flagging
- Duplicate transaction reference detection
- Manual match with override log (user + timestamp)
- Invoice status sync: paid, partial, outstanding
- End-of-day reconciliation summary (in-app + email)
Analytics & Reporting
- Daily revenue chart with previous period comparison
- Weekly and monthly revenue summaries
- Top customers by M-Pesa payment volume
- Invoice aging report: 30 / 60 / 90+ days
- Failed and pending payment summaries
- Payment timing analysis (when customers pay)
- CSV export — all transactions, all date ranges
- PDF report formatted for accountants
Smart Alerts
- Unusual payment amount alert (per-customer baseline)
- Duplicate transaction reference detection
- Revenue below threshold notification
- Customer missing expected payment alert
- Invoice unmatched after 24 hours
- Invoice overdue escalation (configurable days)
- Configurable alert thresholds per business
- In-app and email delivery per alert type
Integrations
- REST API with OpenAPI documentation
- Outbound webhooks: payment.received, payment.reconciled, payment.flagged
- QuickBooks-compatible CSV export format
- Xero-compatible CSV export format
- API key management with per-key permission scopes
- Request log with HTTP status and latency
- Webhook retry: exponential back-off, up to 5 attempts
- Test mode for integration development (no real data)
Account & Security
- Multi-user accounts with roles: owner, accountant, viewer
- bcrypt password hashing — cost factor 12 (~250ms per hash)
- JWT sessions — 7-day expiry, HS256
- Login audit log (IP, timestamp, outcome)
- AES-256 data encryption at rest
- TLS 1.3 for all data in transit
- Kenya-hosted data — no cross-border transfer
- Two-factor authentication (roadmap Q3 2025)
See every feature in action
Book a 30-minute walkthrough. We will demo each workflow using a dataset that matches your business — retail, logistics, or services.
Book a demo