Questions, answered.

Payment orchestration is the layer between your application and multiple payment providers. Instead of building and maintaining separate integrations for Paystack, Flutterwave, M-Pesa, and Stripe, you integrate once with Reevit. We handle the complexity: automatic failover when a provider is down, smart routing to maximize success rates, and unified reporting across all your payment channels.

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.

Most teams are processing live payments within 2-4 hours. Install our SDK, add your existing provider credentials, configure your routing rules in our dashboard, and you're live. We provide migration guides for teams moving from direct Paystack, Flutterwave, or Stripe integrations. Our record is 23 minutes from signup to first live transaction.

The free tier covers unlimited sandbox transactions, every payment provider, smart routing, webhooks, and the full dashboard. The only limit is live transactions (100/month). No credit card required, no time limit, no feature restrictions.

You pay a platform fee on each successful transaction, starting at 0.5%, plus whatever your payment providers charge directly. No monthly minimums, no hidden fees, no contracts. As you grow, your rate automatically decreases. High-volume merchants on our Scale plan pay as low as 0.25%. Failed transactions are always free.

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 Paystack, Flutterwave, Hubtel, Monnify, M-Pesa, PawaPay, and Stripe. That covers cards, mobile money, bank transfers, and USSD across Ghana, Nigeria, Kenya, Zambia, and 40+ countries via Stripe. New providers are added monthly based on merchant requests. Need a specific provider? Let us know. We typically add new integrations within 2-4 weeks.

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.