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

# Smart AA Router

> Enterprise-grade traffic distribution and routing optimization across multiple Account Aggregators

## Overview

Moneyone's Smart AA Router delivers intelligent Account Aggregator traffic distribution logic that balances coverage, health metrics, and performance across multiple AAs. It enables Financial Information Users to configure, route, and optimize customer consent journeys using customizable routing strategies that maximize success rates and minimize drop-offs.

The router abstracts the complexity of managing multiple AA integrations while providing FIUs with granular control over routing preferences based on business priorities and customer experience goals.

## Core Value Proposition

### Maximize Data Availability

By integrating with multiple Account Aggregators simultaneously, the Smart AA Router ensures that customers can link accounts from any Financial Information Provider, regardless of which AA the FIP has integrated with. This dramatically increases consent success rates and data fetch coverage.

### Optimize Success Rates

The router continuously monitors Account Aggregator health metrics, FIP availability, and historical success patterns to dynamically select the AA most likely to complete the consent journey successfully.

### Minimize Customer Drop-offs

By automatically re-routing to alternative AAs in case of downtime or degraded performance, the Smart AA Router reduces journey abandonment and improves the overall customer experience.

### Reduce Single-AA Dependency

Multi-AA connectivity eliminates business continuity risks associated with relying on a single Account Aggregator. If one AA experiences downtime, traffic seamlessly shifts to healthy alternatives.

## Key Features

### 1. Multiple AA Integrations

The Smart AA Router supports simultaneous connectivity with all RBI-licensed Account Aggregators, including:

* Onemoney
* CAMS Finserv
* NESL Asset Data Limited
* FinVu (Cookiejar Technologies)
* PhonePe
* NADL (Perfios)
* Other licensed AAs

**Benefits:**

* Single API integration provides access to the entire AA ecosystem
* Unified webhook handling regardless of underlying AA
* Consistent consent artifact format across all AAs

### 2. Preferred AA Selection

FIUs can configure primary and fallback Account Aggregators based on strategic partnerships, commercial terms, or customer base alignment.

**Configuration Options:**

<AccordionGroup>
  <Accordion title="Manual Preferred AA">
    Explicitly specify the first-choice AA for all consent requests. The router will attempt to use this AA unless it fails health checks or routing criteria.

    **Use Case:** Contractual commitments with a specific AA partner
  </Accordion>

  <Accordion title="Dynamic AA Selection">
    Allow the router to automatically select the optimal AA based on real-time health metrics and FIP coverage analysis.

    **Use Case:** Maximizing success rates without fixed AA preferences
  </Accordion>

  <Accordion title="Use-Case-Specific Routing">
    Map different consent purposes or product journeys to specific AAs. For example, route loan journeys through AA-A and wealth management journeys through AA-B.

    **Use Case:** Optimizing for AA specialization or product-specific performance
  </Accordion>
</AccordionGroup>

### 3. Dynamic Threshold Configuration

FIUs have granular control over the routing decision parameters, enabling them to balance between coverage, reliability, and value.

#### Routing Thresholds

**FIP Coverage Threshold**
Define the minimum percentage of target FIPs that must be available on an AA before routing consent requests to it.

*Example:* If set to 80%, the router will only use AAs where at least 80% of the FIPs you need are active and responsive.

**AA Health Score Threshold**
Set minimum health score requirements based on recent success rates, uptime, and response times.

*Example:* Route only to AAs with >95% uptime and \<5% failure rates over the past 24 hours.

**Value per Transaction**
Assign weight to AAs based on expected conversion rates, customer experience quality, or commercial considerations.

*Example:* Prioritize AAs that historically yield higher data fetch success rates for your customer base.

#### Configuration Interface

All thresholds are configurable via the FinPro admin portal without requiring code changes or redeployment.

### 4. Dynamic Evaluation Duration

The Smart AA Router continuously re-evaluates routing decisions based on updated metrics and health data.

