Skip to main content

Email and phone verification

Assesses trust signals from a user’s contact details​

Helps businesses identify suspicious or trustworthy behaviour based on email, phone, name, and IP data before the user continues with e.g. identity verification or electronic signiture processes.

Key features​

  • Computes a trust score from email, phone, IP and name signals.
  • Routes flow using configurable thresholds: suspiciousUserThreshold and trustedUserThreshold.
  • Required inputSources to specify step IDs (basicIdentity, extendedIdentity, deviceSignals). Must cover at least 2 potential claims.
  • Produces DigitalSignals for trusted, suspicious, and not_trusted; inconclusive when no definitive assessment.

Configuration​

ParameterTypeRequiredDefaultDescription
suspiciousUserThresholdIntegerYesThe score threshold (in percent) below which a user is considered "suspicious".
trustedUserThresholdIntegerYesThe score threshold (in percent) above which a user is considered "trusted".
inputSourcesObjectYesSpecifies the flow step IDs to use for sourcing data. The configuration must cover at least 2 potential claims: basicIdentity contributes 1 claim, extendedIdentity contributes 2 claims (phone + email), and deviceSignals contributes 1 claim. Note that extendedIdentity alone satisfies this requirement. See Input mapping.
inputSources.basicIdentityStringNoThe step ID providing basic identity data (e.g., first name, last name).
inputSources.extendedIdentityStringNoThe step ID providing extended identity data (e.g., phone, email).
inputSources.deviceSignalsStringNoThe step ID providing device signal data (e.g., IP address).

Input data blocks​

Data blockRequiredDescription
BasicIdentityNoProvides name signal (1 claim). Only consumed when inputSources.basicIdentity is configured.
ExtendedIdentityNoProvides phone and email signals (2 claims). Only consumed when inputSources.extendedIdentity is configured.
DeviceSignalsNoProvides IP signal (1 claim). Only consumed when inputSources.deviceSignals is configured.

The inputSources configuration must cover at least 2 potential claims in total. extendedIdentity alone satisfies this requirement. The referenced steps must have already produced the corresponding data blocks before this step executes.

Routes​

Routes for this step.

RouteDescription
trustedThe score computed is greater than or equal to trustedUserThreshold.
suspiciousThe score computed is strictly between suspiciousUserThreshold and trustedUserThreshold.
not_trustedThe score computed is less than or equal to suspiciousUserThreshold.
inconclusiveThe provider cannot compute a definitive score or assessment.

Output data blocks​

Data blocks produced per route.

RouteData blocks producedNotes
trustedDigitalSignals
suspiciousDigitalSignals
not_trustedDigitalSignals
inconclusiveDigitalSignals