Recently in Global Phone Verification Category

Verify National ID like SSN with Personator

| No Comments | No TrackBacks

by Michael Johnson, Sales Engineer

Personator has never yielded the crown of contact verification, and that is no accident.  Personator is the quintessential contact verification service.  Nowhere else can you find a fast, no maintenance, easy-to-use web service that will give you a level of certainty your data is not only good, but that it is correct.  One of our newest features in our flagship service to be released is Personators SSN Verify.

Personator SSN Verify adds an integral feature of contact verification to Personator that had not existed before: the ability to verify that an individuals' SSN belongs to them.  Personator now has the ability to take in a social security number and full name and tell you whether or not they match.  We chose not to stop there, but we give you the power to dictate how much of your SSN and name to verify.  Do you want to know if your last name was correct to the SSN? 

What about the correct full name to last 4 SSN?  Our newest option, SSNCascade, allows you to determine whether or not we attempt to drill down and verify multiple segments of your social security number and name combination.

·         Full Name and Social Security

·         Last Name and Social Security

·         Full Name Last 4 Social Security

·         Last Name Last 4 Social Security

We don't just stop at verifying the social security number and name; we crank up the volume to 11.  If the SSN and Name are verified as a match, we allow you to have the option to append information regarding that person.  We are able to append the address, phone, email, demographic data, and census data all regarding the matched individual.

Personator is our flagship product which leads the industry of contact verification. You will be hard pressed to find another single product with so much potential.  We continually add new features and sources to our arsenal, which not only gives the end user more options but will give them more confidence that their data is correct.


By Kevin Ubay-Ubay, Sales Engineer

Global ID Verification is Melissa's powerful cloud service that gives one single, simple way to clean and verify your global contact data. Leverage our experience in name, phone, address, and email validation to gain comprehensive contact checking and identity-level verification.

Our web service may be applied to:

  • Age verification
  • Name-address verification
  • Anti-fraud applications
  • Online shopping cart & eCommerce platforms
  • FinTech/Banking

When you need your contact data checked and verified, Global ID Verification begins with standardizing and validating your records. At this stage, the service will parse and standardize your data as well as check for the following:

  • Name is in a valid format
  • Address is deliverable
  • Email address exists
  • Phone number is callable


  • Full Name: John doe
  • Phone: 8458692102
  • Email:
  • Address Line 1: 1 unicorn
  • City: norwich
  • Administrative Area: Postal
  • Code: NR33AB Country: GB


  • Full Name: John doe
  • Phone: +44 8458692102
  • Email:
  • Address Line 1: :1 Unicorn Rd
  • City: Norwich
  • Administrative Area: Norfolk
  • Postal Code: NR3 3AB
  • Country: GB

In the diagram above, you can see the final result of reformatting. Casings are changed and abbreviations are corrected. Continuing the process, you gain missing street suffixes, phone country dialing codes, missing state/province/administrative area info, and even typographical email domain corrections. For example, will be adjusted to

Next, Global ID Verification evaluates your data against trusted reference data in order to verify each individual's information so you can be confident that names and communication channels are current.

In this verification stage, the web service takes the standardized name, phone, email, and address from the previous stage and performs ID verification. Additional input, such as an individual's national ID, such as a social security number and date of birth can be verified as well; depending on the country of origin.


  • Full Name: John Doe
  • National ID: HJDO840230HVZRRL05
  • Date of birth: 2/30/1984
  • Phone: +56-222-226-8000
  • Email:
  • Address Line 1: Paseo De Los Conquistadores 2000
  • City: Guadalupe
  • Administrative Area: NL
  • Postal Code: 67170
  • Country: MX


  •  KV01 - Address matched

  • KV02 - National ID matched

  • KV03 - First name matched

  • KV04 - Last name matched

  • KV05 Phone number matched

  • KV06 Email matched

  • KV07 Date of birth matched

The diagram above shows how the service will return result codes indicating which information has been matched. By observing what kinds of result codes are returned, you may determine how reliable your data is.

Global ID Verification will be available as a web service hosted on our servers - which means you won't have to worry about updates and maintenance. Information about the countries supported and the level of coverage may be found on our wiki at Sample code and documentation is also provided to help you get a jump start on building applications and services incorporating our ID Verification technology.

By Allison Moon, Global Phone Channel Manager

For most businesses, it's important for you to keep contact with clients, which means ensuring that the correct contact information is always available. Using Melissa's Global Phone Cloud Service, you can check on phone number validity, activity status, and also distinguish between landlines, cell phones, append geographical information, access real-time lookups, and more.

Integrating and uplifting your business with the Melissa Global Phone Cloud Service provides multiple capabilities. By using the service, you can sift out landlines and mobile numbers and execute custom communication techniques to each type. For example, if a number is detected to be a cell phone, then SMS messages can be sent to alert them of credit limits or send messages about arriving packages.

Service Level Capabilities

The Global Phone Cloud Service has two levels of capabilities that cater to different users. Our Express level is the default and primary step to phone validation. With this level, you'll be able to access our line-range data as well as our database of known phone numbers. This determines validity, phone type, carrier information, and appends geographical information (e.g. predominant language spoken in the area, general latitude/longitude points, city name, etc.). Premium level users will get all the capabilities of the Express level, as well as access to real-time lookups for more accurate phone type and active number detection.

Another major capability of the new service is our Suggestion feature. Suggestions are now returned for numbers that were undetermined on input. If a single request is sent, and we are unable to validate it with the data set on input, the response will include an array of possible countries where the number exists. This can be useful in determining alternatives to the inputted data and help you narrow the search to your point of contact.

