Supercharge your messaging-based financial workflows

Symphony Messaging is purpose-built for financial workflows with standard end-to-end encryption, an intuitive capital markets interface, open APIs and low-code bot development, integrations with third party applications, and a robust community of financial professionals at your fingertips – helping drive connectivity, prioritize security, and provide stability for your workflows.

Connect with over 550,000+ global users from 450 institutions on Symphony Messaging. With Federation, extend secure and compliant connectivity to any user of popular messaging channels including WhatsApp, WeChat, SMS, and LINE.

You can download the desktop application here.

Because of Symphony Messaging’s open APIs and low-code development, you can create custom workflows to fit the needs of your firm. Visit the Symphony Developer site or view demos of our clients’ innovations from Symphony Innovate 2024 here.

Symphony Messaging offers the Content Export Bridge (CEB) which can be used to export content through ad-hoc or scheduled downloads and send to on-premise or cloud-based systems where it is decrypted and loaded into your compliance and archiving systems, ensuring your content retention and passive compliance requirements are met.

Yes, Symphony Messaging is available for Android and iOS users. Follow either link to the iOS or Google Play App Store and click install. For more help visit our downloads page here.

Reach out to [email protected] or access our help center here.

Symphony uses various safeguards to ensure data confidentiality. Here are several data confidentiality breach scenarios and how Symphony would respond to each.

If a data breach occurs on Symphony servers, only encrypted data would be accessible. The data remains unexploitable without authorized access to the cryptographic keys. All data transmitted through the Symphony Messaging platform is end-to-end encrypted, and the keys are securely stored separately within the customer’s key management system.

Therefore, the data’s vulnerability is contingent upon the breach of both the Symphony servers and the customer’s key management system.

The inherent architecture of Symphony Messaging precludes access to encryption keys and mandates data encryption prior to transmission to its servers. There is no technological mechanism by which Symphony can disclose conversation content.

Consequently, regulatory authorities and agencies need to seek conversation content directly from the participants in that discussion stream.

This mirrors the scenario involving the subpoenaing for access to conversation content. Given that Symphony lacks access to encryption keys, a malicious actor would only be able to acquire encrypted data. Data decryption would necessitate the exploitation of the customer-owned key management system.

The cryptographic isolation and secure encryption key distribution protocol prevents a non-participant from accessing the conversation encryption key. This rule applies even if the non-participant is an authorized Symphony Messaging user.