User Guides
Home

Migrate to SocureID for Identity Resolution

Migrate your persistent identity identifiers to SocureID for deduplication, cross-platform identity resolution, and fraud consortium access.

What is SocureID?

SocureID combines Socure's top-tier identity verification with predictive analytics to assign a reliable, privacy-focused unique ID to each identity. You can leverage SocureID for various use cases, such as:

A major social media platform implemented SocureID to combat the proliferation of ghost accounts, significantly enhancing user trust and platform integrity.

Here's how it works:

  • SocureID utilizes advanced algorithms to analyze user profiles and identify patterns indicative of ghost accounts. It detects anomalies such as similar identity characteristics, lack of genuine activity, suspicious creation patterns, or bot-like behavior.
  • The system cross-references user data across multiple dimensions—email addresses, phone numbers, IP addresses, and behavioral patterns—to uncover networks of ghost accounts. SocureID assigns risk scores to accounts, enabling the platform to take appropriate actions, from requiring additional verification to suspending suspected ghost accounts.
  • As a result, the platform experienced a significant reduction in fake followers, artificial engagement, and coordinated inauthentic behavior. Real users enjoyed more genuine interactions, as ghost accounts were systematically identified and removed. This clean-up process led to more accurate follower counts and engagement metrics, providing authentic influencers and brands with a true measure of their reach.
📘

Info:

SocureID is available by default for Socure Verify Plus customers. If you would like to provision this feature for your Socure Verify, reach out to your Technical Account Manager.

Prerequisites for migration

Ensure you have the following prepared for your migration process:

  • API credentials: Make sure you have a valid API key for sending requests to the RiskOS™ API.
  • Existing identifier system: Identify the current persistent identifier system you are migrating from (e.g., LexID, CID, etc.).
  • Mapping method: Determine the method you will use to map existing identifiers to SocureIDs.

How it works

You can quickly migrate to SocureID by following the steps below:

1. Obtain SocureIDs for existing identifiers

To obtain a SocureID for an existing identifier, send a POST request to the RiskOS™ API endpoint. Ensure to include the data.individual.id field in the request to pass the existing identifier. Your data.individual.id could be something you created to track each consumer uniquely or something you received from a legacy provider.

Below are example requests:

{
    "id": "APP-123456",
    "timestamp": "2022-07-28T06:10:54.298Z",
    "workflow": "consumer_onboarding",
    "data":
    {
        "individual":
        {
            "id": "60796b83-bd1c-4914-9d08-6b340d18a956",
            "given_name": "Blair",
            "family_name": "Kawashima",
            "national_id": "598003289",
            "date_of_birth": "1980-07-05",
            "phone_number": "+13475550100",
            "address":
            {
                "line_1": "32194 N College Ave",
                "locality": "New York City",
                "major_admin_division": "NY",
                "country": "US",
                "postal_code": "10001"
            },
            "additional_context" : 
            {
              "user_consent" : true,
              "consent_timestamp": "2020-05-26T13:34:43Z"
            }
        }
    }
}

A successful API call returns the unique socureId for the submitted data.individual.id, as shown below:

{
    "id": "APP-123456",
    "eval_id": "6dc8f39c-ecc3-4fe0-9283-fc8e5f99e816",
    "decision": "REVIEW",
    "tags": [...],
    "review_queues": [...],
    ...  
    "data_enrichments":
    [
        {
            "enrichment_name": "Socure Verify",
            "enrichment_endpoint": "https://sandbox.dev.socure.com/api/3.0/EmailAuthScore",
            "enrichment_provider": "Socure",
            "status_code": 200,
            "request":
            { ... },
            "response": 
            {
                "referenceId": "a1b23456-7cd8-9012-abc9-d86531bffdd5",
                "socureId": "ab06216f-b88b-4be8-8075-933bb5c2303c", 
                "userId": "60796b83-bd1c-4914-9d08-6b340d18a956",
                "kyc": {
                  "reasonCodes": [
                    "I919"
                  ],
                  "fieldValidations": {
                    "firstName": 0.99,
                    "surName": 0.99,
                    "streetAddress": 0.99,
                    "city": 0.99,
                    "state": 0.99,
                    "zip": 0.99,
                    "mobileNumber": 0.99,
                    "dob": 0.99,
                    "ssn": 0.99
                 }
               }
           }
        }
    ]    
}

2. Map SocureIDs to your existing consumer base

To effectively map SocureIDs to your existing consumer base:

  • Create a database table or spreadsheet with columns for your existing consumer identifier and the new SocureID.
  • Iterate through your consumer database, making API calls for each consumer to obtain their SocureID.
  • Store the mapping between your existing identifier and the new SocureID in your created table or spreadsheet.

Benefits of mapping:

  • Unified consumer view: By mapping SocureIDs to your existing identifiers, you create a bridge between your current system and the new, more accurate Socure system.
  • Seamless transition: This mapping allows you to gradually transition to using SocureIDs without disrupting your current operations.
  • Historical data preservation: You maintain the connection to historical consumer data while benefiting from Socure's enhanced identity verification.

3. Update and clean up CRM/contact information using Verify Plus responses

Socure Verify Plus provides rich, verified information about each identity. You can use this data to enhance and correct your existing consumer information.

  1. When you receive a Verify Plus response, compare the returned data with your existing CRM data.
  2. Update your CRM with the verified information from Socure, focusing on fields like name spelling, address formatting, and phone number validation.

Benefits of CRM cleanup:

  • Improved data quality: Socure's verified data helps correct inaccuracies in your existing records.
  • Enhanced consumer communication: With more accurate contact information, you can improve your consumer outreach efforts.
  • Reduced fraud risk: By identifying and correcting discrepancies, you can flag potential fraudulent entries for further investigation.
Visual representation of data cleanup

Here's an example of how the data cleanup process might look:

FieldOriginal CRM DataSocure Verified DataAction
Identifier60796b83-bd1c-4914-9d08-6b340d18a956ab06216f-b88b-4be8-8075-933bb5c2303cUpdate to SocureID
First NameBlaireBlairUpdate to Blair
Last NameKawashimaKawashimaNo change needed
Address32194 N Colege Ave32194 N College AveCorrect spelling
CityNYCNew YorkExpand abbreviation
Phone347-555-0100+13475550100Format to E.164
DOB07/05/19801980-07-05Standardize format

4. Implement SocureIDs in your systems

To complete the migration:

  1. Extract the socureId returned in the API responses.
  2. Update your systems to use SocureID as the primary identifier for consumer records.
  3. Maintain the mapping between your original userId and socureId for reference and data consistency checks.

By implementing these steps, you'll successfully migrate to SocureID, improving your identity verification process and data quality across your organization.

5. Testing your integration

Before fully migrating, test your integration:

  1. Create test customers in your staging environment.
  2. Obtain SocureIDs for these test customers.
  3. Verify that your systems correctly use SocureIDs for all operations.
  4. Confirm that data cleanup processes are working as expected.

Updated 3 months ago

Did this page help you?