We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Overview
Badge v1.94.0 will be released on 2/26/2026. Clients will automatically receive this update – no action is required.
New & Improved
Updated Multi-Factor Authentication (MFA) Messaging
MFA text messages have been updated to reflect suite-level authentication by referencing “Card Integrators” instead of Badge.
Platform Infrastructure Update: [cardintegrators.com] Consolidation
We’ve consolidated application resources under [cardintegrators.com] to simplify navigation, improve session handling, and streamline system configuration. This update improves authentication consistency and overall platform organization.
Key updates include
Portal login will be available at: https://cardintegrators.com/account/login
Badge will be available at: https://www.cardintegrators.com/badge
What stays the same
To ensure a smooth transition, existing portal2 links will remain active for the foreseeable future and will automatically redirect to the new URLs.
What we recommend
Portal login will be available at: https://cardintegrators.com/account/login
Badge will be available at: https://www.cardintegrators.com/badge
What we recommend
If your organization uses network allowlists, bookmarks, or scripted integrations, please take a moment to:
Stability & Reliability
Improved Login Session Handling
Fixed an issue where users could encounter a CSRF error after remaining on the login page for an extended period.
Input Records Connection Selection Fix
Fixed an issue where selecting one connection during Input Records configuration could automatically select other connections associated with the same provider.
0 Votes
0 Comments
Login to post a comment