Skip to content
Fraud recognition

Spot synthetic identities before they cost you.

Check the name, email, phone and address on a signup or transaction against 269M+ real US profiles. When the details do not belong to the same real person, flag it for review.

One API call
POST /api/v1/enrichment/email
{ "email": "dana@northlinelogistics.com" }

200 OK
{ "first_name": "Dana",
  "job_title": "VP of Operations",
  "mobile_phone": "15125550148",
  "business_email_validation_status": "Valid (Esp)",
  "company": { "name": "Northline Logistics",
    "employee_count": "251 to 500" } }
Sample response with a made-up person, trimmed. Full reference in the API docs.
The problem

Why synthetic identities get through

01

Every field looks valid alone

A real-looking email, a working phone and a real address can be stitched together from different people.

Check whether they all belong to one real profile.
02

Review queues keep growing

Manual review cannot keep up when every borderline signup goes to a person.

Clear matches pass on their own, so reviewers see fewer cases.
03

Stricter rules punish good users

Every new check adds friction for the customers you actually want.

Run the check in the background with no extra steps for the user.
How it works

How a check runs

STEP 01A signup or transaction

Your system sends the email or phone number the user entered.

STEP 02Compare to the graph

LeadFuze returns the profile on file: name, addresses, phones and email validation status.

STEP 03Decide

Approve when the details line up, and route to review when they do not.

Fields you can compare
DWDana WhitfieldVP of Operations, Northline LogisticsMade-up person
First nameDana
Last nameWhitfield
Personal emailsdanawhitfield@gmail.com
Personal emails validation statusValid (Esp)
Mobile phone15125550148
Personal phone+15125550173
Personal address1180 Oak Ridge Dr
Personal cityRound Rock
Personal stateTX
Personal ZIP78681
DPV codeY
11 of 60 fields shownSee all 60 fields
Questions

Fraud Recognition, answered.

Something else on your mind? Ask the data team.

How does LeadFuze help detect synthetic identity fraud?

Send the email or phone a user entered and compare the profile on file with the name and address they gave. When the details belong to different people, or to no one, flag the account.

What is the DPV code?

Delivery point validation from the postal service. Y means a confirmed deliverable address, which helps separate real home addresses from made-up ones.

Can I run checks in bulk?

Yes. Upload a CSV of emails through the bulk enrichment endpoint and download the results when the job finishes.

Keep exploring

Teams that use this also look at

Try it on your market

Test it on your own signups.

Run a sample of past signups through the API and compare the results with the accounts you already know were fraud. API access comes with every plan.