The goal of DDA is to prevent emission of outgoing duplicate messages and processing of incoming ones. The duplicate detection logic is based on message content, comparing each new message to the traffic of a configurable number of previous days, independently from the SWIFTAlliance live message file size. DDA is highly configurable; both message types and fields to be involved in detection are user-definable.

DDA Benefits

Fine-tuned Detection

• 4 return-codes:
  - Unique
  - Real Duplicate
  - Duplicate
  - Duplicate of NAKed
• User definable history period for comparison
  
• Increase security
• Suppress the risk of executing duplicate operations
• Suppress the risk of duplicate payment emission
• Reduce costs, avoid penalties
  - Cost to recover double payments
  - Limits unnecessary PDE

Characteristics

• Prevent emission of duplicate messages by comparing with message history on user selected fields
• Detect incoming duplicate messages and assigns them a “duplicate” status for further processing in SWIFTAlliance routing
• History independent from SWIFTAlliance live database capacity
• DDA is highly configurable, based on the message type and on all fields for each type