FAQs

This section includes frequently asked questions (FAQs) about Email Risk.

General product behavior

How does Email Risk work?

Email Risk evaluates characteristics of an email address and related context to assess potential fraud risk and identity consistency.

Signals may include indicators related to email validity, tenure, usage patterns, and alignment with provided identity attributes.

The resulting scores are intended to support risk assessment and workflow routing when used alongside other signals.

Does Email Risk support international or legacy email addresses?

Yes. Email Risk supports a wide range of email patterns, including international and legacy formats.

Signal depth may vary by region, and results are best interpreted in combination with additional identity context when available.

Does Email Risk replace other fraud tools?

Email Risk is designed to act as an early risk and consistency signal, particularly when limited identity information is available.

It is most effective when used in combination with other verification and fraud prevention tools as part of a layered strategy.


Integration & input formatting

What data is required to use Email Risk?

Email Risk evaluates the inputs provided with each request.

An email address is required to generate a score. Additional identity attributes, such as name or location data, can provide supporting context and improve confidence when available.

What happens if input data is missing or invalid?

If required inputs are missing or cannot be processed, Email Risk may return limited or no results.

Validating input formatting and ensuring consistent data submission helps improve reliability and signal quality.

Are special characters or Unicode supported?

Email Risk supports standard character encoding when inputs are properly normalized.

Normalizing inputs before submission helps avoid processing issues and ensures consistent results.


Output & interpretation

What do Email Risk scores represent?

Email Risk returns scores that represent relative risk and identity consistency based on the evaluated inputs.

Scores are intended to be interpreted in context and used as part of a broader decisioning strategy rather than as standalone determinants.

What types of explanations are returned?

Email Risk may return explanatory indicators that highlight contributing factors associated with elevated or reduced risk.

These explanations are designed to support investigation and review and should be evaluated alongside other available information.

Why might scores vary over time?

Scores may change as new information becomes available or as patterns associated with the email evolve.

For best results, evaluate scores in combination with other signals and over time rather than in isolation.


Retry & fallback

What should I do if a score is not returned?

If a score is not returned, verify that required inputs are present and correctly formatted and that the integration is configured as intended.

Providing additional context where available may improve results.

How should elevated risk outcomes be handled?

Elevated risk indicators can be used to trigger additional review, verification, or escalation steps according to your organization’s fraud policy and risk tolerance.


Troubleshooting & support

How should unexpected results be handled?

If results appear unexpected or inconsistent, first confirm that inputs are complete and consistently formatted.

For further assistance, contact Socure Support with relevant details about your integration and use case.


Product limitations

Is Email Risk a standalone identity verification solution?

No. Email Risk is designed to provide risk and consistency signals and should be used as part of a broader fraud prevention or verification strategy.

Does Email Risk update when other identity data changes?

Email Risk evaluates characteristics related to the email address and associated behavior. Changes to other identity attributes may not immediately affect results.

Can scoring behavior be customized?

Email Risk outputs can be incorporated into configurable workflows within RiskOS™, allowing organizations to define how scores and signals are used based on their policies and requirements.