I received a faulty alert. What can I do?

For Ethoca alerts specifically, occasionally our partnered banks send faulty data. Most commonly this happens with Ethoca alerts (RDR alerts are deployed differently which prevent the possibility of erroneous alerts). 

Since the data source for the Ethoca alerts are consumer banks its possible that the consumer bank sends a faulty alert. According to large data set the most common scenarios for faulty alerts are the following:

1. An alert for a failed transaction
2. An alert for an already disputed transaction
3. An alert for a previously refunded transaction

The majority of faulty alert categories are detected automatically if you are processing on a connected processor, however occasionally our detection algorithms will allow a faulty alert through. You may reject any faulty alert under the appropriate reason code and request a credit, which will be swiftly granted. It is our priority that you are never paying for useless data with Chargeblast.

Why does this happen?

Certain issuers are less compliant with operating procedures mandated and will send higher volumes of erroneous data. Most likely, the issuing bank has poorly implemented the alert datafeed and as a result sends superfluous data. In addition, the issuing feed is enriched via various other sources which occasionally will pick up a duplicate alert (though very rare as there's robust deduplication strategies in place). In our data set, 95% of Ethoca alerts are valid alerts. We routinely monitor erroneous alert transmissions and inform the banks accordingly.