Fraudsters can fake a name, a document or a phone number on their own, but making every detail fit one coherent identity is much harder. The cracks usually show in where an application comes from: the network, device, location or channel behind it.

A high-risk source of application is the flag lenders and financial services apply when that origin looks risky, regardless of how credible the applicant’s details appear.

What Does High-Risk Source of Application Mean?

Risk teams use the label to describe an application whose origin raises concern, even when the applicant’s identity looks valid. “Source” covers more than geography: it includes the internet connection, the device used to apply, the history behind the contact details and the channel that delivered the application, such as an affiliate site, broker or retail partner.

This is why a legitimate person can receive the flag. Someone who applies through a VPN, from a device previously linked to other applications or through a partner with a record of bad referrals may be scored as high risk before anyone reviews their documents.

The term also overlaps with anti-money laundering (AML) compliance. Applications from sanctioned jurisdictions, or from applicants who match a politically exposed person (PEP) or sanctions list, carry regulatory risk on top of fraud risk and need screening under your AML program.

What a High-Risk Source Flag Means for Applicants

The flag is about where an application came from, not about the person behind it. A genuine applicant can still get it if their location online doesn’t match their home address, if they apply through a VPN or if they use a device that has already been used for other applications.

That is also why the reason is rarely explained in detail. Rejected applicants usually receive an automated message with limited information, because revealing which signals triggered the decision would show fraudsters what to change.

What Counts as a High-Risk Source of Application?

Each signal below raises a question rather than proving fraud, so the third column matters as much as the second. A strong decision tests the legitimate explanation before acting on the risk.

SignalWhy it raises riskLegitimate explanation to rule out
IP location far from the stated addressThe applicant may be hiding where they really areTravel or a corporate network
VPN, proxy, Tor or data center connectionThe real network origin is maskedCorporate networks, travel and privacy-conscious users
Device location that contradicts the IP and addressThe location claim may be spoofedA VPN or corporate network routing traffic elsewhere while the device sits where the applicant says
A device already seen behind other applicationsOne person may be applying with several identitiesA device shared by a household, workplace or family
Emulator, virtual machine or device farm indicatorsOne operator may be posing as many applicantsRare for loan applicants; occasionally developers or enterprise-managed devices
A channel, affiliate or merchant with unusual application patternsA partner may be complicit or sending low-quality trafficUnrelated customers arriving through the same marketing campaign
IP or device located in a sanctioned jurisdictionRegulatory and money laundering riskTravel, or a VPN routing traffic through that country

Why High-Risk Applications Pass KYC and Credit Checks

Identity checks confirm that a document is genuine and that the person matches it. They do not confirm that the applicant intends to repay, or that someone else isn’t using the identity, which leaves room for synthetic identities, stolen IDs, money mules and coached applicants.

Risk teams describe the same pattern across lending, BNPL and consumer finance: much of the fraud that reaches the loan book passes identity and credit checks, looks like a real person throughout onboarding and only shows itself when the first payment is missed and the borrower stops responding.

Automation raises the stakes further. AI agents now complete applications accurately and faster than any person, and device farms run real phones remotely so each session looks organic. Every application can look ordinary on its own, which is why checking the source matters: it shows where an application came from and through what, not only what it contains.

High-Risk Countries and Jurisdictions

Most organizations start with sanctions lists. Applications linked to sanctioned jurisdictions carry regulatory risk regardless of any fraud signal and which lists apply depends on where your company operates, since they differ by region.

These lists also change quickly. A new sanctions designation can appear overnight, so a country table copied into a rulebook goes stale. Screen against directly sourced, regularly updated data in real time instead.

Many teams also keep internal high-risk lists based on their own losses. These help, but country blocking alone rarely solves fraud, because attackers simply route the same attempts through IP addresses in countries you still allow.

SEON investigations point the same way. In one case, a device country mismatch was the only red flag across a batch of accounts and it turned out to be the least stable part of the pattern. Treat location as the start of an investigation, then confirm it with independent evidence.

How to Detect High-Risk Sources of Application

The methods below work best in combination. Each one adds evidence that a single check would miss and together they let you clear good applicants quickly while concentrating scrutiny where the risk actually sits.

1. Check the Application Before Paying for KYC

Device, network, email and phone checks run in milliseconds without asking the applicant for anything. Running them at the first form submission filters obvious fraud before you pay for document and selfie verification and gives you context for every decision that follows.

2. Compare Where the Applicant Claims to Be With Where the Device Is

