OmniMessaging Functional Description 8.3

OmniMessaging Functional Description
07/22/04 Opsol Integrators Inc. Confidential and Proprietary Page 51 of 68
16 ACH / EDI Support with Digital
Signatures X.509
(To purchase this additional module please contact your HP Sales Representative)
16.1 Secure email is defined as
1) The value-bearing portion, or the entire body, must be encrypted.
2) The value-bearing portion, or the entire body, must be authenticated via digital
certificate.
16.2 Some requirements for Secure email
1) Customers want to be able to send us financial transactions using secure email.
2) They want transaction returns via secure email. (Returns are transaction rejects).
3) They want to receive reports via secure email.
4) There might also be a need to receive confirmations (i.e. "yes, we received such-
and-such") via secure email.
5) Web application screens allow users to request a report delivery via email.
6) Replace large daily fax transmissions with email.
8) Must have a programmatic API to email support to legacy applications.
9) Must function through proxies for digital certificate handling.
10) Must interface with other mail servers for receiving and transmitting email.
16.3 Encrypted and digitally signed emails
OmniMessaging supports Secure Messages with full support for PKI certificates. An
end user prepares the message using their standard email client such as Outlook or