Phone Risk Scope

Product tiers

Supported countries and formatting requirements

Phone Risk is available in 180+ countries, providing international phone-based identity insights. All phone numbers must be submitted in E.164 format.

International phone number formatting

All phone numbers must use E.164 format: a + prefix, followed by the country code, followed by the national number with no spaces, dashes, or parentheses.

Example: A United Arab Emirates mobile number 50 123 4567 with country code 971 becomes +971501234567.

Known limitations

• Dashboard phone field length: The RiskOS™ Dashboard phone input field may truncate numbers that exceed the expected length for a given country. If you encounter this issue when entering international numbers through the Dashboard, submit the phone number via the API in E.164 format instead.
• Country code required: Phone numbers submitted without a country code cannot be validated. Always include the full E.164 number including the + prefix and country code.
• Unsupported regions: If a phone number originates from an unsupported country, Phone Risk may return limited or no results. The evaluation continues with other available enrichments.

Industries it fits

• Financial services: Account opening, fraud prevention, progressive onboarding
• E-commerce: Checkout fraud prevention, return abuse detection
• Payments: Reduce risk in P2P transfers and high-value transactions
• Gaming & media: Stop fake accounts, bonus abuse, duplicate accounts
• Telecom: Validate new phone numbers during profile changes and SIM/line updates
• Call centers & CX: Real-time trust checks for number changes and OTP delivery
• Plus other digital onboarding and fraud risk workflows

Business and operational outcomes

1. For fraud and risk teams

• Identify high-risk phone numbers in real time.
• Reduce OTP-related ATO by validating the destination number’s risk and ownership.
• Leverage multiple model scores per call for testing and migration.
• Gain transparency with reason codes for both risk and correlation.

2. For growth and onboarding teams

• Progressive onboarding: Establish trust early with only a phone number (optionally name/address for correlation).
• Reduced friction: Let good users through while blocking risky numbers.
• Adaptive signals: Multiple models tuned for different fraud/risk trade-offs.

3. For support and operations

• Fewer escalations: Clearer signals reduce review queues.
• Transparent explanations: Reason codes help agents understand outcomes.
• Lightweight integration: Minimal required fields keep implementation fast.

Performance considerations

• Fast responses: Sub-second latency on average in production.
• Always available: 99.99%+ uptime with global redundancy.
• Built for scale: Supports tens of millions of risk checks per day.
• Smart models: Multiple models can run in parallel to optimize accuracy and fraud capture.

Boundary conditions

• Phone number + country are required: correlation accuracy improves when first and last name are also provided.
• Multiple models: Test challenger vs. production models to tune thresholds.