ACHEFT transactions may showed Failed in CiviCRM but may in fact be Ok:BankAccept in iATSPayments - daily journal

[KarinG]

If an ACHEFT encouters a REJ:TIMEOUT - iATS Payments will reprocess and update the daily journal to a possible Ok:BankAccept (if successful), but not update the download/box journal (where you can download e.g. an entire month worth of data). There the response remains REJ:TIMEOUT.

The iATS Extension uses the download/box journal to verify ACHEFT in CiviCRM. So such contribution arrive with REJ:TIMEOUT - and hence we show contribution_status_id = 4 (Failed).

We've mentioned this inconsistency to iATS Payments and they are aware of the issue. They are actively working with their dev team to update the download/box journal as well.

In the mean time - keep a close eye on your ACHEFT Failed transactions; You can use the new Journal report: Create New Report from Template: iATS Payments Journal -> set you Filters -> Result string to Contains REJ - and you'll get:

Look for REJ:TIMEOUT -> and then check the iATSpaments.com daily journal to verify if it got Ok:BankAccept

[jitendrapurohit]

getting similar issues on ACHEFT payments for first recur contributions.

If journal has encountered a REJ:TIMEOUT, is it correct to set them as status_id = 4 in civicrm_iats_journal table?

As status_id is set to 4 here, next job "iATS Payments Verification" gets the status from the above table and updates the core civicrm_contribution status to Failed. See https://github.com/iATSPayments/com.iatspayments.civicrm/blob/master/api/v3/Job/Iatsverify.php#L126. We get a lot of failed records in civi which are actually accepted on iATS.

Is there any way to re-execute them and complete them in civi? Can this be considered as a bug which should not set status_id = 4 in civicrm_iats_journal table in case of a REJ:TIMEOUT error and wait for another job execution? @KarinG @adixon