EastNets awarded 2011 SwiftReady Alliance label

Source: EastNets

EastNets, the leading global provider of compliance and payment solutions and services, announced today that four of its products have been awarded the 2011 SWIFTReady Alliance Add-on label by the Society for Worldwide Interbank Financial Telecommunication (SWIFT), the operator of the global financial messaging network.

As the operator of the financial messaging network, SWIFT supplies standardized and secure messaging services to more than 9,000 financial institutions in over 200 countries worldwide. The SWIFTReady Application award evaluates products based on their ability to provide SWIFT users with the technology and functionality required to fully integrate with the SWIFT community.
"As a long time strategic partner of SWIFT we are committed to providing our customers with comprehensive solutions that adhere to the highest of standards," said Hazem Mulhim, CEO of EastNets. "The SWIFTReady label is a mark of excellence and an important validation of our ongoing efforts to innovate and enhance our solution portfolio to the financial services community."
The following EastNets products passed the stringent support criteria for SWIFT standards, messaging services and interface connectivity, affirming full compliance with the development guidelines and good coding practices laid down by the SWIFT Alliance Developer Kit:
• en.SafeWatch Filtering market leading anti-money laundering watch list screening solution provides real-time blocking, supporting all lists including OFAC and PEP, and offers direct SWIFT message screening;
• en.Reporting enables SWIFT Alliance users to benefit from one central view to investigate, monitor and report all FIN and XML traffic within one environment;
• en.Duplicate Detection enables SWIFT users to save significant time and money by preventing the emission of duplicate payments or other FIN messages sent to correspondents or received from correspondents;
• en.Recovery enables SWIFT users to restart operations within minutes after an outage instead of hours.

Comments: (0)