The detection can be configured per message type; indicating a list of fields to ignore, or on the contrary, by defining explicitly a list of matching fields to consider a message is duplicated.

Duplicate messages can be compared in the GUI, accepting or rejecting the duplicate.

Main Features

Main Features

Detection by Matching Fields

Enabling duplicates detection based on explicit fields instead of pairing the complete message. This can be used for example to detect possible duplicate payments based on receiving institution, currency and amount, regardless of other transaction details.

Detection by Ignored Fields

Enabling duplicates detection based on full text comparison but ignoring specific fields.
A use case scenario could be within an infrastructure where the reference fields are auto-generated by an interface, so a duplicate payment generated by a backoffice application could end up in two different messages with unique reference fields.

Verification GUI

The duplicate messages can be analyzed in the GUI, with the matching fields highlighted. The operator can then decide whether to accept or reject the message. If the message is accepted it will continue its processing flow right away.

Get it

Give it a try

Looking for pricing information? Want to try a demo?
Contact us indicating your company type and use case.

News

Products

Company

This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the cookie policy.
By scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.