> ## 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. # System Architecture > Technical deployment of FinShare (FIP) and FinPro (FIU) servers in the Account Aggregator ecosystem ## Moneyone Deployment Architecture The Moneyone Account Aggregator Stack comprises two core components that enable Financial Information Providers (FIPs) and Financial Information Users (FIUs) to securely participate in the AA ecosystem. Both modules are designed to interact with any RBI-licensed Account Aggregator, ensuring dynamic routing, compliance, and ecosystem-wide connectivity. Moneyone Architecture ## FinShare: FIP Server Architecture ### Purpose FinShare serves as the backend gateway for Financial Information Providers, enabling them to respond to consented data requests from Account Aggregators. It handles encryption, schema validation, account discovery, and secure data delivery while maintaining zero data retention. ### Components #### Execution Environment The FinShare server runs on a **Linux system** with the following technology stack: * **NGINX**: Reverse proxy and load balancer for handling incoming AA requests * **Node.js**: Application runtime for executing business logic and data processing * **FIP Core Module**: Handles schema validation, encryption, and AA protocol compliance * **FIP Admin Module**: Provides operational controls and monitoring dashboards * **Web XML Processor**: Transforms financial data into AA-compliant XML formats * **Data Processor**: Manages data retrieval, encryption, and payload construction #### Database Server A dedicated **MySQL Database** stores operational metadata across multiple schemas: * **Schema AA**: Account Aggregator meta-structures, entity registrations, and routing information * **Schema Users**: FIP-side user identity mapping and customer account associations * **Schema Linked Accts**: Records of discovered accounts and account linkage requests * **Schema Data Requests**: Audit trail of all data fetch requests and responses #### Communication Layer * **TCP/IP** protocol ensures secure communication between the execution environment and database layer * All inter-service communication is encrypted and authenticated #### Integration Point The **FIP API Gateway** receives encrypted data requests from Account Aggregators and orchestrates the entire response workflow, including: * Consent verification * Account discovery * Data encryption using customer-specific keys * Delivery confirmation and status updates *** ## FinPro: FIU Server Architecture ### Purpose FinPro provides Financial Information Users with a comprehensive interface to raise consent requests, retrieve customer-permissioned financial data, and analyze it securely. It abstracts the complexity of multi-AA integration and provides a unified API surface. ### Components #### Execution Environment The FinPro server operates on a **Linux system** with: * **NGINX**: Load balancing and reverse proxy for managing high-volume API traffic * **Node.js**: Runtime for handling consent workflows, data fetching, and analytics * **FIU Core Module**: Manages consent creation, AA routing, and data retrieval logic * **FIU Admin Module**: Operational dashboard for monitoring consent funnels and data flows * **Web XML Processor**: Parses and decrypts incoming AA data formats * **Data Processor**: Extracts, transforms, and delivers financial insights to FIU applications #### Database Server A **MySQL Database** maintains structured records across dedicated schemas: * **Schema AA**: Master registry of all integrated Account Aggregators and their health status * **Schema Products**: FIU financial product definitions used for consent template mapping * **Schema Consent Requests**: Comprehensive logs and lifecycle tracking of all consents * **Schema Data Requests**: Audit trail of FI fetch operations and statement-level data access #### Communication Layer * **TCP/IP-secured** communication between execution and database tiers * API authentication using OAuth2 client credentials flow #### Integration Point FinPro connects with the **FIU Application Layer**, which may include: * Credit scoring engines * Personal Finance Management (PFM) platforms * Wealth management systems * Lending and underwriting workflows The platform delivers decrypted, structured financial data ready for consumption by downstream analytics and decision-making systems. *** ## Account Aggregator Integration ### AA-Agnostic Design The Moneyone stack is designed to be interoperable across **all RBI-licensed Account Aggregators**, including: * Onemoney * CAMS Finserv * NESL * FinVu * OneMoney * PhonePe * Other licensed AAs ### Key Interoperability Features #### Consent Request Creation and Redirection FinPro generates AA-agnostic consent handles that can be fulfilled by any integrated Account Aggregator based on routing logic. #### Tokenized and Encrypted Data Flow Data flows from FIPs to FIUs via the selected AA, with all payloads encrypted end-to-end using customer-specific key pairs. #### Inter-AA Account Discovery Supports account discovery across multiple AAs, enabling customers to link accounts from different financial institutions seamlessly. #### Dynamic AA Routing The Smart AA Router evaluates FIP coverage, AA health metrics, and routing preferences to select the optimal AA for each consent journey. #### Seamless AA Addition New Account Aggregators can be integrated without rearchitecting existing systems, enabling plug-and-play ecosystem expansion. *** ## Technical Highlights ### Modular Linux-Based Architecture * Containerized deployment options for Kubernetes or Docker Swarm * Horizontal scalability for handling high-volume consent and data operations ### NGINX-Based Routing * Optimized load balancing for API traffic * SSL/TLS termination for secure external communication ### Node.js Runtime * Asynchronous processing for non-blocking I/O operations * High concurrency support for parallel consent and data workflows ### TCP/IP Secured Communication * Encrypted channels between execution and database layers * Role-based access control (RBAC) for internal service authentication ### MySQL-Backed Schema Store * Well-defined AA data models aligned with ReBIT specifications * Relational integrity for audit trails and compliance reporting ### Zero Data Retention Principle * Encryption at every stage (in transit and at rest) * No plaintext financial data stored on Moneyone servers * Compliance with RBI's data minimization guidelines ### Admin Modules with Operational Dashboards * Real-time monitoring of consent funnels and data fetch success rates * Webhook support for event-driven integrations * Audit trail logging for regulatory compliance ### Dynamic Interoperability with All Licensed AAs * Plug-and-play routing across multiple AAs * Automatic failover and re-routing during AA downtime * Unified webhook delivery regardless of underlying AA *** ## Deployment Considerations ### Hosting and Compliance * All deployments hosted in **India** to comply with data localization norms * Regular security audits aligned with RBI AA guidelines and IT Act 2000 ### High Availability * Multi-zone deployments for fault tolerance * Database replication for disaster recovery ### Monitoring and Observability * Centralized logging with ELK stack or equivalent * APM tools for real-time performance monitoring * Alerting for AA health degradation and routing failures ### Scalability * Horizontal scaling of Node.js workers for handling traffic spikes * Database sharding for managing large consent and data request volumes *** ## Summary The Moneyone architecture provides a robust, scalable, and compliant foundation for entities participating in the Account Aggregator ecosystem. By abstracting the complexity of multi-AA integration and providing modular, well-architected components, Moneyone enables faster time-to-market for both FIUs and FIPs while ensuring adherence to regulatory standards and best practices in data security.