Cross-check the stated address against the IP location and, where the applicant grants permission, the device’s GPS position. A VPN user whose device sits in the same city as their address is a very different case from a device in another country routing through a residential proxy.

“Using a VPN is not a crime, but a VPN exit in one country, a stated address in another and a phone carrier in a third is a story that doesn’t hold together.”

Jane Singh, Sr. Product Marketing Manager (Fintech)

3. Recognize Returning Devices Behind New Identities

Fraud rings rotate names, emails and phone numbers, but they reuse hardware. A persistent device identifier that survives factory resets, reinstalls and private browsing reveals when one device sits behind several supposedly new applicants.

Organized fraud groups now generate a new device identifier for every account, so also look for hardware characteristics that should differ between real devices but don’t. In one SEON investigation, a single fraud group ran 197 accounts that shared no device identifiers, yet five unrelated hardware characteristics were identical across all of them.

Emulator and virtual machine sessions deserve a firmer response in lending than elsewhere. Genuine applicants rarely submit a loan application through these environments, so they warrant review or decline rather than a small score increase.

4. Score Each Channel and Partner Separately

Tag every application with the channel, affiliate, broker or merchant that sent it, so you can compare approval, fraud and default rates by source. A partner whose applicants suddenly share devices, addresses or near-identical details is sending a pattern that no single application reveals.

Velocity rules, which count how often a device, IP address or partner appears within a time window, surface these bursts as they happen. In lending, the number of applications from the same device within 48 hours is a core signal to track.

Where applications arrive through third-party forms, you may not capture device data at all. Weight email, phone and channel signals more heavily for those flows and route uncertain cases to step-up checks sooner.

5. Screen for Sanctions and PEP Matches With Risk-Based Settings

Check every applicant against sanctions, PEP, watchlist and crime lists, but don’t apply the same rules to everyone. Set how closely a name must match a list entry by jurisdiction and product, so high-risk segments get strict thresholds while low-risk ones don’t flood your team with false positives.

Timing matters as much as tuning. A new designation can appear overnight and a nightly batch check can approve an application before the next update catches it, so screen in real time at the point of application. An automated first review of each hit then clears obvious false positives before they reach an analyst.

6. Score Signals Together, Not One at a Time

No single signal should decide an application. Add a modest score for a VPN, another for a new email address and another for a device mismatch, then reserve the firmest responses for signals that are rarely legitimate for loan applicants, such as emulator sessions and Tor traffic.

Context such as age, product and loan amount changes what each signal means. Younger borrowers and recent movers share surface traits with synthetic identities, so rules that combine signals protect genuine thin-file applicants while still catching the combinations real customers rarely produce.

Use the applicant’s contact details as a cross-check rather than a verdict. An email address or phone number with no online history, or one other businesses have reported for fraud, adds weight when the device, network or channel already looks wrong.

What to Do When You Detect a High-Risk Application

Match the response to the strength of the evidence. Approve low-risk applications automatically, decline those with clear fraud indicators and step up the uncertain middle with document, selfie or bank verification instead of declining outright, which keeps good customers moving.

Size the manual review queue deliberately. If reviewers spend most of their time clearing anomalies you already know are legitimate, adjust rule weights rather than adding headcount.

If a review raises suspicion of money laundering, file a suspicious activity report (SAR) to notify the relevant authorities. Give rejected applicants a route to appeal, but avoid revealing the specific signals behind the decision, since that shows fraudsters what to change.

Finally, feed outcomes back into your rules and models. Label applications that end in fraud or first payment default and expect those labels to take one to three months to mature, because early-payment fraud only becomes visible once the first due dates pass.

How SEON Helps Detect High-Risk Sources of Application

Source signals are most useful when they arrive before the expensive checks and when your team can see why they fired. SEON analyzes the network, device and location behind each application as it is submitted, so you can filter out or step up risky sources before identity verification starts

Device intelligence recognizes when a device returns behind a new identity and flags emulators, device farms and automated sessions. It also compares GPS, IP and browser network data to show whether an applicant is really where they claim to be.

Contact details then act as a cross-check rather than a verdict. Digital footprint analysis shows whether an email address or phone number has a history online and sanctions screening runs in the same workflow, so location risk and regulatory risk are assessed together.

Each decision shows the signals and rules behind it, so your team can explain outcomes and adjust rules as fraud patterns change.

Explore digital footprint analysis or speak with an expert to see how this fits your application flow.

Take the First Step Toward Transformative Fraud Prevention