Understand your revenue and customers.
MRR, revenue, usage and customer views that match your invoices — because they come from the same ledger.
Everything analytics needs, included.
- 01MRR
Monthly recurring revenue and its movements.
- 02Revenue
By period, product and rail.
- 03Usage
Metered volume per meter and customer.
- 04Customers
New, active, churned.
- 05Export
Metrics endpoints under /analytics.
- 06Logs
API and usage logs alongside the numbers.
Numbers you can reconcile.
Every figure traces back to invoices and payments in the same workspace — no second source of truth.
Pull it into your own tools.
GET /analytics/overview, /mrr, /revenue, /usage and /customers return the same data as the dashboard.
evt_118+ 4.5processedevt_119+ 12.0processedevt_119+ 12.0duplicateevt_120+ 3.2processed- Roles, MFA, audit log
Owner to viewer roles, TOTP with step-up, every sensitive change recorded.
Find out more - Signed webhooks
Tola-Signature (HMAC-SHA256, timestamped), retries, no private-network deliveries.
Find out more - Test and live modes
tola_test_ keys with sandbox Khalti, eSewa and Stripe; flip to live when ready.
Find out more
Get up and running fast.
One REST API under /api/v1, documented in OpenAPI. Create a customer, send an event, open a checkout — and listen for invoice.paid. Everything on this page is reachable from the API and the dashboard alike.
Read the docstola_test_•••• 7f2k2 min agotola_live_•••• m4abRotating · 24h gracehttps://api.yourapp.np/tolainvoice.paid · 200Tola-Signature · HMAC-SHA256Retries on 5xxGoes well with analytics.
Asked often.
Is there revenue recognition?
Deferred revenue schedules are on the roadmap; today you get MRR, revenue and usage reporting.
Can I try it before going live?
Yes. Every workspace has a test mode with separate tola_test_ keys and sandbox Khalti, eSewa and Stripe.