Phone Registration & Risk
Checker Category: Identity — PII / Risk — Communication
Used In Steps: PII Validation (registration), PII Validation and SMS Link (risk add-ons)
Used In Workflows: Identity Verification, NIST IAL2, Continuous Re-Authentication
Overview
Phone Registration checkers verify a user's identity by matching their provided PII (name, address) against data sourced from mobile carriers for the provided phone number. They also return phone-level signals — account tenure, phone type, SIM/device status, and carrier-based location.
Phone Risk add-ons assess specific risk signals: SIM swaps, recent deactivations, and account tenure. These directly address attack vectors PII matching cannot catch — a fraudster who has SIM-swapped a victim's number, or is using a recycled or deactivated number.
End User Requirements
Mobile phone registered to the user (not prepaid, VOIP, or registered to someone else). Active cell service.
Role in Layered Verification
Phone Registration runs as part of the PII Validation step alongside the Authoritative Database checker — both run simultaneously. Phone Registration handles carrier-side corroboration; Authoritative Database handles the identity record side. Risk add-ons run as optional add-ons on the PII Validation or SMS Link API key.
Phone Registration Variants
Supported Countries: Select international markets. Contact your ID Dataweb team for current country coverage.
What It Provides: PII matching against mobile carrier data sourced from Boku's carrier network. Validates name and address against carrier records for the provided phone number. Returns carrier identity match scores (0–10 per field), phone type, status, and porting signals.
Acquired Attributes
| Attribute | Code | Description |
|---|---|---|
| Phone Service Type | PhoneServiceType | Mobile, landline, VOIP, prepaid, etc. |
| First Name Score | FirstNameScore | 0–10 match score for provided first name against carrier record |
| Last Name Score | LastNameScore | 0–10 match score for provided last name against carrier record |
| Street Address Score | StreetAddressScore | 0–10 match score for provided address |
| City Score | CityScore | 0–10 match score for provided city |
| State Score | StateScore | 0–10 match score for provided state |
| Postal Code Score | ZipCodeScore | 0–10 match score for provided postal code |
| Email Address Score | EmailAddressScore | 0–10 match score for provided email (if submitted) |
| Attribute Data Source | AcquiredAttributeDataSource | Data source for this attribute |
| Phone Carrier | PhoneServiceProvider | Carrier name for the provided phone number |
| Phone Service Country Code | PhoneServiceCountryCode | Country code for the carrier |
| Phone Type | PhoneType | Mobile, landline, VOIP, etc. |
| Phone Status | PhoneStatus | Active, inactive, suspended |
| Phone Ported From | PhonePortedFrom | Previous carrier if number was ported |
| Porting Date | PortingDate | Date of most recent port |
Assertions
| Assertion | Key | Description |
|---|---|---|
| Provided Full Name Partially Matches Identity Record Full Name | link.fullName_phone | Compares the provided full name to the full name in identity records for the provided phone number, using partial matching. Passes if a partial match is found; fails if no match is found. |
| Provided Last Name Linked to Provided Phone Number in Identity Record | link.lastName_phone | Compares the provided last name to the registered full name on record for the provided phone number. Passes if the last name matches; fails if it does not. |
| Provided Phone Number Linked to Provided Street Address in Identity Record | link.phone_address | Confirms that the provided phone number corresponds to the provided street address in identity records. Passes if a correspondence is found; fails if none is found. |
| Provided Phone Number Linked to Provided State in Identity Record | link.phone_state | Confirms that the provided phone number corresponds to the provided state in identity records. Passes if a correspondence is found; fails if none is found. |
| Provided Phone Number Linked to Provided Postal Code in Identity Record | link.phone_zip | Confirms that the provided phone number corresponds to the provided postal code in identity records. Passes if a correspondence is found; fails if none is found. |
| Phone Number Last Ported Check (>14 Days) | test.lastPortGT14days | Confirms that the provided phone number was last ported more than 14 days ago. Passes if the last port date exceeds this threshold; fails if it does not. |
| Phone Number Last Ported Check (> 30 Days) | test.lastPortGT30days | Confirms that the provided phone number was last ported more than 30 days ago. Passes if the last port date exceeds this threshold; fails if it does not. |
| Phone Number Active Check | test.phoneActive | Confirms that the provided phone number is currently active. Passes if the number is active; fails if it is inactive. |
| Phone Number Type Check | test.phone_landline_mobile_personal | Confirms that the provided phone number is a verified landline, mobile, or personal line. Passes if the line type is confirmed; fails if it cannot be. |
Notes
Match scores (0–10) provide more granularity than binary assertions — a score of 0 is no match, 10 is exact match. VoIP and non-carrier numbers fail PhoneServiceType checks. Recent porting (PortingDate) is a risk signal; pair with SIM Swap add-on for stronger coverage.
Phone Risk Add-ons
Optional add-ons that run alongside PII Validation or SMS Link to assess phone-level risk signals before verification proceeds. Enable these when phone-based possession is a meaningful assurance factor.
What It Provides: Detects recent SIM swaps — phone number transferred from one SIM card to another. SIM swap is a common fraud technique used to intercept OTP codes by taking control of a victim's phone number.
When to use: Always recommended when SMS Link or OTP grants meaningful account access. A recent SIM swap means someone else may currently control the phone number.
Acquired Attributes
Content coming soon.
Assertions
Content coming soon.
Notes
Carrier coverage varies — result may be inconclusive when data is unavailable from the carrier.
A swap within the last 30 days is a strong fraud signal; 30+ days is typically considered low risk.
Best used as a step-up trigger or hard block, depending on policy configuration.
Contact your ID Dataweb team for testing guidance — requires a real number with a recent port to trigger deny path.
Testing & Expected Results
Testing for registration variants follows PII Validation step procedures. See PII Validation for test credentials and step-by-step instructions.
- Approve: Andrew Roshell with a carrier mobile phone number
- Deny (phone type): VOIP or Google Voice number — fails phone type assertion
- SIM Swap deny: Requires a real number with a recent SIM port — contact your ID Dataweb team
- Deactivation deny: Requires a recently deactivated number — contact your ID Dataweb team
- Status + Tenure: Trigger with a newly activated number
Related Resources
→ PII Validation | → SMS Link | → Authoritative Database | → Identity Verification
Updated 2 days ago