Creating reports at regular intervals on how many of the transactions made at a merchant fail, and tracking them, is important for both the merchant and the institution.
For transactions initiated from a POS device that return an error, BKM error codes give us information.
Tracking transactions that return errors at merchants can provide the following advantages:
- Noticing errors caused by configuration in advance,
- Increasing merchant satisfaction when quick interventions are made,
- Preventing loss of turnover,
- Finding out whether there have been system outages,
- When errors come from on-us cards, it can also alert you to check your cards.
The situations above are cases where the transaction is initiated from the POS device and an error code is returned by the HOST.
You can also monitor system outages in other ways.
Which indicators should be monitored?
The failed transaction rate per merchant, the distribution of error codes, hourly volume and device-level problems can be monitored. Sudden increases may point to a problem such as a configuration error, a connection issue or a fraud attack.
If alert thresholds are set, the support team notices the problem before the customer complains. A regular report also offers value to the merchant.
It is recommended that the report be shared not only with technical teams but also with sales and operations teams.
