Rekurra — The billing layer Wompi doesn’t give you: plans, recurring charges and multi-tenant with a single API.
A subscription platform on top of Wompi: plan creation, recurring charges with retries, hosted checkout and an MRR dashboard, all through a single API and SDKs for six languages.
Visit rekurra.devWhy it exists.
Wompi solves one-off charges in Colombia, but not recurrence: no plans, no subscriptions, no retries, no multi-tenancy. Every SaaS that wants to bill monthly ends up building its own billing layer from scratch.
What we built.
We built Rekurra as the billing layer that sits on top of Wompi: plan and price creation, a recurring-charge engine with dunning (automatic retries and failed-payment recovery), hosted checkout that never touches cards, multi-tenant infrastructure with isolated API keys per client, and a dashboard with real-time MRR, active subscriptions and churn. Backend in .NET 8 with Clean Architecture and PostgreSQL; official SDKs for six languages.
Outcome.
Rekurra operates as a subscription platform with three plans (from free Hobby to Scale), SDKs for C#, Java, JavaScript, Python, PHP and cURL, and a metrics panel for the development teams that integrate it. A single endpoint replaces the billing layer every SaaS used to rebuild by hand.
Rekurra was born from a concrete gap in the Colombian ecosystem: Wompi is a great gateway for one-off charges, but it offers nothing for recurrence. No plans, no billing cycles, no retries when a card fails, no multi-tenant separation. The result is that every SaaS that wants to charge subscriptions ends up writing its own billing layer, the most delicate and least differentiating part of its product, over and over.
We designed Rekurra as that layer, ready to sit on top of Wompi through a single API. Teams create plans and prices, and Rekurra handles the full cycle: recurring charges, dunning with automatic retries and failed-payment recovery, hosted checkout so they never handle card data, and multi-tenant isolation where each client has its own API keys. A dashboard shows MRR, active subscriptions and churn in real time.
The engineering is built to last: backend in .NET 8 and C# with Clean Architecture (Domain / Application / Infrastructure / Api), EF Core on PostgreSQL, dashboards in React + Vite + TypeScript with shadcn/ui and a Next.js landing. Official SDKs ship for six languages —C#, Java, JavaScript, Python, PHP and cURL— so integrating recurring subscriptions takes hours, not months.