Are you a current Kount customer? If so, please select which AWC Environment, Production or Sandbox

If not, please contact our sales department for more information.

Home > Developer Resources > Software Updates and Release Notes > Release Notes > Release Notes 7.8.1

Release Notes 7.8.1

Kount Complete

7.8.1 Release Notes

October 24, 2017 | updated October 31, 2017

Event Notification System (ENS) Update

 

Infrastructure Improvements

Kount continues to make enhancements to its core infrastructure for improved reliability and performance. In this release, the Event Notification Systems (ENS) has been updated.

 

Merchants who currently subscribe to the ENS may notice some minor changes in the composition of ENS message batches and the formatting of the XML content. In addition, the retry logic that the ENS uses when delivery failures occur has been modified. These changes are described in detail below and are not expected to impact existing implementations.

 

Merchants who do not currently subscribe to the ENS will not be impacted.

 

ENS subscribers can expect the following: 

 

  1. Batched events have been modified to better handle load. Batch compositions will appear slightly different than in previous versions of ENS, but outputs should not be impacted. Parsing issues may occur for merchants who are not currently using an XML-compliant parser. If parsing issues occur, merchants should ensure they are using a modern XML parser.
  2. Delivery failures and retry handling has been simplified and clarified. Kount will attempt to deliver every batch to the customer URL four times in rapid succession (one second plus any http delay between each attempt). After a fourth failure to deliver, the failing message will go into an hourly retry. Attempts to redeliver will continue for up to three days, after which attempts will cease.
  3. To improve ENS performance and scalability, Kount has switched to a newer XML library. The XML payload will display slight formatting differences, as follows, but will remain 100% XML compliant.
  • The XML will have a consistent two space indent at each tier of the XML.
  • Empty XML tags will no longer be self-closing (i.e. <old_value/>) but will instead use the slightly more verbose closing tag (i.e. <old_value></old_value>).

 

Below are examples of the current payload and the new payload:

 

Old Message

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<events merchant="000000" total="1">

<event>

  <name>WORKFLOW_NOTES_ADD</name>

  <key order_number="AAAAAA" site="TEST">ABCDE123456</key>

  <old_value/>

  <new_value reason_code="">SYSTEM: New Account</new_value>

  <agent>name@kount.com</agent>

  <occurred>2017-03-03 23:59:26.626254</occurred>

</event>

</events>

 

New Message

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<events merchant="000000" total="1">

  <event>

    <name>WORKFLOW_NOTES_ADD</name>

    <key order_number="AAAAAA" site="TEST"> ABCDE123456</key>

    <old_value></old_value>

    <new_value reason_code="">SYSTEM: New Account</new_value>

    <agent>name@kount.com</agent>

    <occurred>2017-03-03 23:59:26.626254</occurred>

  </event>

</events>

 

 

You must to post a comment.
Last modified

Tags

Classifications

This page has no classifications.