FAQ

CNAM data is pulled from telecom industry Line Information Databases (LIDBs) managed by carriers and aggregators.
Coverage varies depending on carrier and phone type (landline, VoIP, mobile), so not all numbers will return a caller name.

CNAM is available as an enrichment step in RiskOS™ workflows.

• It cross-checks the name a user provides against the registered name for their phone number.
• Mismatches can indicate potential fraud.
• Once enabled, CNAM results can be referenced by subsequent workflow steps and decision logic.

The only required parameter is phone_number in E.164 format (e.g., +13475550100).

It can be placed in either the individual or business JSON object in the request payload.

No. CNAM is limited to U.S. and Canadian phone numbers. International numbers are not supported.

Yes. Phone numbers must be in E.164 format (e.g., +15555551234).
Omitting the plus (+) can cause lookup failures. RiskOS™ has some fallbacks, but correct formatting is strongly recommended.

• Only supported in the U.S. and Canada
• Not available for unregistered numbers or numbers with carrier-level CNAM blocking
• Should not be used as sole proof of ownership or association

RiskOS™ sandbox supports test cases with predictable results.

• Example: For +1-415-555-1212, the sandbox returns "John Doe".
• If you see a 404 error:
  • Confirm number formatting
  • Ensure API keys are valid for the correct environment

No. CNAM is not sold as a standalone Socure product.
It is offered as an enrichment, often included in prefill or identity verification bundles.

• Account Manager → Enablement and workflow integration
• Socure Support / Solution Consultant → Technical issues or endpoint troubleshooting