Production Release: 7/9/26

Improved visibility into fuzzy matching decisions

What changed

We added new events related to fuzzy matching to the Logs for Gov ID + Selfie Match. These events are now available in Logs in the Admin 2.0 Transaction Details Report and in Transaction Events in the legacy Admin Transaction Details Report.

The new log details can include the expected passing threshold, the matching logic used, match results for each attempted name comparison, and the final match ratio when applicable.

Why it matters

Fuzzy matching can influence whether a transaction passes or fails. By surfacing more detail about how a match was evaluated, these logs make it easier to troubleshoot unexpected outcomes, investigate customer support questions, and understand the reasoning behind a match decision.

What you need to know

• No action is needed on your part.
• This update adds visibility in transaction reporting; it does not change the matching logic or customer workflow behavior.

Enhanced automated failover for Resilient Checkers

What changed

We enhanced the internal automation that powers automated failover for Resilient Checkers, reducing operational complexity while preserving the same customer-facing behavior.

Why it matters

This strengthens the resilience benefits of Resilient Checkers by making failover easier to maintain and scale as additional providers are supported.

What you need to know

• No action is needed on your part, though if you're interested in implementing Resilient Checkers, reach out to your account team.
• There are no API or integration changes for customers.

Additional platform and admin updates

This release also includes internal admin and platform updates that improve operational efficiency, reporting performance, and platform maintainability without requiring customer action.