Skip to content

We started this because a payment failed.

One integration in front of the provider accounts you already own. We route the charge; your money never touches us.

  • Remote-first
  • Built in Africa
  • BYOK by design
8

providers behind one API, from Paystack to M-Pesa.

GH·NG·KE

failover markets, where two or more providers overlap.

8

SDKs shipped: Node, Python, Go, PHP, Rust, React, Vue and Svelte.

GHS0

of your money we hold. Charges settle to your own accounts.

01 · Origin

Born from a real problem.

Reevit started while we were building an e-commerce app for a natural spices merchant. The project hit a wall when payment services repeatedly failed. Callbacks arrived inconsistently, and every provider outage meant lost sales with no fallback.

Worse, switching providers meant rewriting the payment code from scratch. The problem wasn’t any single provider. It was the missing layer between them.

So we built what was missing. One API, your own credentials behind it, and a charge that moves to the next provider the moment one stops answering.

checkout.logbefore / after
# the nightmarePOST /webhooks/provider_a502 Bad GatewayPOST /webhooks/provider_b408 Timeout # the fixPOST /api/v1/payments200 · rerouted to healthy provider{ "status": "succeeded" }
The brief

A simple e-commerce build turned into a nightmare of unreliable webhooks and provider lock-in.

02 · Principles

Engineering resilience.

Four rules we hold every part of Reevit to. Point at a card to see the rule at work.

01

Security first

Production credentials are vaulted with envelope encryption, the keys held in a separate, hardened key management system. They are AES-256-GCM at rest and only ever decrypted in memory, at the moment of the call.

Vault · paystack_liveAES-256-GCM
Secret keyenc:v1 · 9fQ2…xK7e
In memorynothing held
Visible to our teamnever
02

Developer experience

One SDK, one format, one response structure. Provider-specific complexity is our problem, not yours. Switching rails should never mean rewriting your product.

Response
status"succeeded"
amountGHS 150.00
provider"paystack"
03

Automatic failover

Cascading routes that prioritise healthy providers. When a default channel times out or goes down, the charge reroutes inside the same request.

Route · Ghana · mobile money
01hubteldefault
02paystackfallback
03flutterwavefallback
04

Africa first

Mobile money, cards, and bank transfers behind one API, market by market.

Coverage

6 of 8 providers cover Ghana.

Stop losing payments to provider downtime.

Free for your first 1,000 payments a month, and failed payments are never billed. Connect a provider and take your first payment before the coffee gets cold.