> ## Documentation Index > Fetch the complete documentation index at: https://docs.archefusion.com/llms.txt > Use this file to discover all available pages before exploring further. # Observatory Archefusion, as a payment orchestrator, provides you with detailed insights into how all transactions are routed through different payment gateways. As a merchant, you can view gateway performance over time, why transactions fail, and how to fix them, and measure routing performance. ## Gateway performance This section provides insights into each gateway's performance, so you can adjust routing rules to improve transaction success rate and enhance customers' experience. You can click each payment gateway in the table to track its success rate and latency trend over a given period. | Term | Meaning | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Share | The percentage of total transactions routed to each payment gateway over the selected period. | | SR (Success rate) | The percentage of transactions that completed successfully on each payment gateway over the selected period. The bracketed percentage is the success rate from the previous equivalent period. | | Avg (Average) | The average time it takes for a payment gateway to process a transaction over the selected period. | | p95 (95th percentile) | The time it takes a payment gateway to process 95% of its transactions over the selected period. | | Timeout | The percentage of transactions that never got a response from each gateway over the selected period. | | 5xx | The percentage of transactions that returned a server error from each gateway over the selected period. | | Worst | The most common reasons for transaction failure on each gateway over the selected period. For example, invalid requests, authentication errors. | ### Payment gateway charts This section shows how each of your payment gateways performed over the selected period, helping you improve your routing rules based on their performance. For example, if a gateway's success rate drops or its latency increases, you can adjust your routing rules to route transactions to best-performing gateways or enable failover to protect your customers’ experience. **1. Success rate trend**: This shows how each gateway's success rate has changed day by day over the selected period. You can hover over any point to see the exact success rate on that date. **2. Latency trend**: This shows how long it takes each gateway to process a transaction day by day over the selected time period. You can hover over any point to see the exact latency on that date. ## Failure reasons This section provides insights into failed transactions, why they occur over the selected period, and how to fix them, so you can reduce transaction failures. ### Summary At the top of the page, there are three key metrics: **1. Failed transactions**: The total number of failed transactions over the selected period **2. Failed amount**: The total value of failed transactions over the selected period. **3. Basis**: How transaction failures are measured. For example, "final\_failed\_attempt" means a transaction is only counted as failed after all retry attempts have been exhausted. ### Failure table | Term | Meaning | | ------ | ---------------------------------------------------------------------------------------------------------------------------------------- | | Reason | The reason why a group of transactions failed. Click a reason to see its failure trend over time and the specific root causes behind it. | | Count | The total number of transactions that failed for a particular reason. | | Amount | The total value of transactions that failed for a particular reason. | | Share | The percentage of total failed transactions for a particular reason. | Clicking a reason in the table updates the trend chart and the root causes section to show details specific to that failure reason, along with a recommended fix. ## Routing insights This section provides insights into how smart routing has impacted transactions over the selected period, so you can determine whether it is improving transaction success rates. ### Summary At the top of the page, there are 4 key metrics: **1. Routed transactions**: The total number of payments processed through smart routing, including success, failure, and retries. **2. Failover rate**: The percentage of transactions that required switching to another gateway to prevent failure. It is counted once per transaction. **3. Success lift**: The improvement in success rate achieved by smart routing compared to what the success rate would have been without it. It also shows the number of failed payments prevented. **4. Latency**: The extra time added when processing a transaction due to retries or failover. ### Success rate comparison chart This compares the transaction success rate when smart routing is applied against what the success rate would have been without it over the selected period. ### Failover trend This shows how often smart routing had to switch gateways day by day over the selected period to prevent transaction failures. ### Gateway switch paths This table shows how transactions moved between gateways during failover to prevent failures. | Term | Meaning | | ----------------- | -------------------------------------------------------------------------------------------------------------- | | Path | The route transactions take between payment gateways to prevent failures. For example, Paystack → Flutterwave. | | Count | The number of transactions for each payment gateway path. | | Share | The percentage of total transactions for each payment gateway path. | | SR (Success rate) | The success rate percentage for each payment gateway path. | | Latency | The extra time added when routing transactions for each payment gateway path. | | Reason | The reason why transactions are routed from one payment gateway to another. |