GetRisiti (@getrisiti) header
GetRisiti (@getrisiti) profile picture

Add eTIMS invoicing to your POS, ERP, SaaS or marketplace. One API, multiple merchants. Sandbox now open for Kenyan software teams.

Nairobi, Kenya
Joined June 2026
Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)Photo by GetRisiti (@getrisiti)
🤧🤧🤧 hug a bald man, those people are suffering
13
“Mbele naona success…”
6
“Even Heaven demands Death”
Young people believe they can hold on to what they have and still gain what they want . They think they can get fit and still drink and eat junk on the weekends . They think they can start a business and still have free time to take a vacation anytime. The moment you understand that life demands a sacrifice for what you want most is the moment you will get clarity. Even heaven demands death.
1
1
69
KRA wameannounce stock management ya eTIMS. Risiti tuliship kitambo. Hii future mnasema, sisi tunaishi ndani yake 😮‍💨
Public notice 🚨 KRA is preparing to implement the Stock Management functionality for electronic invoicing, with stakeholder consultations beginning in September 2026. Taxpayers and businesses are encouraged to participate and share feedback to help ensure a smooth and practical rollout. For feedback and support, contact KRA via 020 4 999 999 / 0711 099 999 or Email [email protected] or [email protected]
1
83
Na best part? eTIMS yote iko kwa simu yako. Hakuna extra device. Hakuna setup costs. Hakuna mambo mingi. Ingia Risiti, anza biashara. Join our waitlist: getrisiti.com
53
KRA just announced the roadmap. Risiti already shipped it. Stock bought. Sold. Transferred. Returned. Adjusted. We’re not catching up with the future of eTIMS. We built for it before it arrived, stock automatically sync with KRA.
KRA plans to introduce stock tracking on eTIMS. Businesses will be required to record stock bought, sold, transferred, returned or adjusted. [For example, if you run a business, you will need to keep track of your stock movements on eTIMS].
1
76
Customer: “Nitumie ETR.” You: “Sawa.” Not: “Ngoja nifungue laptop.” RISITI is coming. getrisiti.com
1
8
67
49,601
Where do your customers actually ask for invoices: WhatsApp, email or print?
163
The way Kenyan businesses issue eTIMS invoices is about to change.
4
22
52,586
Watu wanastress juu ya eTIMS kama KRA iko chini ya kitanda yao. Calm down. Risiti inakusort invoicing yote, wewe shughulikia biashara yako tu. 😮‍💨 getrisiti.com
126
KRA was down for 3 days. For many businesses, that meant invoices could not be submitted, customers had to wait, and payments were delayed. With Risiti, your invoice is safely received, queued, and automatically retried when KRA is available again. KRA downtime should not become your business downtime.
Notice to all eTIMS Online Portal users📢 The eTIMS Online Portal is currently unavailable due to a technical issue. Our team is actively working to resolve the issue and restore normal service. We regret any inconvenience caused and thank you for your continued patience.
97
First external developer review of the Risiti API found a real scaling flaw. Our fixed retry schedule could cause hundreds of invoices to hit KRA simultaneously after an outage. They were right. We’re replacing it with per-invoice exponential backoff, jitter, circuit breaking and bounded concurrency. This is why we asked developers to break it.
1
52
The dangerous sequence: KRA goes down - invoices accumulate - KRA recovers - every retry fires together - the recovery causes another failure Shared retry schedules look harmless at low volume. At platform scale, they become coordinated traffic spikes.
45
Kenyan developers are rebuilding the same eTIMS plumbing inside every POS, ERP, pharmacy app, garage system and marketplace. Same KRA problem. Different codebase. Again and again. Hii ni wazimu. We built Risiti: one eTIMS API underneath your product. Break it.
1
71
No forced Risiti dashboard. You own the interface and customer relationship. Use Scalar to inspect the endpoints, send sandbox requests and tell us where the API becomes confusing or unsafe. developers.getrisiti.com We want broken assumptions, not launch applause.
1
36
Test any one area: • Authentication • Merchant isolation • Invoice schemas • Validation errors • Idempotency • Failure recovery • Webhooks • Documentation Reply with the exact endpoint, field or workflow that needs fixing. We will publish what we change.
10