Synchronous and Asynchronous Receipts
Synchronous Receipts
The following synchronous options are available:
Sync Signed A signed, synchronous receipt is requested from the trading partner for each message. This is automatically selected if you check Non Repudiation of Receipt. An Initiator asks for signed or unsigned sync receipts if it wants to receive the receipts in the same HTTP connection so that it does not have to wait for the receipts to arrive on a separate connection.
Sync Unsigned An unsigned, synchronous receipt is requested from the trading partner for each message.
For synchronous receipts, the receipt should be returned by the trading partner in the reply to the HTTP request.
For more information on receipts, see Message Disposition Notification Receipts.
Asynchronous Receipts
The following asynchronous options are available:
Async Signed A signed, asynchronous receipt is requested from the trading partner for each message. An Initiator asks for signed or unsigned async receipts if it wants to receive the receipts in a separate HTTP connection. After the Responder gets the document and verifies the content for integrity, it opens a connection back to the Initiator to send out the receipt that was requested.
Async Unsigned An unsigned, asynchronous receipt is requested from the trading partner for each message.
For asynchronous receipts, the trading partner could return the receipt to another URL. MAILTO, HTTP, and HTTPS URLs are supported.
For more information on receipts, see Message Disposition Notification Receipts.