Version: "",
TransmissionReference: "",
TransmissionResults: "",
Records: [
RecordID: "1",
Results: "PE04",
PhoneNumber: "",
AdministrativeArea: "",
CountryAbbreviation: "",
CountryName: "",
Carrier: "",
DST: "",
Language: "",
Latitude: "",
Locality: "",
Longitude: "",
PhoneInternationalPrefix: "",
PhoneCountryDialingCode: "",
PhoneNationPrefix: "",
PhoneNationalDestinationCode: "",
PhoneSubscriberNumber: "",
UTC: "",
Suggestions: [
RecordID: 1
Results: PS01,PS08,PS20
PhoneNumber: 94941135624
CountryAbbreviation: LU
CountryName: Luxembourg
Carrier: Entreprise des Postes et Télécommunications
Language: French
Latitude: 49.60000000
Longitude: 6.15000000
PhoneCountryDialingCode: 352
PhoneNationalDestinationCode: 949
PhoneSubscriberNumber: 41135624
UTC: +01:00
RecordID: 2
Results: PS01,PS08,PS20
PhoneNumber: 94941135624
AdministrativeArea: Uusimaa Helsinki
CountryAbbreviation: FI
CountryName: Finland
Carrier: Elisa Oyj
Language: Finnish
Latitude: 60.169812
Longitude: 24.93824
PhoneCountryDialingCode: 358
PhoneNationPrefix: 0
PhoneNationalDestinationCode: 9
PhoneSubscriberNumber: 4941135624
UTC: +02:00

The Best Way to Stay in Touch

Keeping a well-cleansed database of active phone numbers can allow you to keep close communications with your customers and keep your customer relations strong. Learn more.

Validating Global Phone Numbers 101: A Quick, Easy Tutorial

| No Comments | No TrackBacks

By Allison Moon Data Quality Analyst 

With the advent of global communications and business, chances are you are not only capturing addresses of your contacts, but contact phone numbers as well. This is where Melissa's Global Phone Object comes into play.

Global Phone Object validates registered phone numbers in more than 240 countries and territories, as well as enrich your data by appending information such as latitude, longitude, city, predominant language spoken, and more.

Setting up the object is quick and easy, especially if you're a current customer of any other Melissa API.

Here's a quick tutorial:

First, add the Phone Object DLL or .SL file to your project and instantiate an instance of the Global Phone Object:

SET globalPhonePtr as NEW Instance of GlobalPhone

Second, set your license string: 
CALL SetLicenseString WITH LicenseString

Next, initialize the data files:
CALL Initialize WITH DataPath RETURNING Result
IF Result <> 0 THEN
     CALL GetInitializeErrorString RETURNING
    PRING "Error: " & ErrorString

Now you're ready to start validating phone numbers! Using the 'Lookup' method, you can now loop through and feed your contact phone numbers through the object. For best results, pass in both the phone number and country associated with it with the Lookup method. If you require all the digits necessary for dialing internationally from your country, you will also need to pass in the Country of Origin (e.g. the country from which the caller is dialing from).

The outputs returned from the Global Phone Object are useful for call-centers or businesses that would benefit from knowing about the general area the contact is located. For instance, the UTC (Universal Time Code) output can help the caller schedule an appropriate time to dial the contact and the language output can provide the caller information on the language most comfortable for the contact.

The appended regional information, such as the latitude, longitude, locality (city), and administrative area (state) can be sued to get a general sense of where the majority of your contacts are located.

If you're capturing international contact information, the Global Phone Object will be a useful tool in determining registered phone numbers, standardizing phone number formats, and understanding more about where the contact is located.


To test Global Phone for free, go to:


Melissa provides numerous APIs to handle the standardization, cleansing and verification of various data elements such as addresses, names, phones and emails. Often times we get asked by our customers as to what are some ways to improve the speed when processing records using our APIs. Below are some performance tips to consider when implementing our APIs:



The type of medium where the data files are stored may have an impact on processing speed. We recommend the use of solid state drives to store our data files as they have faster seek & read times compared to spinning disk drives.

We have also sometimes seen clients store the data files on a network share which we definitely don't recommend. Typically, trying to access the files over a network introduces latency which impacts the processing speed when blocks of data need to be fetched quickly. Data files, therefore, should often be stored locally on the machine.



The amount of memory available and speed can also affect processing. While using the APIs, once data is read from the hard drive, the data is cached and stored temporarily into memory in case the data needs to be accessed again shortly.


A simple example below, we have a list of phone numbers that were verified using our Phone Object API along with the times in milliseconds indicating the amount of time to verify the phone number.


When the Phone Object API encounters a phone number in a new area code, there are spikes in the verify times as the Phone Object now has to go back and fetch a new block from the data files stored on a hard disk and cache it into memory. The more memory available on the system, the more that can be cached into memory as the API reads more blocks from the data files on the disk. And, as discussed in the previous section, having a faster hard drive will help keep those disk read times low when those data file reads occur.



Processors with more than a single core are now common these days. If multiple cores are available on the system, we highly recommend that developers take advantage of that. When multithreading with our APIs, we suggest having each thread contain its own object instantiation for our APIs. 

For example, if you have 8 cores, you may want to create 8 threads with our API instantiated 8 times: once per each thread. Ideally, you would want to create a pool of threads that have our API instantiated already, and therefore ready for processing. If you keep reinitializing/instantiating our API, that will introduce some overhead in the processing.


The graph and table below shows some multithreaded testing of our own with our Global Address Object® API with UK addresses and, as shown, there as substantial speed increases that can be obtained through multithreading: