Monetra 8.11.1 has been released and is available for upgrade. This release contains no security fixes, but it does contain an update that is necessary for First Data (Datawire) customers in order to maintain functionality.
If you are a First Data customer, and have not updated to this release before Datawire releases their fix (the fix release date has not yet been announced), you will no longer be able to process credit cards until you update to Monetra version 8.11.1 or newer.
Full release notes from Monetra are below:
Monetra 8.11.1 released
October 7, 2019
Effective 10/07/2019
Monetra 8.11.1 has been released to the public and is a maintenance release.
This release is highly recommended for all users of Monetra and should be considered the most modern and stable release available.
Changelog
Database Schema: v4.10 (compatible with v4.0)
Fixes:
• First Data's Secure Transport (Datawire) will be deploying a change for case sensitivity in its messaging protocol, and one of the elements had the wrong case in the messaging (as has been the case for over 10 years). When Datawire deploys this change, all prior versions of Monetra will stop working.
• TLSv1.3 could stall due to buffered (but unprocessed) data immediately upon successful connection, due to TLSv1.3 having fewer round trips. This will now deliver an event on such an occurrence to properly process the buffered data.
• Elavon would failed to structure a transaction when referencing a token without Card on File framework data, which is the case for all legacy tokenized cards.
• Recurring purge expired had an SQL query malformation.
• Recurring History was not appending the token checksum to the report so the tokens were missing the last digit.
• REST API fixes plus additional logging of the method and endpoint.
• Push Notifications list users has an SQL query malformation.
• Account Updater was erroneously trying to evaluate an edit of a non-eligible token.
