MNO Validation - UC01 Token Registration

When the user/customer tries to register their mobile token, MNO Validation prevents the registration of fraudulent mobile tokens.

Acceptance

• The number provided is a valid U.S. Mobile Phone Number.
• The Mobile Phone Number is active.
• The Mobile Phone Number was assigned by a Mobile Network Operator to a mobile plan containing the Payments Customer as an authorized user.
• The Payments Customer has control and possession of the Mobile Phone Number.
• The Mobile Phone Number is associated with a U.S. Mobile Network Operator, a U.S. Mobile - Virtual Operator or a Mobile Network Operator approved by the Network Operator.
• The Mobile Phone Number is not an international number (e.g., does not have an international subscriber identification module (SIM) card).
• The Mobile Phone Number is not a toll free phone number.
• This is for new enrollments only, not existing active enrollments

Flags involved

• MNOValidation flag - Configured on FI level
• MNOOverride flag - Configured on User level

API's involved

• PCS - FI Lookup, MNOOverride Lookup
• ENS - NotMobPhoneValidate

Twilio

• The backend provider of ENS NotMobPhoneValidate is Twilio. ENS_NotMobPhoneValidate uses LineType and Identity match services of Twilio.

LineType Possibilities

ENS_MNOLineTypeEnum	Description
Land	landline
Mob	mobile
FixVoip	fixedvoip
NonFixVoip	nonfixedvoip
TollFree	tollfree
Prem	premium
ShareCos	sharedcost
UAN	uan
VoiceMail	voicemail
Pager	pager
Unknown	unknown

IdentityMatch Possibilities

ENS_MNOIdentityMatchEnum	Description
Exact	Exact Match
HighPart	High Partial Match
Part	Partial Match
NoMatch	No Match
NotAvail	Not Available

Steps

1. The first step will be the FILookup to check the MNOValidation flag is enabled/disabled in user's FI level configuration. If it is enabled, proceed to second step; else, proceed to the register the token in EWS and PCS.

2. The second step will be the MNOOverrideLookup to check the MNOOverride flag. If it is overridden, proceed to the register the token in EWS and PCS; else, proceed to third step.

3. The third step will be the ENSLookup. We are using ENS_NotMobPhoneValidate contract to lookup the details. If the mobile tokens's line type is mobile and first name, last name match is matched with the name in ENS -- EntityConfdScore, we can proceed to the register the token in EWS and PCS; else, error out.

Note

MNO Validation is applicable only to Token Register and not Token Transfer.

Sequential diagram of MNO Validation - UC01