iATS 1st Payments bug fix release

gistfile1.txt

The following 1stPay Gateway fixes have been released:

ACH Status 

Impact: Integrators using Rest API and ACH
Previously: ACH transactions were left in 'Pending' status, partners had to rely on whether a batch number was displayed to know if the transaction was settled
Now: ACH transactions will appropriately reflect as 'Settled' both in RestAPI Query and Transaction Center
 

Batch Number 

Impact: All Fifth Third merchants
Previously: Batches with fewer than 5 transactions were not displaying the batch number in Rest API / Transaction Center
Now: All batch numbers (retro and new) will display correctly, regardless of the transaction count in the batch
 

Webhooks

Impact: Webhooks subscription front end users
Previously: Users were not able to set up a specific End Point to receive notification for a specific merchant ID
Now: Users are able to assign an End Point to receive select notifications for a specific merchant ID
 

These releases noted below are now complete and fully functional within the 1stPay Gateway:

Fix

ACH transactions reflect as 'Settled' both in RestAPI Query and Transaction Center.
Batch numbers (retro and new) display correctly, regardless of the transaction count in the batch.
Webhooks - assign specific End Point for notifications for specific MIDs