Connect your first payment provider.

Overview

Reevit uses a Bring Your Own Keys (BYOK) model. You maintain direct relationships with your payment providers, and Reevit orchestrates traffic using your credentials. This means your funds always flow directly to your merchant accounts.

In this guide, you'll add your first provider connection in sandbox mode.

Prerequisites

• A Reevit account (see Create Your Account)
• API credentials from at least one supported provider (Paystack, Flutterwave, Hubtel, Monnify, or Stripe)

Add a connection

1. 1

   Navigate to Connections

   Mark as doneDoneMark step 1 as done

   From your dashboard sidebar, click Connections. You'll see an empty state with a prompt to add your first connection.

2. 2

   Click Add Connection

   Mark as doneDoneMark step 2 as done

   Click the Add Connection button in the top right. A sheet will slide open with the list of supported providers.

3. 3

   Select your provider

   Mark as doneDoneMark step 3 as done

   Choose from the supported providers:

   • Paystack: Cards, bank transfers, mobile money (Ghana, Nigeria)
   • Flutterwave: Cards, mobile money, bank transfers (Nigeria, Ghana, Kenya, 30+ countries)
   • Hubtel: Mobile money (Ghana)
   • Monnify: Bank transfers, cards (Nigeria)
   • Stripe: Cards, wallets (40+ countries)
4. 4

   Enter your credentials

   Mark as doneDoneMark step 4 as done

   Paste your test/sandbox API keys from the provider's dashboard. Each provider requires different fields:

   For Paystack:

   • Secret Key (starts with sk_test_)
   • Public Key (starts with pk_test_)

   For Flutterwave:

   • Secret Key
   • Public Key
   • Encryption Key

   For Hubtel:

   • Client ID
   • Client Secret
   • Merchant Account Number

   Hubtel callbacks are managed by Reevit. You do not need to type a Hubtel callback URL into the connection form. Reevit sends its own inbound webhook URL to Hubtel automatically when a payment is created.

5. 5

   Add a label

   Mark as doneDoneMark step 5 as done

   Give your connection a descriptive label, like paystack-ghana-test or stripe-primary. Labels must be lowercase, alphanumeric, with hyphens. This label is used in routing rules and API calls.

   Use a naming convention like provider-region-environment to keep things organized as you scale.

6. 6

   Save and verify

   Mark as doneDoneMark step 6 as done

   Click Save Connection. Reevit will validate your credentials by making a lightweight API call to the provider. If successful, you'll see a green "Connected" status.

Connection health

Once connected, Reevit monitors your connection's health in real-time:

• Healthy (green): Provider is responding normally
• Degraded (amber): Elevated error rates detected
• Unhealthy (red): Provider is experiencing issues

Health is calculated from the success rate of recent transactions. If a connection becomes unhealthy, smart routing will automatically shift traffic to your next provider.

Next steps