**Configurable Evaluation Windows:**

<CardGroup cols={2}>
  <Card title="Real-Time Monitoring" icon="clock">
    Continuous health checks every 1-5 minutes to detect AA or FIP outages
  </Card>

  <Card title="Rolling Window Analysis" icon="calendar">
    Analyze success rates over 1-hour, 6-hour, or 24-hour windows to identify trends
  </Card>

  <Card title="Scheduled Re-evaluation" icon="rotate">
    Periodically reassess routing strategies (e.g., daily, weekly) based on aggregate performance
  </Card>

  <Card title="Event-Driven Updates" icon="bell">
    Immediately adjust routing when AA status changes or new FIPs come online
  </Card>
</CardGroup>

**Re-routing Triggers:**

* AA downtime detected
* FIP unavailability on primary AA
* Success rate drops below threshold
* Customer-specific routing preferences (e.g., VIP customers)

### 5. Out-of-the-Box Efficiency

The Smart AA Router ships with pre-built routing logic based on Moneyone's operational experience across millions of consent journeys.

**Default Routing Strategies:**

**Coverage-First Strategy**
Prioritizes AAs with the highest number of integrated FIPs to maximize the likelihood of successful account linking.

**Health-First Strategy**
Routes to the AA with the best recent uptime and success metrics, even if FIP coverage is slightly lower.

**Balanced Strategy**
Combines FIP coverage, health metrics, and value per transaction in a weighted scoring model to select the optimal AA.

**Round-Robin with Failover**
Distributes traffic evenly across healthy AAs to balance load and maintain warm connections, with automatic failover to alternatives.

### 6. Automatic Re-routing on Downtime

When the primary AA experiences downtime or degraded performance, the router automatically redirects consent requests to the next best available AA without manual intervention.

**Re-routing Process:**

<Steps>
  <Step title="Health Check Failure">
    Router detects that the primary AA is unreachable or returning error rates above threshold
  </Step>

  <Step title="Fallback Selection">
    Evaluates secondary AAs based on FIP coverage and health metrics
  </Step>

  <Step title="Seamless Redirect">
    Routes the consent request to the fallback AA without exposing the failure to the end customer
  </Step>

  <Step title="Monitoring and Recovery">
    Continues monitoring primary AA health and automatically resumes routing when it recovers
  </Step>
</Steps>

**Customer Impact:**

* No visible errors or journey interruptions
* Consistent consent approval experience
* Higher overall success rates

### 7. Multi-AA Coverage Insights

The FinPro admin portal provides real-time visibility into FIP availability across all integrated Account Aggregators.

**Dashboard Features:**

* **FIP Coverage Matrix**: View which FIPs are available on each AA
* **AA Health Status**: Monitor uptime, latency, and error rates per AA
* **Routing Distribution**: Analyze traffic allocation across AAs over time
* **Success Rate Comparison**: Compare consent approval and data fetch success rates by AA

## Configuration and Setup

### Step 1: Enable Multi-AA Integration

Contact Moneyone to enable additional Account Aggregator integrations beyond the default AA. Moneyone handles all technical setup, entity registration, and testing.

### Step 2: Define Routing Preferences

Configure routing strategy in the FinPro admin portal:

1. Navigate to **Settings → Smart AA Router**
2. Select routing mode (Preferred AA, Dynamic, Use-Case-Specific)
3. Set FIP coverage and health score thresholds
4. Assign value weights to AAs if using weighted routing

### Step 3: Test in UAT Environment

Simulate consent journeys across all configured AAs to verify routing behavior:

* Create test consent requests with various product templates
* Monitor routing decisions in the admin dashboard
* Validate automatic failover by simulating AA downtime

### Step 4: Monitor and Optimize

After go-live, continuously monitor routing performance and adjust thresholds based on observed metrics:

* Review success rates per AA weekly
* Adjust thresholds if drop-off rates increase
* Update preferred AAs based on commercial agreements or customer feedback

