{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/6029f997c39849bcb652651a511c038b\" frameborder=\"0\" width=\"1728\" height=\"1296\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1296,"width":1728,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1296,"thumbnail_width":1728,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/6029f997c39849bcb652651a511c038b-3e48973dd06d8252.gif","duration":401.983,"title":"UbaActimize AML: Enhancing Anti-Money Laundering Efforts in Banking 🏦","description":"In this video, I present our project called UbaActimize AML, which is an anti-money laundering application designed for banking organizations. The application helps screen account openings and transactions to reduce fraud levels. We’ve built this using a microservices architecture, integrating various services and a portal UI while ensuring proper documentation and error handling.  This project is a .NET 8 Blazor WebAssembly solution focused on real-time data synchronization for Anti-Money Laundering (AML) processes, specifically for Customer Due Diligence (CDD) operations. The core of the solution revolves around the serialization and management of complex customer and account data structures, as seen in the CddProfileData.cs file. The data models are meticulously designed to map to XML schemas, supporting integration with external systems that require structured data exchange, such as regulatory or compliance platforms. The use of attributes like [XmlRoot] and [XmlElement] ensures that the data can be serialized and deserialized accurately, maintaining fidelity with the expected XML formats.\nThe solution models a wide range of entities relevant to AML and CDD, including parties (customers), accounts, addresses, emails, phones, services, loans, and various relationships between these entities. Each class is tailored to capture detailed information, such as identification documents, business units, risk scores, and compliance statuses. The design supports extensibility and strict typing, with required fields and optional custom fields to accommodate evolving regulatory requirements. The inclusion of methods like ToString() for XML serialization demonstrates a focus on interoperability and auditability, which are critical in financial compliance scenarios.\nGiven the presence of validators and controllers in the open files, the project likely exposes APIs for receiving, validating, and processing CDD data requests. The validators ensure that incoming data adheres to business and regulatory rules before being processed or persisted. The controller layer orchestrates these operations, serving as the entry point for client applications or other services. Overall, the solution is architected to provide robust, compliant, and scalable handling of sensitive financial data in a modern, web-based environment, leveraging Blazor WebAssembly for rich client-side experiences and .NET 8 for backend reliability."}