We updated the descriptions of the following Image Alert List (IAL) reason codes to more clearly reflect face-matching results across previous verifications: R859, I859, and I860.
There is no change to Image Alert List logic or decisioning behavior. No integration or configuration changes are required. For reason code definitions, see the reason codes in the RiskOS™ Dashboard.
We have added incremental data across vendors, increasing coverage for email addresses, phone numbers, physical addresses, and SSNs, and improving the accuracy of identity signals.
As more identity history becomes available, the firing frequency of some reason codes shifts:
For reason code definitions, see the reason codes in the RiskOS™ Dashboard.
Why it matters:
These improvements increase the predictiveness and accuracy of these reason codes, enabling you to make more confident and precise decisions.
You can now verify a document barcode in a single Evaluation API call. Send the decoded barcode payload as a base64-encoded string in the new barcode_payload field on the individual's docv data, instead of uploading the barcode separately and then evaluating it. This removes a network round trip and its underlying storage step from the verification path, which lowers overall latency.
This change is optional and additive. Your existing two-call upload flow continues to work unchanged, and only the barcode text is affected — front, back, and selfie images still use the existing upload flow.
To adopt the single-call flow, see the DocV Integration Guide.
We released the following new reason code:
This informational reason code does not change the transaction decision. Use it for additional visibility or in your own decisioning logic. For its definition, see the reason codes in the RiskOS™ Dashboard.
As part of ongoing infrastructure updates, we have added new IP addresses to RiskOS™. After August 31, 2026, RiskOS™ may begin serving traffic from these addresses.
If your organization restricts traffic by IP, add the six addresses listed here to your allowlists and firewall rules before that date. If you don't allowlist them, requests can be blocked and you may experience service disruption.
These additions are additive. Keep every Socure IP you already allowlist and add the six new ones.
New production IPs
54.209.34.129100.24.247.10944.195.229.53New sandbox IPs
3.218.138.16213.217.134.9854.85.52.249What you need to do
If you do not restrict traffic by IP, notify [email protected] so we can mark your account as ready.
For help during the update, contact [email protected] or your account team.
Released the Digital Intelligence Web SDK v2.11.0. This release includes the following enhancements:
Passkeys add a phishing-resistant, biometric credential to your RiskOS™ workflows through the Digital Intelligence Web SDK. The Socure Passkey Service runs the WebAuthn registration and assertion ceremonies and stores the resulting credentials, keyed by the identifiers you supply. It stores no user profile data and makes no authentication decision — it attests proof of possession, and you decide whether that authenticates the user for your system.
You integrate in two phases through your existing RiskOS™ workflows and the DI Web SDK. Registration creates a passkey on the user's device on their first visit, and assertion proves possession of that credential on return visits, using the SDK's registerPasskey() and assertPasskey() methods.
To get started, see the Passkey Integration Guide.
Resolved a formatting issue that could cause a Brazilian national ID (CPF) to be returned without its leading zero. These identifiers are now always represented accurately for matching.
Added two phone tenure signals to the Phone Risk International flow for India. These signals indicate the age of the phone service and return the subscriber tenure as a range, in months.
Released the Digital Intelligence Web SDK v2.10.1. This release includes the following fixes:
SigmaDeviceError that includes the underlying cause, instead of a plain string, making them easier to handle.Verify International now uses additional address sources that distinguish residential, business, and high-risk address types — including commercial mail receiving agencies — with greater precision. This change affects the R964 and R972 reason codes for all international countries.
We've enhanced our Canada identity verification service to more fully support FINTRAC compliance requirements.
Richer verification data for Canada Credit Bureau checks (Credit File Method)
Responses now include tradeline count, verification category, and credit file age, giving compliance teams the information needed to confirm which FINTRAC-prescribed method — credit file or dual process — was used to verify an identity.
Expanded platform availability
These verification details are now available through ID+ and RiskOS platform integrations, giving customers more flexibility in how they consume FINTRAC-compliant verification data.
More complete verification source reporting
When an identity is verified using multiple data sources — for example, a credit bureau and a telco provider — customers need to see every source that contributed to that decision, not just the ones that returned a match. Source attribution now lists all sources involved in a check, including a credit bureau consulted as part of the process even when it didn't return its own match. This gives compliance and audit teams a fuller, more consistent record of how each identity was verified, which is especially important for demonstrating FINTRAC-compliant identity verification in Canada.
Released the Digital Intelligence Android SDK 4.12.0 and React Native wrapper 4.11.1.
This release includes the following enhancements:
Over the past few weeks, we've expanded cross-transaction face matching to include selfies, in addition to the existing document headshot matching.
With this enhancement, Image Alert List now compares both the document portrait and the captured selfie against previously enrolled faces, improving our ability to detect identity reuse across verification attempts. This provides broader fraud coverage while maintaining the same integration and workflow you use today.
What's changing for you:
Image Alert List now matches selfies in addition to document headshots.
No integration or configuration changes are required.
Existing reason codes and API responses remain unchanged (I859/R859).
You can now configure Okta to use Socure as a Custom Identity Verification (IDV) provider. Okta routes users through a Socure verification flow — for example, during authenticator enrollment or password recovery — using OAuth 2.0 / OpenID Connect and credentials you generate in RiskOS™ Key Management.
To set it up, see Configure Okta with Socure Custom IDV.
Released reason code I937 for Socure Verify.
This code is generated during identity verification when the input phone number and input address resolve to different countries. It is informational and intended for downstream review and risk analysis. For its definition, see the reason codes in the RiskOS™ Dashboard.
Released the Digital Intelligence Android SDK 4.11.1 and React Native wrapper 4.10.0.
This release includes the following enhancements:
As of July 21, 2026, the RiskOS™ MCP Server no longer supports username and password authentication. MCP Server Keys replace it with token-based authentication. If you currently connect to the MCP Server using username and password credentials, generate an MCP Server Key and update your MCP client configuration to use the token before connecting again.
SSO-enabled organizations can now use the MCP Server. Previously, organizations using Single Sign-On (SSO) could not connect because authentication required local RiskOS™ username and password credentials. MCP Server Keys remove that requirement, so SSO-configured organizations can authenticate to the MCP Server with token-based authentication.
To generate a key and update your configuration, see MCP Server integration.
Released the Digital Intelligence iOS SDK 4.10.0.
This release includes the following enhancements:
You can now enable Auto Submit on a Capture App flow. When enabled, each captured image is automatically submitted for processing as soon as it passes the Capture App quality checks, so consumers no longer confirm each image manually.
This reduces the number of interactions during capture and streamlines the verification experience while keeping existing verification behavior unchanged.
To enable, go to Settings > DocV App > Flow, create or edit a flow, and turn on Enable Auto Submit. See Capture App Flow Setup.
Updated the nickname matching logic in the Phone Risk International flow to improve name-to-phone matching coverage and accuracy.
Age Assurance is a new RiskOS™ solution that confirms whether a user meets an age threshold without exposing their date of birth or exact age. A configurable waterfall runs low-friction passive methods first — device, phone, and email checks against Socure's Identity Graph — and escalates to active selfie or document capture only when a passive method returns no result.
Responses return privacy-preserving Boolean threshold flags (18+, 21+, and 25+) alongside a top-level accept or reject decision. No date of birth, exact age, images, or confidence scores are returned. Passive methods follow a no-hit, no-charge model.
To get started, see Age Assurance and Build an Age Assurance Integration.
Added support for identifying California driver's license and identification card digital signatures that have been revoked or suspended by the issuing authority. When Document Verification detects this condition, it returns R812.
This is an informational authentication signal only and does not impact the overall document verification decision. It provides additional visibility into the status of the issuing authority's digital signing certificate for downstream review and risk analysis.
You can now control how your Watchlist date of birth (DOB) filter behaves when DOB is missing from a match record. A checkbox in your filter settings lets you opt in to returning matches even when DOB is absent on a matched entity. Matches now also return by default when DOB is missing from your input request.
To enable, go to Settings > Watchlist and select your active policy, then choose False Positive > DOB Filter and check Include matches where match DOB is missing.
Released the Predictive DocV React Native SDK 5.2.8. This release adds full support for the React Native New Architecture (TurboModules and Fabric), introduces a new Promise-based launchSocureDocVWithPromise API, and adds a machine-readable code field to error responses.
Customers using implicit eCBSV can now take advantage of an expanded trigger option. When Socure's identity verification detects multiple conflicting dates of birth associated with an identity, eCBSV can be automatically invoked as part of your verification workflow — enabling faster, more seamless SSN verification without manual intervention.
This enhancement is opt-in and disabled by default. Contact your Socure representative to enable it for your account.
Added verification of the digital signature embedded in the PDF417 barcode on supported California driver's licenses and identification cards. This enhancement provides an additional layer of tamper detection by cryptographically validating barcode data issued by the California DMV, helping identify fraudulent, altered, or revoked credentials with greater confidence.
When digital signature validation is successful, Document Verification returns I800.
When digital signature validation is unsuccessful, Document Verification may return R810.
The consent language displayed on the Terms & Consent page in the Predictive DocV Native and Web SDKs has been updated to improve transparency around how consumer data is processed during identity verification.
Key update:
Full updated consent language:
Hello! We will verify your identity for ongoing fraud prevention purposes using our service provider Socure to analyze your selfie and document images captured via photo or video with automated technology, including facial recognition.
You have read, understood, and agree to Socure's Terms of Use, including class action waiver and arbitration agreement, and Privacy Notice, which explains how they collect, use, retain, transfer, and secure your facial biometrics and other personal information, their use of service providers, and your data rights.
No SDK update is required. The updated consent language is applied automatically to all new DocV transactions.
Released the following new informational reason code for Predictive DocV:
This code is generated during document verification for supported California driver's licenses and identification cards as part of the digital signature validation capability. It is intended for downstream review and risk analysis. For its definition, see the reason codes in the RiskOS™ Dashboard.
Fixed a bug where signals.address.localHour and signals.address.timezoneOffset were not adjusting based on Daylight Savings Time (DST).
Enhanced Email RiskScore model routing to support future international model expansion. Requests without a country now default to the US Email RiskScore model, while international models are selected only when a non-US country is explicitly specified.
Released the Digital Intelligence Web SDK v2.10.0. This release includes the following enhancements:
Fixed an edge case in SSN resolution logic where identities with multiple shared SSNs could retain an incorrect SSN after correction. The system now evaluates all associated SSNs before applying corrections, improving match accuracy and reducing false low-confidence outcomes for affected consumers.
You can now authenticate to the RiskOS™ MCP Server using MCP Server Keys — a secure, token-based authentication method. Generate and manage keys from Developer Workbench > API & SDK Keys in the RiskOS™ Dashboard, then pass the key as a bearer token in your MCP client configuration.
MCP Server Keys enable MCP Server access for all customers, including organizations that use Single Sign-On (SSO). Username and password authentication for the MCP Server is no longer supported after July 21, 2026. Generate an MCP Server Key and update your MCP client configuration before this date.
For more details, see Integrate Using Cursor / Claude Code (MCP Server).
The Reason Codes endpoint is now available in RiskOS™. Retrieve the reason code catalog programmatically with GET /api/reason-codes, filter by product, name, free text, or active status, and cache the descriptions in your own systems instead of reading the Dashboard manually.
For more details, see List Reason Codes.
Released the Digital Intelligence Android SDK 4.10.1 and React Native SDK 4.9.1. Fixed SDK ProGuard configuration to allow consuming apps to apply full code shrinking and obfuscation without interference.
Released the Predictive DocV iOS SDK 5.4.2. This is a maintenance release with minor bug fixes.
Released the Digital Intelligence Android SDK 4.10.0.
This release includes the following enhancements:
Added new computed fields called hasBatteryFullStateMismatch and hasLowEntropyUserAgentClientHints to the Digital Intelligence API response.
hasBatteryFullStateMismatch: a boolean that indicates whether the device has a battery percentage of 100% but battery state is not 'full'.hasLowEntropyUserAgentClientHints: a boolean that indicates whether the browser has low entropy User-Agent Client Hints (web only).Added new exact match reason codes for Phone Risk International: I623, I624
Released the Digital Intelligence Web SDK v2.9.0. This release includes the following enhancements:
Phone Risk International coverage has been expanded to support 240+ countries and territories, increasing global phone risk assessment capabilities and enabling broader international coverage for identity verification and fraud prevention use cases.
A new Enable For Platform option is now available when configuring Capture App flows. This setting restricts a DocV flow to a specific platform — Web, Mobile, or All Platforms — binding the session to the selected platform type.
When a flow is bound to a single platform, the session cannot be completed on a different platform type, helping prevent link-forwarding attacks where a verification link intended for one platform is shared to another.
Configure this option in Settings > DocV App > Flow in the RiskOS™ Dashboard. For more details, see Capture App Flow Setup.
Released the Predictive DocV Android SDK 5.4.7. This release includes the following bug fixes:
Payment Screening is now available as a pre-built solution in RiskOS™. Screen every entity and identifier involved in a payment transaction against global sanctions lists, PEP data, and Adverse Media in real time.
Key capabilities:
For more details, see Payment Screening.
DocV now captures video across all image capture steps to strengthen injection detection and support enhanced fraud review within RiskOS™. These session videos are surfaced directly in RiskOS™ for improved investigation.
Added Document Verification (DocV) with Socure Pass as a Socure Launch solution for startups. This solution combines government ID verification with Socure Pass reusable identity, allowing returning users to skip repeat document verification through passkey authentication.
Key capabilities:
The solution uses a Hosted Flow integration where RiskOS manages the entire verification experience, including Socure Pass authentication, document capture, and consent.
For more details, see DocV with Socure Pass.
Fixed an issue with reason code I708 that may result in a slight decrease in firing rates.
Predictive DocV now supports data extraction for secondary documents such as utility bills, bank statements, pay stubs, and tax forms. When a secondary document transaction completes, extracted user and document data is returned in the API response alongside Digital Intelligence device signals.
Data extraction and workflow integration
userData and documentData fields are available in RiskOS Workflow Logic for automated decisioningPDF upload support
UX improvements
Bug fixes
Released the Predictive DocV Android SDK 5.4.6. This release includes the following bug fixes:
IllegalStateException crash during image captureFileNotFoundException crash during multi-frame captureAdded a new computed field called deviceNetworkTimezoneOffsetDiffMinutes to the Digital Intelligence API response. This field represents the difference in minutes between the device's timezone offset and the network location's timezone offset.
Released the Predictive DocV React Native SDK 5.2.4. This is a maintenance release for the React Native DocV SDK.
Released the Predictive DocV Android SDK 5.4.5. This release includes the following changes:
arm64-v8a and armeabi-v7a architecturescompileSdkVersion to 36Released automated document classification and data extraction for the Secondary Documents workflow. These enhancements integrate directly into RiskOS with no API changes required.
For more details, see Secondary Document Capture and Secondary Document Setup.
Released the Predictive DocV React Native SDK 5.2.3. This release includes the following changes:
arm64-v8a and armeabi-v7a architectures, resolving crash issues on low-end devices during the upload processReleased the Digital Intelligence React Native SDK 4.8.1. This release includes the following changes:
Released a new model designed to detect synthetic passport captures exhibiting signals of injection and deepfake activity.
R820, R834Introduced additional signals within DocV leveraging Digital Intelligence to identify spoofing behavior and strengthen injection detection.
R815Released an improvement to phone line type classification for certain carrier-routed numbers. For affected carriers, the line type is now overridden to Non-fixed VOIP.
This update improves the accuracy of line type signals. As a result, you may observe a 0.5%–1.3% increase in Non-fixed VOIP classification rates.
Released new Enrichments for Graph Intelligence Standard and Graph Intelligence Plus. These Enrichments can be placed in workflows as standalone steps, instead of requiring the use of combined Enrichments such as Socure Sigma Identity Fraud + Graph Intelligence or Socure Email Risk + Graph Intelligence.
Add-on requirements still apply. To use Graph Intelligence Plus in a workflow, your workflow needs to include at least one of Socure Sigma Identity Fraud, Socure Sigma First-Party Fraud, Socure Verify, or Socure Verify+. To use Graph Intelligence Standard in a workflow, your workflow needs to include at least one of the former or Socure Email Risk or Socure Phone Risk.
For more details, see Graph Intelligence→Usage Scope and Graph Intelligence→RiskOS™ Dashboard Setup.
Released the Predictive DocV iOS SDK 5.4.1. This is a maintenance release for the iOS DocV SDK.
Released reason code I674 to the Phone Risk module to enhance existing risk detection capabilities.
Released the new reason code R966 to reduce false address failures by conditionally accepting nontraditional residential addresses using external metadata. For more information, see the reason codes in the RiskOS™ Dashboard.
Customers can now approve certain nontraditional residential addresses when they show stable, long-term residence. This change can reduce commercial address-related declines by more than half and help more users get through signup with less friction.
Standard commercial locations like offices, retail businesses, hotels, and short-term lodging will remain blocked under R964, but when enabled, the setting automatically identifies eligible address types:
If the input address maps to a conditional property type, a residential override will be applied to property tax and USPS data enabling frictionless onboarding.
The setting will be under the Verify address product settings and listed as Conditional Address Acceptance.
Why it matters:
This expands coverage for people with valid but nontraditional living situations while keeping your CIP standards intact. It also delivers a meaningful lift in auto-accept rates. We’re finalizing details with partners and will share configuration guidance upon full release.
Released the Predictive DocV iOS SDK 5.4.0, Android SDK 5.4.1 and React Native SDK 5.2.0. These releases include multi-frame capture and additional sensor capture to prevent injection attacks.
Released the Digital Intelligence React Native SDK 4.8.0. This release includes the following enhancements:
setNavigationContext() method for manual navigation context tracking.registerNavigationContextTracking() and unregisterNavigationContextTracking().Released the Digital Intelligence iOS SDK 4.8.1. This release fixes a potential crash when the SDK is stopping viewport size data collection.
We have removed detailed signals documentation from the RiskOS™ doc site (https://help.socure.com/riskos/).
Going forward, signals documentation will be available directly in the RiskOS™ Dashboard for easier access and review.
We have removed detailed reason code documentation from the RiskOS™ doc site (https://help.socure.com/riskos/).
Going forward, reason codes will be available directly in the RiskOS™ Dashboard for easier access and review.
Released the Predictive DocV Android SDK 5.4.0. This release includes minor enhancements and dependency updates.
Released the Predictive DocV iOS SDK 5.3.0. This release includes minor enhancements and framework updates.
Released new signals to provide deeper insights into phone behavior and address types. These updates include information regarding phone porting history, prepaid status, and enriched geographical and structural details for submitted addresses.
| Category | Signal Type | Description | Example Values |
|---|---|---|---|
| Phone | Area Code Localization | The cities associated with the phone number’s area code. | ["city name", "city name"] |
| Phone | Porting History | The number of days since the phone number was last moved between carriers. | 107 |
| Phone | Billing Type | Indicates if the phone number is a prepaid service. | false |
| Address | Building Classification | Categorizes the structure (e.g., single-unit, multi-unit, P.O. Box). | "single-unit" |
| Address | Location Usage | Identifies the primary purpose of the address (e.g., residential, commercial, educational). | "residential" |
Note: Certain phone localization data may return as an
Arraytype. Please ensure your integration is configured to handle this data format.
Released updates to Socure's DocV Privacy Policy to reflect the following product developments:
Released a new reason code to provide a more granular phone subscriber tenure signal for GSA use cases:
This client-specific reason code is available only to authorized GovCloud customers and does not replace existing standard R-prefixed tenure reason codes.
Released the Predictive DocV Android SDK 5.3.1. This release includes minor updates and security enhancements.
We have integrated with additional data vendors to increase coverage on phone numbers, email addresses, and physical addresses, while improving accuracy for phone activity and porting data.
Email Correlation
Improved data coverage now allows for stronger correlation between names and email addresses, resulting in higher confidence matches for identity verification.
Address Correlation
Enhanced address-based coverage improves our ability to correlate individuals within households and provides higher precision for street-level address matching.
Phone Activity & Porting History
Expanded coverage allows for better identification of active phone numbers and more comprehensive porting intelligence, enabling more precise risk decisions.
Added support for Personal Numbers by introducing two new response fields: personalNumber and personalNumberType. These represent identifiers tied to the individual (such as tax or voter IDs) rather than the document itself, providing deeper identity context.
Released the Digital Intelligence iOS SDK 4.8.0 and Android SDK 4.8.0. This release introduces the setNavigationContext() method to SigmaDevice, allowing for improved tracking of user navigation flow during behavioral data collection.
Released an upgrade to international models that significantly improves support for non-Latin characters. Documents may now return data extractions in the original non-Latin script for supported regions.
Introducing International Phone Signals, extending Socure’s phone intelligence to 60+ countries. These signals deliver consistent, standardized attributes globally, including carrier information, line type, and porting status.
The Download Evaluation Documents API will now return a 204 No Content response instead of 404 Not Found when no documents are available. This update improves API consistency and aligns with standard RESTful semantics.
Released the Digital Intelligence React Native SDK 4.7.4. This release adds support for server-configurable location precision settings, giving customers more control over data collection granularity.
Released the Digital Intelligence Android SDK 4.7.5. This release adds support for server-configurable location precision settings.
Released the Digital Intelligence Android SDK 4.7.3 and iOS SDK 4.7.1.
This release includes the following enhancements:
Two new indicators provide clarity: * isMatched shows the record that aligned with the information the user provided. * isLatest identifies which record is the most recent in the identity graph.
Prefill and Verify Plus now return county information as part of every validated U.S. address to support more granular decisioning.
Verify and Prefill now review all available name records and sort them based on recency and frequency across trusted sources to prioritize the most current name.
Added more Relatives and Close Associates (RCAs) data to Politically Exposed Person (PEP) hits. * Improved RCA Context: We now explicitly identify RCAs and define their relationship to the primary PEP directly within the API response. * Relationship Node: A list of known relationships is now available as additional context to provide a clearer view of flagged individuals.
Socure's SAML-based authentication now supports a new (optional) custom SAML attribute called RoleName which can be used to assign RiskOS role(s) to a user via your Identity Provider.
For more information, see the Configure Okta SAML Authentication docs.
Socure Verify now supports the driverLicense field.
* Valid match: Returns a high-confidence field validation score.
* Expired license: Properly identifies expired credentials with a specific status return.
* Verified Data: For Verify Plus customers, the matched driver license number can be included in the response payload when available.
{
"fieldValidations": { "driverLicense": 0.99 }
}
Released the Digital Intelligence Web SDK v2.8.1. This release modifies WebRTC IP capture to IPv4 to better align with common customer use cases.
We have updated signal rounding across Sigma Synthetic and Graph Intelligence for enhanced interpretability. Values are now rounded to between 3 and 6 decimals depending on the specific identity feature to provide more consistent results during manual review.
Update the API response to include a new device.globalDeviceId field:
* Unified Identifier: Links device and identity data across the Socure graph for a cross-client view of reputation.
* Compatibility: Existing device IDs (device.id) remain unchanged for backward compatibility.
Fixed a bug for SSNs issued in specific U.S. territories where geographic metadata was incorrectly populated. These values now correctly return the appropriate state and territory labels and accurate issue year ranges.
Introducing Identity-Based Verification within Account Intelligence. This feature enhances accuracy and expands verification coverage through deeper correlation with identity attributes from the Socure Consortium.
Key improvements:
Updates to Correlation Logic:
This release includes enhanced logic to correlate accounts with identity attributes, including:
Added a QR code to the desktop error screen. When a consumer opens a Predictive DocV URL on a desktop device, they can now scan the QR code to seamlessly continue the verification process on their mobile device.
We have updated our verification logic to properly recognize and categorize National IDs identified as Adoption Taxpayer Identification Numbers (ATINs). This ensures these identifiers are handled correctly within your workflow and are not incorrectly flagged as invalid.
Customers can now optionally configure the auto-capture timeout for image captures between 0 and 10 seconds. This defines how long the system attempts auto-capture before presenting the Manual Capture button.
Released the Digital Intelligence Android SDK 4.7.2 and React Native wrapper 4.7.2. This update adds missing ProGuard rules.
The following enhancements are now live:
New Sigma V4.1 models are now live for the All and Credit Card versions. This update improves overall scoring precision and enhances fraud capture rates against the latest patterns. Reach out to your Account Manager to start migrating today.
Introduced metadata features that enhance Graph Intelligence with richer network-level insights derived from primary keys (e.g., email domains). These features provide insights even for first-time identifiers by leveraging associated network trends.
Corrected an issue where email-based top-level domain indicators were firing within address and phone risk response nodes. These indicators now correctly fire only within email-specific and fraud/synthetic risk modules.
For Canadian verifications using the credit file method, the creditFileNumber is now included in the API response to ensure compliance with FINTRAC recordkeeping requirements.
Watchlist screening now includes additional financial identifiers, including crypto handles, routing numbers, and account numbers. evaluating these provides more precise visibility into which field triggered a sanctions match.
Name matching now supports non-standard token order and more inclusive behavior for incomplete data. Watchlist case tables also now support sorting by creation date.
Released v4.7.1 of the Digital Intelligence Android and React Native SDKs to fix an ANR issue for specific Android devices.
Updated the SMS HELP message language for DocV flows to enhance compliance with U.S. Short Code requirements. The message clarifies Socure's role as a service provider and directs users to your support team.
Added support for automatic language detection. By passing auto as the language value in the configuration, the Capture App detects the user's device language and displays the supported experience.
Released v4.7.0 of the Digital Intelligence Android and React Native SDKs. Added support for Media Device information capture and fixed a Jetpack Compose compatibility issue.
DocV webhooks may temporarily originate from 3.138.161.243 due to regional failover. Update your allowlists as necessary.
Users associated with multiple RiskOS™ accounts will now see a selection screen after logging in to choose their active namespace context.
Refined validation logic to ensure address quality indicators more accurately reflect regional formatting variations, reducing false negatives for international transactions.
Improved name reconstruction logic to infer accurate full names from inconsistent datasets. This includes expanding initials, mapping nicknames, and removing non-human text.
Webhook notifications are now sent only when a watchlist monitoring enrollment fails. If no webhook is received, the enrollment succeeded.
Signals are now available across all Fraud and Risk products (Sigma Identity Fraud, Sigma Synthetic, Email Risk, Phone Risk, and Address Risk), providing direct access to features for fine-tuning specific patterns.
Released iOS SDK v4.7.0. Added support for Media Device information capture.
Deprecated several legacy indicators that overlapped with newer, more stable IP-based and address-based logic to provide improved usability and system stability.
Released Web SDK v2.8.0. Includes support for detailed Media Device information capture and fixes for architecture reporting and screen size information.
New POST /api/evaluation/monitoring endpoint allows customers to enroll existing evaluations in continuous Watchlist Monitoring.
Added identity verification support for Hong Kong, Venezuela, Syria, Guinea, Honduras, Guatemala, and Guadeloupe using a mix of civil, telco, and utility registers.
Switzerland is now supported with 95% population coverage across civil, utility, telco, and credit registers.
Added support for Réunion using phone utility data, providing 68% population coverage.
Added civil, tax, and telco records for Sweden, providing up to 92% population coverage.
Switched from Report-Only to an enforced Content-Security-Policy header. Review your iframe and custom font integrations to ensure domains are allowlisted.
Added support for phone utility data in Vanuatu, providing 25% population coverage for name and phone verification. This supports identity validation in environments where traditional documentation may be limited.
Enhanced commercial identity coverage in Canada, now reaching approximately 51% of the adult population for name, DOB, address, and phone verification.
Added a proprietary source combining government and marketing data, covering 79% of the adult population. Verifies full name, DOB, address, and national identifiers (Passport and Emirates ID).
Support for Sudan’s government voter registry is now live, covering 82% of the population. This strengthens residency and identity confirmation via real-time data updates.
Added high-coverage consumer identity files for the following regions to support digital onboarding: * Spain: 74% coverage via digital campaign and promotional data. * Italy: 54% coverage via census-based sources. * Colombia: 62% coverage via consumer activity signals. * Germany: 22% coverage via eCommerce-linked records. * United Kingdom: 30% coverage via lead generation and consumer offers.
Released major updates to national identity registers: * Mexico (RENAPO): Real-time verification of CURP (national ID), name, and DOB, covering 90% of the population. * Brazil: 75% coverage via eCommerce-derived consumer identity data. * Poland: 32% coverage via digital consumer channels. * Romania: 42% coverage via government voter registry matches. * Qatar: 28% coverage via phone register data for identity resolution in the GCC region.
Added authoritative government sources for: * Panama: 95% coverage via the Electoral Tribunal for real-time ID verification. * Uruguay: 95% coverage via the Civil Registry for Cédula de Identidad verification. * United Arab Emirates: 90% coverage via ICP for Emirates ID and address verification.
Introduced new outcome indicators for Name, SSN, and DOB verification at the SSA. This allows partial verifications to be traced to specific field mismatches, providing clearer insight into verification results.
Added three distinct credit-linked identity sources for the UK, covering up to 85% of the population. These sources verify name, DOB, and postal address for high-assurance financial onboarding.
Consolidated voter registration, credit activity, and telecom subscriber records, covering 56% of the population to support identity continuity checks.
Uzbekistan is now supported via three government sources, including DMV and voter registries, covering 27% of the population with real-time updates.
Added seven unique datasets for Australia to provide holistic identity resolution: * Electoral Roll: 97% coverage for historical name and address validation. * Consumer Credit Bureau: 65% coverage for compliance-grade reliability (requires consent). * Landline and Telco Directories: Combined 30%+ coverage for address-to-identity linkage. * Tenancy and Public Records: Specialized sources for residential consistency and identity continuity.
We now verify identities using official data from the Social Security System (SSS) and tax records, covering 65% of the population.
Added a credit-linked identity source from business registries in Slovakia, supporting economic identity validation for commercial applicants.
Expanded authoritative CPF validation with identity attributes from Receita Federal, covering 67% of the population.
Added a high-assurance commercial dataset built from two major U.S. credit bureaus, covering 90% of the population for KYC and regulated onboarding.
Released updates to document verification logic, including new indicators for: * Identifying invalidated or voided credentials (e.g., hole-punched or cut corners). * Detecting device tampering or digital injection risks. * Recognizing when a document address is a PO Box. * Improved handling of headshot tampering and mismatched ID types.
Released a feature that validates U.S. ID card and driver’s license data directly against issuing jurisdictions to ensure maximum credential integrity.
Added a source combining SRI tax registry data with verified commercial records, covering 55% of the population.
Phone register data is now available for Sri Lanka, providing an alternative to document-based checks for mobile-first verification.
Added support for Pakistan via phone utility records, covering 26% of the population.
Added support for the Department of Provincial Administration (DOPA) registry, providing 90% population coverage. This is Thailand’s core legal identity source, offering deterministic match precision for high-confidence verification.
Now validating national identity via the Junta Central Electoral (JCE), covering 90% of the population. This source provides authoritative confirmation for civil and voting identity attributes.
Expanded coverage in Peru using civil identity (RENIEC) and tax authority (SUNAT) data, reaching up to 99% of the population.
Now support Uruguay’s civil registry with 100% population coverage. This real-time source supports national onboarding and identity resolution workflows.
The Watchlist screening engine now predicts name component order (first, middle, last) to improve match accuracy. This distinguishes between formatting variations and genuine mismatches, ensuring high-confidence matches even when name tokens are reordered.
We’ve simplified the RiskOS™ navigation to help users stay oriented: * Flattened Structure: Key sections are now easier to access with fewer clicks. * Developer Workbench: Repositioned developer tools for better visibility. * Standardized Layout: User icons and account actions moved to the upper-right corner.
The Watchlist API now returns streamlined data for sanctions matches. We have reorganized identification details and simplified data structures to help analysts interpret results and focus on context more quickly.
Response times for Watchlist Plus have been reduced by up to 60% through infrastructure upgrades. Customers will see faster screening and improved uptime during peak hours without requiring integration changes.
The UK is now supported through a nine-source identity graph covering up to 99% of the population. New authoritative and behavioral sources include: * Electoral Register: Legal and residency confirmation via official voter data. * Lender-Verified Records: Identity signals confirmed by UK financial institutions. * Public Registries: Access to insolvency, shareholder, and enforcement data for enhanced due diligence. * Consumer & Marketing Data: Behavioral datasets to validate identity activity for digital-first users.
The UAE is now supported through telco and government sources covering up to 60% of the population, facilitating KYC and compliance matching in MENA markets.
Added a dataset covering identity data from product registrations and digital distance selling workflows. * Coverage: 40% of the population. * Verification: Validates name, DOB, phone, and address. * Benefit: Validates recent address usage and helps identify synthetic patterns through digital activity signals.
Added both telco and population register data for Liechtenstein, providing up to 83% population coverage. This supports cross-border compliance for institutions operating in the Swiss and EU corridors.
Somalia’s voter registry is now available for civil identity confirmation, providing 28% population coverage. This supports eligibility checks in regions with developing infrastructure.
Introduced new Selfie Auto Capture functionality to the Capture App to streamline the user experience during document verification.
Expanded coverage in Portugal via telco, voter, and population registers, reaching up to 90% of the population. This enables strong identity triangulation for regulated onboarding.
Ukraine is now covered via seven government sources, including voter, DMV, and resident data. * Coverage: Up to 93% of the population. * Updates: Real-time government data updates. * Benefit: Ideal for cross-border onboarding and regulatory screening.
Implemented a minimum age requirement of 18 for DocV sessions. System logic now includes automated PII deletion for users identified as underage to support data protection standards.
Released a new endpoint for downloading documents associated with an evaluation as a structured ZIP archive. This includes consumer-submitted identity documents and case attachments, organized into labeled folders for auditability.
Norway is now supported via a resident register and mobile utility records, covering 96% of the population for name, DOB, and address verification.
Uganda’s official government voter registry is now supported, providing 28% population coverage for financial inclusion and eligibility checks.
Added directory and hybrid registry sources for: * Romania: 40% coverage via a hybrid government and credit source. * Spain & Portugal: Expanded landline subscriber directories covering ~35% of each population. * Gibraltar: Additional telecom operator coverage (27%) for geographic presence confirmation.
Added support for a top Colombian credit bureau, covering 75% of the population for name and address evaluations. This source is used to increase precision for identity stability scoring.
Added a daily-updated marketing dataset containing verified consumer information. This is particularly useful for establishing proof of life and confirming digital activity for thin-file or document-light identity profiles.
Now support an 80% population coverage graph in Poland, integrating voter, credit, and telecom data. This provides authoritative signals for digital onboarding, lending, and regulatory screening.
Added two authoritative government sources for identity verification, covering 65% of the population. This combines population and residence data to support both onboarding and address confirmation.
Rolled out major updates to Prefill that improve match quality and coverage for partial data submissions. New logic includes majority-match validation and precision weighting for sparse attributes to ensure higher accuracy and fewer false positives.
Expanded the availability of location-based indicators that analyze the geographic distance between a user's address and physical point-of-sale locations. This provides deeper insight into address-related risk signals for retail and in-person use cases.
Launched the new GenAI Explainability feature in the RiskOS™ Dashboard. This tool provides fraud and compliance analysts with natural-language summaries explaining the key factors behind model scores and verification results. * Coverage: Available for Fraud, Synthetic, Email, Phone, Address Risk, DocV, Verify, and Global Watchlist. * Note: This feature must be enabled at the customer's request.
Released a new third-party data service integration with Baselayer. This business onboarding service provides access to a business data consortium, industry classification checks, and specialized searches for litigation and bankruptcy records.
Successfully refactored the internal watchlist service to streamline code architecture. This upgrade reduces system complexity and improves build efficiency, allowing for faster delivery of screening enhancements without changing production behavior.
Now support identity verification via phone utility data in Mali, providing 26% population coverage for presence confirmation in West African onboarding.
Added three new high-confidence sources for Spain: * Tax Identity (AEAT): NIF-based validation covering 76% of the population. * Telco Registry (SGDA): Alternate access to mobile and landline subscriber data (37% coverage). * Directory Sources: Added supplemental contact validation via national landline and B2B directories.
Updated the logic for identifying transaction anomalies to provide more precise capture. This optimization reduces noise and improves the accuracy of anomaly-related risk indicators.
Now support Nigeria’s national ID, driver’s license, and voter registry. This provides up to 90% population coverage with real-time updates from official government sources.
Added Finland’s official identity database (Väestörekisterikeskus), providing 90% population coverage for full legal identity confirmation.
Now support Indonesia’s primary government registry for legal identity. Covers 80% of the population with daily updates to verify national ID, name, and DOB.
Now support a five-source graph in Singapore including resident registry and credit bureau data, covering 91% of the population with real-time updates.
New Zealand is now supported through eight comprehensive sources, including government identity documents and population registers, reaching 100% population coverage. This supports national onboarding and document fallback workflows with real-time updates.
Added six high-confidence government sources in Mexico, including CURP and tax registers, covering 95% of the population. This supports national onboarding with document-linked identity precision.
Expanded identity coverage via proprietary directory and commercial datasets for:
The Philippines is now supported via a multi-factor framework integrating voter, national ID, and telco data, covering up to 80% of the population.
Added daily-updated consumer identity data derived from loan applications and lifestyle memberships, covering 70% of the population. This supports behavioral verification and identity activity scoring.
Added support for language translations of custom UI text within the Capture App. This enables customers to display localized instructions and feedback to end-users globally.
Advanced Pre-Fill is now live in Brazil, allowing users to pre-populate verified identity data using minimal inputs to reduce onboarding friction while maintaining high security.
Released a new risk indicator that highlights discrepancies between an individual's address history and the issuance location of their primary identity identifiers.
Implemented smart attribution for historical identity data. The system now intelligently handles first and last seen dates, providing automated temporal information when it is unavailable from primary sources.
Added an integrity flag to detect Android devices running suspected tampered or modified OS builds (such as custom ROMs), providing deeper insight into mobile device risk.
Expanded coverage in South Africa across four specialized datasets: * Business Registry: Director and officer verification via the CIPC (75% coverage). * Household Audits: Field-verified data for off-registry populations (75% coverage). * National Deeds: Ownership-linked identity via land title records (65% coverage). * Social Security: Registration data for underserved population verification (55% coverage).
Turkey is now covered through voter, resident, and consumer registries, providing 90% population coverage for high-trust onboarding.
Released two new features in RiskOS™: * One-Time Passcode (OTP): Verifies identity via time-sensitive codes sent through SMS, voice, or email. * Caller Name Verification (CNAM): Retrieves and compares caller names against known identities to enhance verification accuracy.
Now support real-time identity validation using Australia’s official Electoral Roll, covering 95% of the adult population for name, address, and date of birth verification.
Now offer real-time identity validation using data from major UK telecom providers, covering 95% of the population. This high-speed verification supports fraud prevention by validating name, phone number, DOB, and address directly against carrier records.
Added 23 new language customization options for the Capture App, including Japanese, French (Canada), Hindi, and various Spanish regional dialects. These settings apply to default UI text elements and the Terms & Conditions page.
Teams can now run risk evaluations directly within the RiskOS™ Dashboard without requiring API integration. This feature allows users to manually enter case details into a custom intake form and receive instant risk assessment results.
The Netherlands is now supported via a comprehensive graph integrating citizenship, population, telco, and credit registers, covering 90% of the population.
Introduced the Evaluation paused webhook event type for asynchronous integrations. This event triggers whenever a workflow enters a paused state, allowing for better monitoring of manual review queues.
Released a new identity risk indicator that identifies anomalous gaps in an individual's address history, highlighting periods of inactivity that may signal risk despite recent activity.
Now support identity confirmation using verified enrollment and degree data from over 3,600 U.S. institutions. Covering 50% of the population, this source is ideal for verifying students and recent graduates for financial aid and account recovery.
Added phone utility identity support for Togo (26% coverage) and Trinidad and Tobago (79% coverage via voter registry).
Released the api/v1/entity-devices endpoint. This allows customers to retrieve devices associated with a specific household, business, or customer user ID, providing deeper insight into device-to-identity linkages.
Implemented a sophisticated hierarchical system for resolving conflicting identity data (such as multiple Dates of Birth). * Prioritization Architecture: Establishes a hierarchy that favors high-authority data sources. * Coherence Analysis: Uses historical and geographic data to identify outliers and resolve contradictions. * Improved Logic: Streamlines handling of multiple identifiers to ensure cleaner, more accurate identity records.
Added the disableSmsInput option to the DocV Web SDK configuration. This allows customers to streamline the handoff experience by disabling SMS input and exclusively displaying the QR code for mobile transition.
Updated Sigma First-Party Fraud prefill functionality to support combinations of email and mobile number when a 9-digit SSN is not provided. This reduces friction while maintaining identity integrity.
Launched a massive expansion for Australia, integrating over eight authoritative sources including passport, driver’s license, and voter rolls. Provides up to 100% coverage for name, DOB, and address verification with real-time updates.
Added a gold-standard address verification dataset built from USPS records and property registries. Covering 99% of the population, this source confirms residence and reduces jurisdictional risk.
Released real-time identity validation via major mobile network operators across several key markets. These sources confirm phone-to-person linkage and detect synthetic identities: * Netherlands: 99% population coverage via major carriers. * United Kingdom & Canada: High-assurance telco data with consent-based verification. * France, Germany, & Italy: Expanded mobile subscriber coverage (ranging from 24% to 80%). * Brazil & United States: Integrated telco subscriber data with credit-linked identity records for 80-95% coverage.
Now support direct identity verification against Brazil’s largest mobile network operators (Vivo, Claro, TIM, and Algar). * Coverage: 80% of the population. * Verification: Real-time validation of name, DOB, phone, address, and CPF. * Benefit: High match confidence for identity continuity and real-world presence confirmation.
Added phone utility data support for Lesotho (29% coverage) to provide passive KYC signals for mobile-first services in Southern Africa.
Integrated both government voter registers and phone utility data for Albania. This dual-source approach, covering up to 71% of the population, strengthens match accuracy for domestic onboarding and risk checks.
Launched two distinct sources in Morocco: a mobile phone register and a utility register. Combining these sources (up to 75% coverage) strengthens mobile verification and adds behavioral trust signals.
Integrated a broad-coverage credit header dataset built from top banks and telco providers in Brazil. * Coverage: 99% population coverage. * Verification: Comprehensive check of name, DOB, gender, CPF, address, email, and phone. * Benefit: Authoritative visibility for synthetic detection and identity completeness checks.
Added real-time government identity database support for Taiwan, providing 100% population coverage for onboarding and civil status verification.
Now support Afghanistan’s official voter registry, the most authoritative national ID source in the region. Covers 87% of urban and rural registrants for real-time name, DOB, and address verification.
In September 2026, we are expanding international Phone Risk with new signals and a new reason code to help identify disposable phone numbers and estimate how long a phone number has been in service.
If you use Phone Risk, you will begin receiving these signals in your responses.
In September 2026, we are updating our commercial address classification logic to more accurately identify residential addresses. When an address can be identified as residential, the firing frequency of some reason codes will shift:
For reason code definitions, see the reason codes in the RiskOS™ Dashboard.
In September 2026, we are expanding Graph Intelligence with new industry-focused signals. These signals capture how often, and across how many organizations, Socure has seen an identity element within key industry categories, adding finer-grained context on top of the existing Graph Intelligence network signals.
If you use Graph Intelligence, you will begin receiving these signals in your responses. Use them as variables in your own models, or to identify thresholds that correlate with increased risk in your population. For the full signal names and definitions, see the Risk Signals reference in the RiskOS™ Dashboard (Settings > Documentation > Risk Signals).