PayConex - 12.9.2021

This release includes enhancements for PayConex email notifications, Real-time ACH Verification, and new Recurring Schedule options for Hosted Payment Forms.

New Features and Enhancements

PayConex Email Notification Changes

We improved our Forget/Reset Password communication emails for a better user experience for our merchants.

Real-time ACH Verification Enhancements

In the last release, we added support for Real-Time ACH Verification. With this release, we have added the ability to include real-time verification messaging and statuses in Transaction Details, Custom Reports, and the Reporting Services API.

We have also added the ability to receive these values on Hosted Payment Form responses.

Merchants who wish to force or bypass real-time ACH verification can set the validate_ach_account parameter to true or false.

New Recurring Schedule Options for Hosted Payment Forms

We have added the ability for merchants to select what recurring schedule options they would like to allow their customers to choose during setup.

Manual API Based Settlement added for Chase Paymentech.

We have added the ability for merchants using Chase to request via the API to settle their open batches. This requires automatic settlements to be disabled in the account settings.

Bug Fixes

Issue # 1

There was an issue related to making multiple partial refunds that would result in an amount error. This issue has been resolved.

Issue # 2

When sending a request to the Reporting Services API that returned no results and using either XML or CSV data formats, the response was formatted incorrectly as a string. Now the Reporting Services API will respond in properly formatted XML or CSV data.

Issue # 3

We had a regression on the PayConex user interface whereby an ACH transaction could not be reissued if the transaction type was CREDIT. This issue has been resolved.

Issue # 4

There was an issue on Transaction Detail pages for recurring transactions where clicking the link to view the recurring schedule did not route to the proper page. This has been corrected.