> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pesaswap.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Default Fall Back Routing

Fallback is a priority order of all the configured processors which is used to route traffic standalone or when other routing rules are not applicable.

## Overview

Default Fallback Routing serves as a safety net for payment processing. When active routing rules are not applicable, the system uses a predefined priority order of all configured payment processors to route payments. This priority order is fully configurable from the Dashboard.

## How Default Fallback Works

Default Fallback Routing activates in the following scenarios:

* **No Active Routing Algorithm:** When you have no routing algorithm currently active
* **Payment Method Mismatch:** When the payment method for the current payment is not enabled for the processor(s) returned by the active routing algorithm
* **Routing Rule Failure:** When existing routing rules fail to match the current transaction parameters

## Getting Started with Default Fallback Routing

The Default Fallback configuration allows you to establish a backup routing strategy that ensures payment processing continuity even when primary routing rules don't apply.

### Key Benefits

* **Guaranteed Processing:** Ensures payments can always be attempted through available processors
* **Flexible Priority:** Customize processor order based on your business preferences
* **Automatic Failover:** Seamlessly switches to fallback routing when needed
* **Easy Management:** Simple drag-and-drop interface for reordering processors

## Configuration Steps

### Step 1: Access Default Fallback Configuration

1. Navigate to the **Smart Router** section in your dashboard
2. Locate the **Default Fallback** configuration area
3. Click on **Manage** to begin configuring the fallback routing

### Step 2: Configure Processor Priority

You will see a list of all your configured processors. This list represents the order in which processors will be attempted when fallback routing is triggered.

**Reordering Processors:**

1. **View Current Order:** See the existing priority sequence of your processors
2. **Drag and Drop:** Reorder processors by dragging them to your desired position
3. **Set Priority:** Place your most preferred processor at the top of the list
4. **Secondary Options:** Arrange backup processors in order of preference

### Step 3: Save Configuration

1. **Review Order:** Confirm the processor priority order meets your requirements
2. **Apply Changes:** Save the configuration to activate the new fallback routing
3. **Test Setup:** Consider running test transactions to verify the routing works as expected

## Configuration Best Practices

### Processor Ordering Strategy

**Primary Processor (Top Priority)**

* Choose your most reliable and cost-effective processor
* Consider success rates and processing fees
* Ensure it supports your most common payment methods

**Secondary Processors**

* Order by reliability and performance metrics
* Consider geographical coverage and currency support
* Balance cost with success rate requirements

**Backup Processors**

* Include processors with broad payment method support
* Consider processors with different risk profiles
* Ensure coverage for edge cases and unusual transactions

### Considerations for Priority Order

| Factor                  | Description                               | Impact on Priority                                          |
| ----------------------- | ----------------------------------------- | ----------------------------------------------------------- |
| **Success Rate**        | Historical transaction success percentage | Higher success rate = Higher priority                       |
| **Processing Cost**     | Fees charged per transaction              | Lower cost = Higher priority (if success rates are similar) |
| **Geographic Coverage** | Supported countries and regions           | Better coverage = Higher priority for global merchants      |
| **Payment Methods**     | Supported payment types                   | Broader support = Higher priority for diverse payment needs |
| **Settlement Speed**    | Time to receive funds                     | Faster settlement = Higher priority for cash flow           |

## Monitoring and Management

### Performance Tracking

Monitor the effectiveness of your fallback routing through:

* **Fallback Usage Rate:** How often fallback routing is triggered
* **Success Rate by Processor:** Performance of each processor in the fallback chain
* **Transaction Volume:** Distribution of payments across fallback processors

### Regular Review

**Monthly Assessment:**

* Review processor performance metrics
* Analyze fallback routing usage patterns
* Adjust priority order based on performance data

**Quarterly Optimization:**

* Evaluate new processor additions
* Remove underperforming processors
* Update priority based on business changes

## Advanced Configuration

### Conditional Fallback

For more sophisticated routing needs, consider:

* **Payment Method Specific:** Different fallback orders for different payment types
* **Regional Variations:** Adjust processor priority based on customer location
* **Transaction Amount:** Different routing for high-value vs. standard transactions

### Integration with Other Routing Rules

Default Fallback works alongside:

* **Volume-based Routing:** Primary routing by transaction volume
* **Geography-based Routing:** Regional processor preferences
* **Time-based Routing:** Different processors for different time periods
* **Success Rate Routing:** Dynamic routing based on real-time performance

## Troubleshooting

### Common Issues

**Fallback Not Triggering**

* Verify that primary routing rules are correctly configured
* Check that fallback processors are properly enabled
* Confirm payment methods are supported by fallback processors

**Poor Fallback Performance**

* Review processor order and success rates
* Check for processor-specific issues or outages
* Verify processor configurations and credentials

**Unexpected Routing Behavior**

* Confirm routing algorithm settings
* Check payment method enablement for each processor
* Review transaction logs for routing decisions

### Support and Assistance

For help with Default Fallback Routing:

* **Dashboard Help:** Use the built-in help documentation
* **Support Team:** Contact nical support for configuration assistance
* **Documentation:** Refer to the complete Smart Router documentation

## Next Steps

After configuring Default Fallback Routing:

1. **Test Thoroughly:** Run test transactions to verify routing behavior
2. **Monitor Performance:** Track fallback usage and success rates
3. **Optimize Regularly:** Adjust processor priority based on performance data
4. **Expand Coverage:** Add new processors to improve payment success rates

## Summary

Default Fallback Routing provides essential backup payment processing capabilities by:

* Maintaining a configurable priority order of processors
* Automatically routing payments when primary rules don't apply
* Ensuring payment processing continuity
* Offering easy management through the dashboard interface

This failsafe mechanism helps maintain high payment success rates and provides reliable transaction processing even when primary routing strategies encounter issues.