Print Reach Central v4.10.0 Release Notes Follow
Improvement:
On the Reports>Funding Summary>Funding Detail page, the MIS (Printer's Plan or Midnight) Payment ID and Customer Name were added to the report:
Improvement:
When a Job Link Quote is accepted by a customer and turned into an order the Approval Confirmation email will now include the Customer Name and Job Title.
Improvement:
When logged in as a Merchant user, in the Admin Settings > Communications>Logs recent email communications can be resent. As part of this process we have added a Bcc field to this page:
Improvement: When creating a new Security role, Print Reach Central will now alert you if the Role Name already exists and prevent the creation of duplicate role name.
Fix: When logged in as a Merchant user, when viewing the Reports>Transaction>Transaction Detail for a failed ACH transaction an error message was displayed. This is now fixed.
Improvement:
After editing a field on a Print Reach Central page, if you attempt to navigate to another section without saving the changes Print Reach Central will display the following alert:
Clicking No will keep you on the same page allowing you to save the changes. Clicking Yes will take you to the next section without saving the changes.
Improvement: The body of the Daily Transaction Report email now includes the ACH Returns total amount:
Fix: When running an Advanced Search from the Reports>Transations page the filtering fields are now responsive and displayed properly on a mobile device.
Improvement: The Country field on the Hosted Payment Page has been expanded to include additional countries:
Improvement: Updated Print Reach Central to operate on a newer version of Angular.
Improvement: The following security changes have been implemented:
-
We now reject non-Match ("N") for AVS and CVV; failed transactions will return a generic “Declined” message to the user.
-
We disabled the authentication key API when the Hosted Payment Page is disabled.
-
We upgraded to the enterprise edition of Captcha.
Fix: Corrected an issue where the payment receipt did not show the correct time. There were inconsistencies in the time shown on the receipt depending on where the receipt was created. This is now fixed.