Engineering Software for Cash-First Economies: Ledger Reconciliation, OTP Fallbacks, and Low-Bandwidth Networks

The Double-Entry Accounting Solution

In digital payment platforms, Stripe or Visa handles fund transfers. In Cash-on-Delivery (COD) systems, currency physically sits in the driver's pocket at the moment of handover. If a driver collects PKR 5,000 across ten deliveries and their phone battery dies, your platform must maintain continuous accounting integrity.

To prevent fraud and ledger discrepancies, every physical currency event is recorded using Immutable Double-Entry Bookkeeping:

-- Transaction: Customer pays Driver on delivery of Order #4928
BEGIN;

-- Credit Merchant Receivable
INSERT INTO journal_entries (entry_id, account_id, debit, credit, reference_id)
VALUES (gen_random_uuid(), 'acct_merchant_payable_78', 0, 1500.00, 'ORD-4928');

-- Credit Platform Commission
INSERT INTO journal_entries (entry_id, account_id, debit, credit, reference_id)
VALUES (gen_random_uuid(), 'acct_platform_revenue', 0, 250.00, 'ORD-4928');

-- Debit Driver Cash-in-Hand Holding Account
INSERT INTO journal_entries (entry_id, account_id, debit, credit, reference_id)
VALUES (gen_random_uuid(), 'acct_driver_cash_holding_12', 1750.00, 0, 'ORD-4928');

COMMIT;

Handling SMS & WhatsApp OTP Fallbacks

In tier-2 and tier-3 regions, automated SMS gateways experience variable delivery latency. If a customer cannot receive a verification code within 30 seconds, they abandon the app.

Implementing an intelligent fallback ladder—attempting Firebase SMS first, switching to automated WhatsApp Cloud API delivery after 25 seconds, and finally providing an automated voice-call verification—ensures onboarding completion rates remain high.