2026-05-07
We have added a Total Order Count to all views in the Case Queue. This is a real-time counter that displays the total number of orders awaiting review. This helps you:
-
Optimize resource planning by instantly evaluating overall volume to manage analyst workloads and ensure high-priority cases are addressed during peak times.
-
Track volume by viewing both your Current Saved Views and the Total Count of Orders to monitor queue health.
To view the Total Order Count, go to Case Management > Case Queue.
2026-05-29
We have updated our authentication services and refreshed the sign-inexperience to provided a more cohesive navigation across environments. This update introduces the following changes to your sign-in experience:
-
Password reset required: Upon your first sign-in after the migration, you are prompted to reset your password. New, specific password complexity requirements are enforced during this process. Refer to Signing in for the first time.
-
Multi-Factor Authentication (MFA) re-enrollment: All users must re-register your preferred MFA method using either email or text (SMS). This does not apply to organizations that have implemented Single Sign-On (SSO).
Refer to Sign in with Multi-Factor Authentication for instructions on how to re-register.
-
Active sessions: If you are actively using the portal during an authentication update or cutover, your session is terminated and you are signed out.
-
Access to environments: Production and sandbox now require separate sign-in authentications. The process is the same for signing in to either environment.
Too many failed login attempts will lock your account.
What's new?
-
Streamlined login: A new log-in interface for production and sandbox environments for easier navigation.
-
Improved organization selection: If you have more than one organization, a new welcome page displays after authentication. You can quickly view invitations and switch between organizations.
-
Upgraded security: To ensure the highest level of account security, users without a custom SSO solution must reset their password and set up MFA again the first time they log in.
2026-05-29
We have updated our token retrieval endpoints and established enforcement of rate-limiting policies to ensure system stability and security. This update modifies how bearer tokens are retrieved and managed in Kount 360. We have established a new authentication endpoint for all future integrations, provided a transition timeline for existing users, and introduced automated rate-limiting enforcement through our new identity provider infrastructure.
What's new?
-
New Kount 360 token endpoint: We have introduced a new endpoint for retrieving bearer tokens. This endpoint replaces the legacy infrastructure and provides enhanced security architecture and token management.
-
User interface updates: The user interface for API keys in Admin has been updated. It now displays the new endpoint details to help technical teams verify their configurations.
-
Rate-limiting enforcement: To prevent system degradation caused by excessive token requests, rate limits are now actively enforced with our new identity provider.
-
Standardized request thresholds: The recommended token request rate is now set to 20 requests per minute.
Action required
All existing customers must start using the new token endpoints in their current integrations. All token updates must be completed by February 15, 2027.
Your technical teams must audit their authentication workflows to ensure token request volumes remain within the recommended threshold of 20 requests per minute. Sustained volume increases or sudden surges above this limit will trigger rate limits. When a limit is exceeded, the system returns a 429 (Too Many Requests) HTTP status response.
Updated developer documentation with the token endpoint updates are now available on the Developer website.
For technical assistance or questions regarding endpoint updates, contact support.kount.com.
Effective: 2026-05-07
Omniscore within Kount 360 has been updated. This update leverages expanded historical intelligence and real-time telemetry to increase detection accuracy.
Key Changes / Outcomes
-
Data integration: The model now incorporates a larger volume of historical data aggregates, enabling more robust longitudinal pattern analysis.
-
Pattern correlation: The model now implements an improved synthesis of historical trends against current transaction data to identify emerging fraud vectors.
-
Performance metrics: Production data now indicates an increase in fraud detection precision and a measurable reduction in the aggregate chargeback rate.
Impact
The updated model provides a higher rate of fraud capture while reducing the volume of chargebacks for customers.
Implementation
-
Existing users: If your current Kount 360 policies leverage Omniscore, no action is required. Your policies will automatically use the new model.
-
New users: If you are not currently utilizing Omniscore, you can begin incorporating these capabilities by updating your workflow policies.
Comments
0 comments
Article is closed for comments.