Our solution adds a digital signature to the inward or outward message. Any attempt to change the message after it has been created will be detected resulting in the message being rejected and highlighted for user inspection.

The LAU value depends on 2 16 digit keys that are concatenated to provide a key for the encryption algorithm that uses Hash-Based Message Authentication Code (HMAC) Secure Hash Algorithm (SHA-256) signatures.

The symmetric key is shared by both the back-office application and Alliance Access. For any Incoming SWIFT with an LAU in the header Aquila will verify that the LAU is correct and reject messages where there is no LAU. Similarly the SWIFT device will check the authenticity of the LAU on messages created by our system