Evidence Framework
- Tier 1 = Direct evidence to verify: Confirmed unauthorized use or identity misuse tied to the case, not a device or IP match alone
- Tier 2 = Supporting signals: New contact details, device anomalies and unusual behavior need context
- Decision: Use signals to route investigation. Classify fraud only when the evidence supports it; unresolved stays unknown
- Write it down: What you found, where it came from and why you decided, the day you decide
Deciding whether a suspicious order is fraud? Sort what you've got into two tiers. Neither a signal count nor a shared identifier proves that this customer committed fraud. Rows on SSNs, bureau data and never-pay apply if you lend or extend credit. Skip them if you don't.
Overview
Not all fraud signals are equal. Sort them by confidence and you'll call the same case the same way twice.
Tier 1 = Direct evidence, verified against the case
Tier 2 = Supporting signals, checked for legitimate explanations
Tier 1 Indicators
Check what each source actually shows about this case. A data error or a stolen identity record doesn't by itself make the applicant or this order fraudulent:
Identity-Related
| Indicator | How to Confirm |
|---|---|
| Identity details conflict with official records | Verify the record, correct errors and offer a secure escalation path |
| Identity confirmed as fraud victim | Police report, affidavit, bureau alert |
| SSN belongs to deceased individual | Bureau data, death records |
| Submitted SSN, name and date of birth don't match | An authorized SSA route, such as eCBSV, with written consent and eligibility. It can return a death indicator. Resolve the specific mismatch, because a no-match alone doesn't prove identity fraud |
| Document forensically invalid | Document verification technology |
Pattern-Related
| Indicator | How to Confirm |
|---|---|
| Device/IP linked to confirmed fraud | Verify the link to this case; shared devices and networks can include legitimate users |
| Address used by known fraud ring | Consortium data, internal analysis |
| Exact application data matches confirmed fraud | Compare the application's name, address, phone, email and device with the confirmed case; a specialist or your fraud tool does this at scale |
| Account explicitly claimed by identity theft victim | Affidavit, manual review |
When direct evidence establishes unauthorized use in this case, follow your incident procedure and document the reason. If it only points to an anomaly, keep investigating. Don't turn a match into a fraud label.
Tier 2 Indicators
Supporting signals can justify investigation. Several correlated signals may describe one legitimate circumstance, so adding them up doesn't prove fraud. The weights and counts below are illustrative settings for routing work. Test them on cases you've resolved as fraud or legitimate, and on the unknowns, all old enough for the outcome to have come in.
Application Signals
| Indicator | Weight | Notes |
|---|---|---|
| Email first seen recently, on your provider's observed-age field (AtData is one) | ⚠️ Medium | A first-seen date isn't a creation date, and new customers have new addresses too |
| Phone recently ported | ⚠️ Medium | SIM swap indicator |
| Address mismatch (stated vs. bureau) | ⚠️ Low | May be recent move |
| Employment unverifiable | ⚠️ Medium | Check method matters |
| Income stated >> bureau income indicators | ⚠️ Medium | Could be recent change |
Behavior Signals
| Indicator | Weight | Notes |
|---|---|---|
| Never-pay (0 payments from origination) | ⚠️ High | Not conclusive (see first-party fraud) |
| Bust-out pattern (utilization spike) | ⚠️ High | May be financial hardship |
| Device seen on prior fraud (1-2 cases) | ⚠️ Medium | Could be shared device |
| Velocity anomaly | ⚠️ Medium | Context dependent |
Link Analysis Signals
| Indicator | Weight | Notes |
|---|---|---|
| Same phone on multiple identities | ⚠️ Medium | Could be family |
| Same device on multiple identities | ⚠️ Medium | Could be shared device |
| Address velocity (for example, 3+ apps, same address, 30 days) | ⚠️ High | Can point to a ring. Could also be a shared building or household |
Decision Matrix
Classification Rules
| Evidence | Classification |
|---|---|
| Verified evidence of unauthorized use tied to this case | Confirmed fraud, with rationale documented |
| Identity or record anomaly not yet resolved | Investigation; keep the outcome unknown |
| Multiple supporting signals | Prioritize review using case value, risk and capacity |
| One supporting signal | Check its reliability and legitimate explanations |
| No listed indicators | Unknown until you find the cause. No signals doesn't prove credit loss |
Example Scenarios
Scenario A: Clear Fraud
- The verified account holder confirms unauthorized use of this specific transaction through a trusted channel
- Classification: FRAUD, with the confirmation and case link documented
Scenario B: Credit Loss
- Verified employment, verified income
- No velocity anomalies
- No device/address flags
- Customer payment pattern consistent with financial hardship
- Classification: CREDIT LOSS, on the hardship pattern you verified. The missing flags alone wouldn't prove it
Scenario C: Needs Investigation
- Email first seen recently (Tier 2)
- Never-pay pattern (Tier 2)
- Employment unverifiable (Tier 2)
- Action: Gather more evidence, time-box decision
Scenario C is the one that eats your team. Time-box it before you open it, because an investigation with no deadline becomes a case nobody closes.
Documentation Requirements
Every fraud classification needs a paper trail. Here's what goes in it:
- Indicators present: List all relevant signals
- Evidence sources: Where each signal came from
- Decision rationale: Why classification was made
- Reviewer: Who made the decision
- Date: When decision was made
Write it the day you decide. A rationale reconstructed six months later is a guess with a date on it.
Next Steps
Setting up evidence framework?
- Define Tier 1 indicators: High-confidence signals
- Define Tier 2 indicators: Supporting signals
- Create decision matrix: Classification rules
Investigating a case?
- Check direct evidence: Verify what it proves about this case
- Assess supporting signals: Check context, not a fixed count
- Manual review: Human investigation for complex cases
Documenting decisions?
- Review documentation requirements: What to record
- Use example scenarios: Apply to your case
- Classify per decision matrix: Make the call
Related Topics
- Prevent Fraud: The fraud hub
- Manual Review: Human investigation for complex cases
- Fraud Types: All fraud type definitions
- Fake Identity Fraud: Fabricated identities
- First-Party Fraud: Customer abuse
- Risk Scoring: Combining signals into scores
- Velocity Rules: Detecting abuse patterns
- Data Enrichment: Email age, phone type, IP signals (Tier 2 indicators)
- Device Fingerprinting: Tracking devices
- Fraud Rings: Organized fraud attacks