Make sure backend services are running on ports 5001-5005
GreenLeafPayGO
GreenLeaf
PayGO Admin
Dashboard
Total Devices
-
Customers
-
Payments
-
Revenue
-
Quick Start Guide
Go to Devices → Add a Manufacturer (e.g., "GreenLight Solar")
Add a Device Type (e.g., "SHS-50W")
Add Devices with serial numbers
Go to Customers → Add customers
Assign devices to customers
Go to Payments → Record payments (tokens auto-generated!)
Use Token Generator for manual tokens
Products
Loading products...
Installations
ID
Customer
Technician
Status
Scheduled
GPS Dist.
Loading...
Evaluator Dashboard
Sales by Payment Method
Geographic Distribution
Arrears Report
Billing
Invoice #
Month
Subscription
Txn Fees
Total
Status
Due
Actions
Loading...
Devices
Manufacturers
0
Device Types
0
Total Devices
0
Active
0
Serial Number
Model / Capacity
Type
PAYGO
REA
Status
Customer
Actions
Customers
Name
Phone
Area
dMRV
Status
Payments
Pending Cash Approvals
Max 3/day · 10/week per approver · Lipa reference required
Reference
Customer
Amount
Date
Actions
All Payments
Reference
Customer
Amount
Method
Status
Date
Approve Cash Payment
1
Enter Lipa Reference
2
MM Verified → Approve
The mobile money reference confirming this cash was received. System will verify with the operator before approval.
Reject Cash Payment
Token Generator
Generate Token
Generated Token
Generated tokens will appear here
dMRV Pipeline
Step Breakdown
Blockers (Rejected Steps)
Pending Approvals
Customer
Area
Current Step
Days Waiting
Locations & Village Chairmen
Location hierarchy used for dMRV and REA prospect submissions
Location Codes
Code
Name / Ward
District · Region
Country
Chairman
Village Chairmen
Tenants
Each tenant is a company using PayGO. Platform admin creates the tenant + its first Business Admin account.
Company
Contact
Address
REA
Status
Actions
Users
Manage staff accounts within your tenant
Business Admin can add: Sales Rep, Technician, M&E Officer, Village Chairman, and other field roles.
Platform Admin adds the first Business Admin for each tenant.
User
Contact
Role
Tenant
Status
Last Login
Actions
Reports
Click Refresh to load report data
Platform Overview
Total Customers
-
Active Devices
-
Revenue (30d)
-
dMRV Complete
-
Customer Map — colored by dMRV status
VerifiedIn ProgressNot Started
Revenue Trend (30d)
Device Status
Recent Payments
Customer
Method
Amount
Status
Loading...
Customer Map
Total
-
dMRV Verified
-
REA Projects
-
With Arrears
-
Customer Locations — click marker for details
Monthly Registrations
Prospect Status
Customers
Name
Area
dMRV
Balance
Loading...
Device Map
Total
-
Active
-
Suspended
-
Unassigned
-
REA
-
Device Locations — colored by status
ActiveSuspendedUnassignedDecommissioned
Status Breakdown
By Device Type
Devices
Serial
Model
Customer
Status
Loading...
Payments Analytics
Total Revenue
-
Transactions
-
Avg Amount
-
Success Rate
-
Payment Origin Map — colored by method
M-PesaCashUSSD
Daily Revenue
By Provider (computed from last 500 records)
Recent Payments
Customer
Method
Provider
Amount
Status
Loading...
dMRV & REA Pipeline
In Pipeline
-
Pending Approvals
-
Avg Days/Step
-
REA Submitted
-
Customer Map — colored by dMRV step progress
Step Completion
REA Submissions
dMRV Kanban — 8 Steps
REA Submission Log
Customer
Pushed At
Success
HTTP
Circuit
Loading...
Notifications Analytics
Total Sent
-
Delivered
-
Delivery Rate
-
Pending
-
Delivery Rate Gauge
-
By Notification Type
Daily Volume (30d)
Recent Notifications
Customer
Type
Provider
Status
Sent At
Loading...
My Work
Loading your work queue...
Add Device
PAYGO Device
Generates OpenPAYGO tokens for pay-as-you-go access control
Device Identity
Must be globally unique — matches the label on the physical device
OpenPAYGO Token Credentials
Must match device firmware exactly
Programmed into device firmware at manufacture. If auto-generated here, program this value into the device before deployment.
Base value for all token calculations. Must match the value programmed in device firmware.
Starts at 1. Increments per token generated. Use Counter Sync token if device falls out of sync — do not edit directly.
REA / dMRV Registration
REA Government Project
Activates 8-step dMRV workflow and REA Prospect API submission. Required for government rural electrification grants.
Project code assigned by the Rural Electrification Agency of Tanzania.
Batch Upload Instructions
Upload the CSV file received directly from your device supplier — no reformatting needed
Or download the template below and fill in one device per row
Rows with bothStarting Code and Key → loaded as PayGO devices
Rows with only Serial Number (no key/code) → loaded as Non-PayGO devices
Set is_rea_project to TRUE/FALSE per device if applicable
Column
Required
Example
Notes
Serial Number
Yes
508230421
Unique per device. Also accepted: serial_number
Starting Code
PayGO only
693368863
OpenPAYGO starting code from manufacturer. Also: starting_code
Key
PayGO only
de950c67…
32 hex secret key from manufacturer. Also: secret_key
Count
Optional
1
Token count — leave blank to default to 1
Hardware Model
Optional
H4G-150
Physical model name. Also: model
type
Optional
PAYGO-50W
Device Type code. Also: device_type_code
manufacturer_code
Optional
GREENLEAF
Must match a Manufacturer code in the system
capacity_watts
Optional
50
Number only (W added automatically)
is_rea_project
Optional
TRUE
TRUE or FALSE (default FALSE)
rea_project_id
Conditional
REA-TZ-041
Required if is_rea_project=TRUE
Auto-detection: A row with both Starting Code and Key is loaded as a PayGO device.
A row with only Serial Number (no key/starting code) is loaded as a Non-PayGO device.
You can upload the CSV file received directly from your supplier — no reformatting needed.