Born from a real problem.
Reevit started when a simple e-commerce project turned into a nightmare of unreliable webhooks and provider lock-in.
Reevit was born during the development of an e-commerce application for a natural spices merchant. The project faced critical challenges when payment services repeatedly failed, highlighting a systemic infrastructure gap.
The root cause was identified as unreliable webhooks; callbacks were inconsistently received, and switching providers necessitated an exhaustive codebase overhaul.
"The need for a unified African payment landscape became evident—a system designed to remain resilient even when individual providers experience downtime."
Drawing on expertise in building global infrastructure at Primer.io, the mission became focused on bringing that same institutional-grade resilience and a developer-first approach to the African continent.
# The Nightmare
POST /webhooks/provider_a
Status: 502 Bad Gateway
POST /webhooks/provider_b
Status: 408 Timeout
# The Solution: Reevit
POST /api/v1/payments
Status: 200 Unified Response
{
"status": "success",
"provider": "failover_healthy"
}
