Effective: 2024-07-31
We now offer Service Provider Initiated Single Sign-On (SSO) for Kount 360. You can configure SSO by using SAML or OIDC. Once activated, after entering your email on the Kount 360 sign-in page, your organization’s domain is detected, and you are directed to the appropriate identity provider. After authenticating through your identity provider, you are returned to the Kount 360 portal.
Effective: 2024-07-11
We implemented a new way to organize users in Kount 360. The portal might look different for some users, but the necessary functionality for each role still exists. User Management is still sectioned by Users and Roles. You can switch between either section and then sort, filter, and search for users or roles.
For more information on User Management, go to Managing Users.
Effective: 2024-07-31
The search feature has been updated in Policy Management which allows you to search for conditions in All Groups. The search feature helps reduce the time it takes to find conditions when creating a segment or policy.
Effective: 2024-07-31
Location Accuracy has been added as a condition to Policy Management for Login and New Account Opening event types. This condition defines the accuracy of the device location with the following criteria:
-
Pinpoint — For customers who need exact locations. This requires the Native Mobile SDKs and Location Services to be enabled. This only exists for Native Mobile SDK collections where the GPS is enabled.
-
City level — This is based on IP information and is considered accurate to the city. If there is a proxy, we pierce it in order to find the IP address closest to the customer and their internet connection.
-
Country level — Country level accuracy happens when we know the location information is being obfuscated to the country/timezone level.
-
Unverified — The location is considered unreliable and should not be considered accurate. This could be because a known proxy was used that we could not pierce or a TOR network was involved.
For more information about this condition, refer to Device Conditions on our support site.
Effective: 2024-07-31
Distinct IP Address per Device, a new velocity, has been added to Policy Management for Login and New Account Opening. This condition counts the distinct IP addresses for successful and failed login attempts for a given device. For more information about this condition, refer to Network Conditions on our support site.
Effective: 2024-07-31
Velocities now link by Payment Token (PTOK) transactions more often. Prior to this fix, not all transactions associated with the same PTOK were being linked as expected.
Effective: 2024-07-31
An issue has been fixed in relation to the VIP address search feature. An error no longer displays when selecting the Billing or Shipping option in the Filter addresses menu. Prior to this fix, the only way to view the correct filter results and not encounter an error was to select Any.
Effective: 2024-07-31
The following Ekata rule conditions have been deprecated:
-
IP Address to Billing Name
-
IP Address to Shipping Name
This change is in response to a decision made by Ekata to improve their fraud prevention capabilities.
Effective: 2024-07-31
A modulemap file has been introduced to the iOS library. The modulemap file lets you import directly into your iOS file and eliminates the need to integrate a bridging header into your projects. Existing implementations with a bridging header will continue to function without issues.
Effective: 2024-07-31
We deployed a minor change for the Web Client SDK (2.1.0) that improves SDK reporting. The Web Client SDK now reports to our servers how the SDK is integrated, bundled or module, and where the SDK came from, NPM or GitHub. The newly reported information provides us with SDK usage data to improve future development and troubleshooting.