## Benefits

### Enhanced Customer Experience

**Reduced Journey Drop-offs**
Automatic failover ensures customers can complete consent approvals even when the primary AA is unavailable.

**Faster Response Times**
Routing to the healthiest AA minimizes latency and improves perceived performance.

**Higher Success Rates**
Maximizing FIP coverage increases the likelihood that customers can link all desired accounts.

### Operational Efficiency

**Automated Traffic Management**
No manual intervention required during AA outages or degraded performance.

**Self-Healing Architecture**
Router automatically recovers when AAs come back online, reducing operational overhead.

**Centralized Monitoring**
Single dashboard for tracking multi-AA health and performance.

### Business Continuity

**No Single Point of Failure**
Multi-AA connectivity eliminates business risk from single-AA dependencies.

**Flexible Commercial Negotiations**
Ability to shift traffic between AAs provides leverage in commercial discussions.

**Future-Proof Architecture**
Seamlessly add new AAs as they launch without redesigning integrations.

## Use Case Examples

### Scenario 1: Lending Platform Maximizing Coverage

**Objective:** Ensure maximum customer reach by integrating with multiple AAs

**Configuration:**

* Enable all available AAs
* Use Coverage-First routing strategy
* Set FIP coverage threshold at 90%

**Outcome:** 25% increase in consent approval rates due to broader FIP availability

### Scenario 2: Wealth Manager Optimizing for Reliability

**Objective:** Prioritize stable, high-quality data delivery over maximum coverage

**Configuration:**

* Preferred AA set to most reliable partner
* Health score threshold at 98%
* Re-evaluation window set to 1 hour

**Outcome:** 99.5% uptime with minimal customer-facing errors

### Scenario 3: Fintech Balancing Cost and Performance

**Objective:** Route traffic based on commercial agreements while maintaining quality

**Configuration:**

* Use-case-specific routing (loan = AA-A, investments = AA-B)
* Value per transaction weights assigned per AA
* Round-robin for non-critical journeys

**Outcome:** Optimized cost structure while maintaining >95% success rates

## API Integration

The Smart AA Router operates transparently behind FinPro's consent APIs. FIUs do not need to modify integration logic to leverage multi-AA routing.

**Consent Request APIs automatically leverage the router:**

* `/v2/consent/request`
* `/v3/consent/request`
* `/v4/consent/request`

**Router selection is returned in API responses:**

```json theme={null}
{
  "consentHandle": "5eada97a-9852-4227-9558-45849b2800a3",
  "redirectUrl": "https://aa-provider.com/consent/...",
  "selectedAA": "onemoney",
  "routingReason": "health_score_optimal"
}
```

## Best Practices

<AccordionGroup>
  <Accordion title="Start with Default Routing">
    Use Moneyone's pre-configured routing logic initially, then optimize based on observed performance.
  </Accordion>

  <Accordion title="Monitor AA Health Weekly">
    Review health metrics and success rates regularly to identify trends and adjust thresholds.
  </Accordion>

  <Accordion title="Test Failover Scenarios">
    Periodically simulate AA downtime in UAT to ensure failover mechanisms work as expected.
  </Accordion>

  <Accordion title="Communicate with AA Partners">
    Share routing decisions and performance feedback with AA partners to collaboratively improve ecosystem quality.
  </Accordion>

  <Accordion title="Balance Coverage and Reliability">
    Avoid overly aggressive coverage thresholds that may route to less reliable AAs. Find the balance that works for your customer base.
  </Accordion>
</AccordionGroup>

## Support and Documentation

<CardGroup cols={2}>
  <Card title="Admin Portal Guide" icon="book" href="/guides/admin-portal">
    Learn how to configure routing preferences
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/consent/request-v2">
    See how routing integrates with consent APIs
  </Card>
</CardGroup>

For questions about Smart AA Router configuration or troubleshooting routing issues, contact Moneyone support through the FinPro admin portal.