Questions, answered.

With Bring Your Own Keys, you maintain direct relationships with payment providers. Your API credentials, your merchant accounts, your money. Funds never touch Reevit. They flow directly from customers to your accounts. You negotiate your own rates, settlement lands in your account on your provider's schedule, and you can leave with your credentials whenever you like. We simply orchestrate the traffic using your credentials, encrypted with AES-256-GCM.

You don't have to switch. You add Reevit as your orchestration layer while keeping your existing provider relationships. The benefits: automatic failover when your primary provider has issues (which happens more often than you'd think), the ability to A/B test providers, unified webhooks and reporting, manual/partial capture, saved payment methods, scheduled payments, and unified 3DS/SCA next_action flows across PSPs. Add new payment methods or expand to new countries without code changes.

Install one of our SDKs (Node, Python, Go, PHP, Rust, React, Vue or Svelte), add your existing provider credentials, configure your routing rules in the dashboard, and switch to your live keys. The reevit init wizard does most of that from your terminal: it detects your framework, installs the right SDK, wires your environment, and writes working checkout and signed-webhook code. Then reevit doctor checks the whole integration, including that your webhook handler accepts genuine signed events and rejects tampered ones, before you go live. We provide migration guides for teams moving from direct Paystack, Flutterwave, or Stripe integrations.

Yes. Free includes 1,000 live transactions a month and unlimited sandbox testing, with 1 live connection, 2 sandbox connections and 1 team member. You get webhooks and the API, audit logs, smart routing, 2,000 workflow executions and 5,000 webhook attempts a month, and 7-day data retention, and you can prove failover across 2 sandbox providers before you pay anything. Live volume is hard-capped at 1,000 a month, and failed payments are never billed. When you need more connections, seats or history, move to Starter or Growth.

You pick a monthly plan; there is no percentage fee on your volume. Free is GHS 0 for 1,000 live transactions a month. Starter is GHS 199 a month (NGN 25,000 · KES 1,999 · USD 15) for 10,000 transactions, 4 live connections and 3 team members. Growth is GHS 649 a month (NGN 80,000 · KES 6,499 · USD 49) for 100,000 transactions, unlimited live connections, 10 team members, routing A/B tests and custom fraud rules. Failed payments are never billed, and your providers bill their processing fees directly. Compare every plan line by line, or talk to us about custom volumes.

Never. You only pay Reevit when money successfully moves. Declined cards, insufficient funds, network timeouts, and provider errors are all free. This aligns our incentives: we only make money when you make money. It's also why routing and failover get more engineering time here than anything else.

We support eight providers: Paystack, Hubtel, Flutterwave, Monnify, M-Pesa, Stripe, PawaPay, and Moolre. That covers cards, mobile money and bank transfers, plus Apple Pay and Google Pay through Stripe. Mobile money runs across Ghana, Nigeria, Kenya, Zambia and other African markets, and Stripe takes cards internationally. Automatic failover works wherever two or more providers overlap, which today is Ghana, Nigeria and Kenya. Moolre, for Ghana mobile money, is explicit-routing-only during its pilot. See every provider, and if you need one that isn't listed, let us know.

You configure a priority list of providers for each payment method. When a transaction fails (network error, provider downtime, rate limit), we automatically retry with the next provider in your chain, inside the same request, with nothing for your customer to retry. You can also set rules: route mobile money through Hubtel, but if it fails, try Paystack. Route cards through Stripe, failover to Flutterwave. The payment detail page lists every attempt, which provider took it, and why the earlier ones failed.

Yes, and it's provider-agnostic. Create subscription plans, manage billing cycles, schedule charges, store saved payment methods, handle upgrades/downgrades with proration, and automate failed payment recovery (dunning) all through one API. If a customer's card fails on Paystack, we can automatically retry on Flutterwave. You get one subscription dashboard across all providers, not one per provider.

Your credentials are encrypted at rest using AES-256-GCM with keys stored in a separate, hardened key management system. They're only decrypted in isolated memory when making API calls. They're never logged, never written to disk, never visible to our team. You can rotate credentials anytime from your dashboard, and we support IP allowlisting for additional security.

We're designed to keep you PCI compliant. Reevit never sees or stores card numbers. Sensitive payment data goes directly to PCI DSS Level 1 certified providers. Our infrastructure runs on SOC 2 compliant cloud providers with encryption in transit (TLS 1.3) and at rest. We run penetration tests, and every transaction gets an audit log entry.

We run multi-region redundancy with automatic failover at the infrastructure level, and we publish live status at reevit.io/status rather than quoting a marketing number. But here's the key difference with BYOK: if the worst happens, you can bypass Reevit entirely and call your providers directly. You own the credentials.