In the realm of payment processing, the detection and mitigation of anomalies are crucial to ensure efficiency and conversion rates. However, one of the biggest challenges is identifying anomalies in payment processing from providers, making real-time detection and action difficult. Therefore, complete monitoring and support teams are required to detect anomalies and take immediate action.

From the Monitors section in the Yuno dashboard, you can detect and mitigate anomalies that may arise in payment processing.

Monitoring process operation

The Monitor operation is divided into three action types to identify and restore your payment routes:

  1. Detection of anomalies and alarms: Monitors continuously check the approval rate. The approval rate is calculated based on a time period you define. If the approval rate falls below the defined threshold, an alarm is activated through various channels you can configure, such as email and Opsgenie.
  2. Send alert: In a scenario where the approval rates fall below the threshold, Yuno sends an alert to the configured channels.
  3. Trafic redirection: Yuno will automatically redirect payments to the fallback provider options after detecting the approval rate falling below the threshold. In this scenario, you need to be aware of the following default behaviours:
    • A small percentage of traffic will remain processed through the original provider (original route) to monitor if the service is re-established.
    • While the approval rate performance from the fallback provider is better than the original provider, the monitoring process will continue.
    • If the fallback provider's approval rate falls below or matches the one from the original provider, the traffic is restored to the original route.
  4. Traffic restoration: Once the primary provider's performance improves, with a conversion rate above the set threshold, traffic will seamlessly revert to the original route.

This process ensures the system's adaptability and effectiveness, enabling the early detection of issues and the immediate implementation of measures to maintain optimal approval rates.

Monitoring process additional characteristics

The Monitor feature was developed to cover all situations your routes may face during operation. Below, you find complementary information covering specific scenarios related to the monitoring process.

  • In the event of interruptions from a provider, the traffic is redirected to the configured fallback provider. If that alternative provider experiences interruptions, the traffic is redirected to the second configured alternative provider if it's available.
  • If all providers on the route are down, traffic goes to the provider with the highest approval rate in the last measured time interval. Yuno system will continue to monitor all providers and move traffic dynamically, trying to provide the best approval rate until the providers' systems are reestablished.
  • The definition of down and recovered depends on user configurations.

The following list describes the system behaviour for different conditions:

  1. If a provider's approval rate falls below the defined threshold, traffic is redirected to the fallback for error handling.
  2. If the second provider also falls below the defined approval rate threshold, traffic is rerouted to the fallback for that provider's error handling (if available).
  3. If the approval rate of the third provider falls below the set threshold, payments will be routed through the provider with the highest approval rate, regardless of the specified threshold.

The image below describes the different scenarios described by the above list:

Configuring the Monitor

To configure the monitor, access the Routing tab in the dashboard and open an existing route. You can define a different approval rate monitor for each condition on your route. To configure an approval rate monitor, follow the steps below:

  1. First, you need to customize the payment route according to your preferred method.

  2. Select the necessary conditions and include providers for payment processing in each set.

  3. Click on the Monitors icon (bell icon) and configure the following data:

    • Time frame: Define the time period for measuring the approval rate.
    • Approval rate limit: Choose the approval rate limit, which will trigger the alarm and the actions.
    • Number of payments: You can choose between setting a minimum, a maximum, or a range for the number of payments within the time frame to trigger the condition. Use these options to avoid redirecting traffic due to an anomaly when a small number of payments are being executed.
    • Alert channels: Define if the alert notifications will be sent through email or Opsgenie.
    • Automatic traffic redistribution: Enable automatic traffic redirection whenever an alarm is triggered. This feature requires a configured fallback provider for "Error" and "Pause".
    • Percentage of traffic: Define the percentage of traffic that will remain with the original and currently unavailable provider for monitoring.
  4. Save the monitor changes, or save it as a template for future usage.

You can't create a monitor in published routes.