Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Gateway Control File processor now returns more information about exceptions to make the troubleshooting easier.

  • Added support for the Tag DF5E Quasi Cash Maximum Amount in Application Profiles (E6).

  • Added support for the Tag DFF5 Quasi Cash Minimum Amount in Application Profiles (E6).

  • NexoFastConfigurationParser no longer uses dynamic libraries and is now statically linked.

  • DGNP, DCCQ and DCRR have been added to the messages to send in the Acquirer Protocol Parameters section of the POI configuration.

    • Action required: A configuration needs to be redeployed to add these new messages.

  • Introduction of the API V02. See the documentation on the page API V02. The introduction of this new version of the API have no impacts on the existing one. In the future, some functionality will be available in both version of the API. It is encouraged to use or migrate to version 2.

  • With the introduction of the version 2 of the API, it is now possible to archive the POI messages and the application log entries based on a retention period given in days.

    • Action required: Call the two new API methods as described in the documentation. The database user given in the web application configuration file (.env) must have the MySQL access right FILE. The deployment strategy might need to be adjusted since the data is archived in file. These file should be preserved. More information is available in the API documentation.

  • Four new methods are available in the API V02. They return information about the POI profiles, and the Application Log Events. It worth noting that the POI profile methods returns almost all the related details which solves tickets ATHD-132 and ATHD-133.

...