Overview
Smart routing is the core of Reevit's orchestration engine. Instead of hardcoding a single provider, you define rules that determine which connection handles each payment, with automatic failover when things go wrong.
How routing works
When a payment comes in, Reevit evaluates your routing rules in priority order:
- Match conditions: Currency, payment method, amount range, customer country
- Select connection: The first matching rule determines the primary connection
- Failover chain: If the primary fails, Reevit automatically tries the next connection in the chain
Default behavior. Without routing rules, Reevit uses your first-connected provider for all payments. Adding rules unlocks the full power of multi-provider orchestration.
Create your first routing rule
Navigate to Routing Rules
From your dashboard sidebar, click Routing → Rules. You'll see the rule builder interface.
Click Create Rule
Click Create Rule to open the rule builder. Each rule consists of conditions and a provider priority chain.
Define conditions
Set the conditions that trigger this rule. You can combine multiple conditions:
- Currency: e.g., only match GHS payments
- Payment method: e.g., only match mobile money
- Amount range: e.g., payments over 1,000 GHS
- Customer country: e.g., only customers from Ghana
Example: Route all GHS mobile money payments through Hubtel.
Set the provider chain
Add connections in priority order:
- Primary: Hubtel (handles the payment first)
- Failover 1: Paystack (tries if Hubtel fails)
- Failover 2: Flutterwave (last resort)
Each connection in the chain is tried sequentially if the previous one fails. This all happens within milliseconds, invisible to the customer.
Set priority
If you have multiple rules, drag them to set evaluation priority. Higher-priority rules are evaluated first. The first matching rule wins.
Save and activate
Click Save Rule. The rule takes effect immediately for new payments. Existing in-flight payments are not affected.
Example routing configuration
Here's a common setup for a business operating in Ghana and Nigeria:
| Rule | Conditions | Primary | Failover |
|---|---|---|---|
| Ghana Mobile Money | Currency: GHS, Method: mobile_money | Hubtel | Paystack |
| Ghana Cards | Currency: GHS, Method: card | Paystack | Stripe |
| Nigeria Cards | Currency: NGN, Method: card | Paystack | Flutterwave |
| International Cards | Currency: USD/EUR/GBP | Stripe | Flutterwave |
Automatic failover
When a payment fails at the primary provider, Reevit automatically:
- Detects the failure type (network error, declined, rate limit, provider down)
- Routes to the next connection in the chain
- Retries the payment with the same parameters
- Returns the result to your application, seamlessly
Failover is invisible. Your application receives one response. Whether it took 1 provider or 3, the API contract is identical. You can see the full routing path in the payment details.