Fraud & identity data dictionary

An operation creates thousands of accounts using automated signup scripts and slightly varied name/email combinations, then sells verified, aged accounts in bulk to be used for bonus abuse or bot fraud elsewhere.

Farmed accounts often pass individual verification checks — each one may look plausible in isolation — which is why detecting account farming typically requires identifying the coordinated pattern across many accounts rather than any single account.

Network/link analysis identifying clusters of accounts sharing subtle infrastructure (device, creation timing patterns, IP ranges) is the primary detection method, since individual-account signals alone are often insufficient.

A fraudster obtains a customer's email and password from a data breach on an unrelated site, then uses those same credentials to log into the customer's account elsewhere, since many people reuse passwords across services.

ATO is especially damaging because it exploits an account with an established, trusted history — bypassing checks designed for new-account fraud, and often going unnoticed until the legitimate owner reports unauthorized activity.

Behavioral and device signals — a login from an unfamiliar device or location, a sudden change in typical usage patterns — can flag a session as likely compromised even when the correct credentials were used.

A bank monitors transaction patterns for signs of layering — moving funds through multiple accounts in ways designed to obscure their origin — as part of its AML program.

AML compliance is a legal requirement for financial institutions and many other regulated businesses; failures can result in severe regulatory penalties, and AML obligations exist independently of whether a specific transaction is also fraudulent.

AML programs combine KYC/KYB onboarding checks, ongoing transaction monitoring for suspicious patterns, sanctions and PEP screening, and mandatory reporting of suspicious activity to regulators.

If a business processes 10,000 account applications and approves 9,200, its approval rate is 92%.

Approval rate is in direct tension with fraud loss rate — a system tuned to approve almost everything will have a high approval rate but likely also higher fraud losses, while an overly conservative system will have low fraud losses but reject legitimate customers (false declines), suppressing growth.

The goal generally isn't maximizing approval rate in isolation, but maximizing approvals of genuinely legitimate customers specifically — which requires distinguishing false declines from correctly declined fraud within the rejected population.

A returning customer's typical typing cadence and navigation pattern differs noticeably from the session pattern observed after their credentials were used following a data breach, flagging the session as potentially compromised.

Behavioral biometrics can detect account takeover even when the correct password and device were used, since they evaluate how the account is being used rather than only what credentials were presented.

These signals are typically evaluated continuously during a session, rather than only at login, allowing detection of a takeover that occurs mid-session.

A person creates several accounts using slightly varied name spellings, different email aliases of the same inbox, and rotating devices to claim a "new customer" sign-up bonus multiple times.

Promotional programs are priced assuming a bounded number of genuine new customers claim them; abuse at scale directly inflates marketing costs without acquiring genuine new customers, and can make an otherwise profitable promotion loss-making.

Cross-account signal matching — shared devices, email aliasing patterns, overlapping addresses or payment methods — identifies clusters of accounts that are likely the same person or an organized abuse ring, even when individual account details differ.

Within seconds of tickets going on sale, automated bots purchase a large share of available inventory across many simulated accounts, leaving few or none available to genuine buyers at the original price.

Beyond direct revenue impact, bot-driven scalping damages customer trust and experience — genuine fans or customers are systematically outcompeted by automation, not other genuine buyers.

Behavioral and velocity signals — inhuman click/purchase speed, patterns across many accounts sharing underlying device or network characteristics — distinguish bot traffic from genuine high-demand human traffic.

A synthetic identity opens a credit card, makes small purchases and on-time payments for a year to build a positive history and earn credit limit increases, then rapidly charges the account to its limit and stops paying entirely.

Bust-out fraud is specifically designed to defeat standard credit risk monitoring, since the account looks genuinely low-risk right up until the moment it doesn't — the entire scheme depends on a patient, deliberate build-up phase.

Sudden, sharp deviations from an account's established usage pattern — a jump in spend velocity or credit utilization inconsistent with prior behavior — are a key signal, even against an account with an otherwise clean history.

A fraudster runs a script that attempts many small transactions using a list of stolen card numbers against a merchant's checkout page, identifying which cards are still active and unflagged.

Card testing itself may not directly cost the merchant much (small transaction amounts), but it degrades checkout performance, increases processing costs, and the merchant's site becomes a tool for validating cards subsequently used for fraud elsewhere.

High-velocity, low-value transaction attempts using different card numbers but shared device or session characteristics are a strong card-testing signal.

An analyst investigating a flagged account uses a case management tool to view the account's full signal history, related accounts sharing device or network connections, and prior similar cases, rather than piecing that information together manually from separate systems.

Investigation quality and speed depend heavily on how much relevant context an analyst has readily available — scattered or incomplete information leads to slower investigations and less consistent decisions across analysts.

Effective case management tools surface not just the flagged item itself but its connections within the broader identity graph, prior related cases, and clear reason codes explaining why it was flagged in the first place.

A customer buys a product, receives it, then files a chargeback claiming non-delivery — keeping both the product and the refunded money.

Chargebacks carry direct financial cost (the refunded amount plus processing fees) and, at scale, can push a merchant's chargeback ratio above thresholds set by card networks, risking additional penalties or loss of payment processing privileges.

Because the transaction itself often looks legitimate at time of purchase, detection relies more on behavioral patterns — repeat disputers, mismatched claim details, delivery confirmation data — than on point-of-sale risk signals alone.

A merchant processing 100,000 transactions in a month who receives 150 chargebacks has a chargeback ratio of 0.15%.

Card networks (Visa, Mastercard) set chargeback ratio thresholds, and merchants exceeding them can be enrolled in monitoring programs with additional fees, or in severe cases lose payment processing privileges entirely.

Reducing chargeback ratio requires addressing both fraud-driven chargebacks (via better transaction risk decisioning) and friendly-fraud-driven chargebacks (via clearer billing practices and dispute response processes).

A list of email-password combinations leaked from a breached retailer is automatically tested against a bank's login page; the small percentage of reused passwords succeed and grant access to those accounts.

Credential stuffing doesn't require breaking any specific service's security — it exploits password reuse, meaning even a service with strong security of its own can be affected if its users reused a password compromised elsewhere.

High-volume, automated login attempt patterns — many attempts in rapid succession, often from a distributed set of IP addresses — are a strong signal for credential stuffing, distinct from normal human login behavior.

An unauthorized party gains access to a company's customer database and extracts email addresses and hashed passwords, which are later sold on illicit marketplaces and used in credential stuffing attacks against other services.

Data breaches at one company create downstream fraud risk for other, unrelated companies, since exposed credentials and personal data are frequently reused across services — a breach's impact isn't contained to the breached organization.

Businesses can monitor for their users' credentials appearing in known breach datasets and proactively prompt password resets, rather than waiting for fraudulent activity to occur.

A fraudster uses an AI-generated video of a person's face, synced to a live camera feed in real time, to attempt to pass a facial liveness check during account verification.

As generative AI tools have become more accessible, the technical barrier to producing convincing deepfakes has dropped significantly, making this a growing category of verification risk rather than a rare edge case.

Detection techniques look for artifacts inconsistent with genuine video capture — unnatural blinking patterns, lighting inconsistencies, or signs of real-time video injection rather than a genuine camera feed — alongside standard liveness checks.

Two account creation attempts using different emails and IP addresses, but the same underlying device fingerprint, can be linked as likely originating from the same source.

IP addresses alone are unreliable for tracking, since they're frequently shared (public wifi, corporate networks) or masked (VPNs); device fingerprinting provides a more persistent signal for connecting activity across sessions.

Device fingerprints feed into an identity graph as one signal type among several, helping establish whether multiple accounts or sessions are connected.

A new account arrives from a device first seen today that is already linked to 7 different emails. A returning customer's laptop shows a 2-year history with a single identity.

Fraud rings reuse hardware even while rotating emails, cards, and IP addresses. Recognizing a known good device also lets returning customers move through login and checkout with fewer interruptions, which protects conversion.

An on-device SDK gathers attributes, and a server resolves them into a persistent identifier with signals such as age, velocity, and tampering indicators for the risk decision.

A person's digital footprint might include an email address first seen years ago, a consistent device history, and a stable pattern of account activity across multiple merchants over time.

A longer, more consistent digital footprint is generally correlated with lower fraud risk, since fabricated identities are harder to backfill with a plausible multi-year history than to fabricate for a single point-in-time check.

Risk models incorporate footprint depth and consistency as one input among several — not as a standalone pass/fail signal, since legitimate thin-file identities also have limited footprints.

A fraudster alters the date of birth on a scanned driver's license image to misrepresent their age during an age-gated verification process.

As document capture and verification have moved online, forgery techniques have adapted accordingly — including digitally edited images and, increasingly, AI-generated fraudulent documents that can be difficult to distinguish from genuine ones on casual inspection.

Detection combines analysis of document security features, consistency checks against known document templates by issuing authority, and cross-referencing extracted document data against other identity signals.

An email address that's been in consistent use for several years across multiple legitimate services generally carries a stronger reputation signal than one created minutes before a transaction.

Email age and usage history are among the more difficult signals for a fraudster to fabricate convincingly at scale, since building genuine-looking history takes real time.

Email reputation is typically one input among several in a broader risk model, not a standalone decision factor, since legitimate customers also sometimes use newly created emails.

A fraud ring runs hundreds of simulated Android device instances on a single server to create and operate fraudulent accounts at a scale impossible with physical devices.

Emulators allow fraud to be automated and scaled far beyond what physical device fraud would permit, and can be used to spoof device characteristics that would otherwise serve as a trust signal.

Emulators often have subtle but detectable technical inconsistencies compared to genuine hardware — sensor data that's absent or unnaturally uniform, performance characteristics inconsistent with claimed hardware — that detection tools check for.

A returning customer travels abroad and makes a purchase from an unfamiliar location on a new device. A rules-based system flags the mismatch and declines the transaction, even though the purchase was legitimate.

False declines carry a direct, measurable revenue cost, and repeated declines often push a customer to a competitor rather than trying again. Because false declines don't show up as "fraud losses" on a balance sheet, they're frequently under-tracked relative to their actual business impact.

Systems that weigh multiple corroborating signals — rather than declining on a single mismatched attribute — reduce false declines by distinguishing genuine behavioral anomalies (a customer traveling) from actual fraud patterns.

A synthetic identity with a convincingly fabricated but internally consistent set of attributes passes a verification check and is approved, only to be used for fraud months later.

False negatives are the direct source of realized fraud losses; unlike false positives, which are visible immediately as customer friction, false negatives are often only discovered after the fact, when a loss has already occurred.

Continuous model retraining against confirmed fraud outcomes helps a system adapt to fraud patterns it previously missed, though a false-negative rate of zero isn't a realistic target — the goal is minimizing it relative to false-positive tradeoffs.

A long-standing customer's transaction is flagged as suspicious because they made a purchase from a new country while traveling, despite the transaction being entirely legitimate.

A high false-positive rate creates unnecessary friction and manual review workload, and — when a false positive results in a declined transaction — becomes a false decline with direct revenue impact.

Evaluating multiple corroborating signals rather than triggering on a single anomalous attribute reduces false positives by distinguishing plausible explanations (travel, a new device) from genuine fraud indicators.

A customer applies for a loan under their real identity with no intention of repaying it, or disputes a legitimate purchase as unauthorized to get a refund while keeping the goods.

First-party fraud is harder to detect with identity-verification tools alone, since the identity involved is genuine — detection instead relies on behavioral and intent signals rather than identity mismatch signals.

Patterns like repeat disputing behavior, applications with unusually optimistic risk profiles, or early default patterns inconsistent with genuine financial hardship can indicate first-party fraud.

A business processing $50M in transactions that experiences $250,000 in confirmed fraud losses has a fraud loss rate of 0.5%.

Fraud loss rate is one of the primary metrics used to evaluate a risk program's effectiveness, but it should be read alongside approval rate and false decline rate — a very low fraud loss rate achieved by declining large numbers of legitimate customers isn't actually a well-performing program.

Accurate fraud loss rate tracking requires reliable downstream outcome data (confirmed chargebacks, confirmed fraud reports) fed back into the risk system, not just point-in-time transaction data.

A cardholder doesn't recognize an unfamiliar billing descriptor on their statement and disputes the charge as fraudulent, even though they made the purchase.

Friendly fraud is often conflated with chargeback fraud generally, but the intent (or lack of it) matters for how a business responds — a confusing billing descriptor is a fixable process issue, while repeat intentional disputers are a fraud pattern.

Clear billing descriptors and proactive receipt/confirmation communication reduce the misunderstanding-driven share of friendly fraud; behavioral tracking of repeat disputers addresses the intentional share.

Traffic originating from a known datacenter IP range associated with automated bot infrastructure carries a different reputation signal than traffic from a typical residential ISP address.

IP address alone is an increasingly unreliable standalone signal — legitimate users regularly use VPNs for privacy, and IP addresses are frequently shared or reassigned — but IP reputation combined with other signals still provides useful context.

IP reputation is best used as one contributing signal alongside device and behavioral data, rather than as a blocking rule, given how common legitimate VPN and shared-network use has become.

A single person might be linked in an identity graph through a consistent pattern: the same device used across several accounts, an email created years ago and used consistently since, and a phone number tied to a stable address history.

Individual data points (an email, a device ID) can each look valid whether the identity behind them is real or synthetic. The relationships between those points — how long they've existed together, how consistently they co-occur — are much harder to fabricate convincingly.

Risk models query the graph to assess whether an identity's attributes have a plausible, consistent history, rather than only checking whether each attribute passes independently.

Verification answers "does this driver's license belong to this person?" Resolution answers "are these three accounts, opened with different emails and phone numbers over two years, actually the same person?"

A system built only for verification can pass a synthetic identity that has a convincing (even genuine) document, because verification alone doesn't check whether that identity's broader signal history is coherent. Resolution catches inconsistencies verification alone would miss.

Most robust risk programs use both: verification at the point of a specific claim (onboarding, a high-value transaction) and resolution continuously, to catch identities that pass verification individually but don't connect coherently over time.

A fraudster uses a victim's stolen Social Security number and other personal details to open a new credit account in the victim's name.

Beyond the direct financial fraud, identity theft can have lasting consequences for the victim — damaged credit history, difficulty accessing legitimate financial services — that persist well after the fraudulent activity itself is stopped.

Identity theft differs from synthetic identity fraud in that it uses a genuine person's complete identity, rather than combining real and fabricated elements into a new, non-existent identity.

A payment processor onboarding a new merchant verifies the business's registration, checks its beneficial owners against sanctions and PEP lists, and confirms its stated business activity matches observable signals.

Businesses can be used as fronts for fraud or money laundering, and beneficial ownership can be deliberately obscured through layered corporate structures, making KYB more complex than verifying an individual.

KYB typically combines business registry checks, beneficial ownership verification, and screening of associated individuals against watchlists.

A bank opening a new account collects and verifies a customer's government-issued ID, address, and date of birth as part of its KYC process before the account is activated.

KYC is often a legal requirement, not just a risk-management best practice, particularly in banking, fintech, and other regulated sectors — non-compliance can carry regulatory penalties independent of any actual fraud outcome.

KYC combines document verification, database checks against known identity records, and sometimes biometric liveness checks to confirm the person onboarding matches the identity they claim.

A large risk model might evaluate hundreds of signals simultaneously — device history, email age, address stability, behavioral patterns — to produce a single score used in an automated approve/decline/review decision.

Models trained on broader, longer-history signal sets generally generalize better to fraud patterns they haven't seen before than narrow, rules-based systems, which only catch fraud patterns someone has explicitly coded for.

These models require continuous retraining against fresh outcome data (confirmed fraud, confirmed legitimate) to avoid drifting out of date as fraud patterns evolve.

A verification flow might ask a user to blink, turn their head, or read a randomly generated number aloud, actions difficult to replicate convincingly with a static photo or pre-recorded video.

Without liveness detection, document and facial verification checks can potentially be defeated by presenting a photo or deepfake of the legitimate document holder rather than the actual person.

Liveness checks combine active challenges (prompted actions) and passive analysis (detecting subtle signs of screen replay, mask artifacts, or unnatural motion) to distinguish a live person from a spoofing attempt.

A transaction scores in a "gray zone" between the auto-approve and auto-decline thresholds, so it's routed to a fraud analyst who reviews the available signals and makes a final decision.

Manual review is typically the most expensive part of a fraud program per transaction, since it requires human time; minimizing the volume routed to manual review (without increasing false negatives) is a common efficiency goal.

Providing reviewers with clear, explainable reason codes alongside a risk score — rather than a bare score — reduces review time per case and improves consistency across different reviewers.

A recruiting platform needs a way to reach candidates, so it sets match_requirements=phone OR email. Profiles with only a name and an employer come back as a free no match.

Paying for profiles that lack the one field a workflow needs is pure waste at volume. Defining a usable match up front ties spend to records the business can act on.

The parameter accepts field names joined with AND, OR, and parentheses, plus subtypes such as phone.mobile or email.personal. A new_ prefix, such as new_phone, charges only when the result adds a phone beyond the one supplied.

A query with a common name and a city returns 3 possible persons scored 0.9, 0.7, and 0.4. The analyst expands the 0.9 candidate first.

Acting on the wrong person wastes analyst time, sends outreach to the wrong contact, or attaches someone else's history to a case. A confidence threshold lets each workflow decide how much ambiguity it can absorb before a human steps in

The minimum_match parameter filters out candidates below a chosen score. The top_match parameter returns either a single definite match or no match at all.

An analyst asks an AI assistant to look into a suspicious signup email. The assistant calls Pipl through MCP, receives the identity data, and summarizes what it found in the conversation.

Integration backlogs delay new data sources by weeks or quarters. MCP lets teams try and use identity data inside the AI tools analysts already work in, with far less engineering time up front.

An organization adds the MCP server to its AI client and authenticates with an API key. The agent then calls the server's tools whenever a request needs them.

A person is recruited (sometimes unknowingly, believing it's a legitimate job) to receive funds into their personal bank account and quickly forward them elsewhere, taking a small commission — the funds are proceeds of fraud committed against someone else.

Mule accounts are a critical link in laundering fraud proceeds; detecting and disrupting mule networks can prevent losses from a wide range of upstream fraud types, not just the mule activity itself.

Accounts that receive funds from many unrelated sources and quickly transfer them onward — a pattern inconsistent with typical personal account activity — are a common mule signal.

Logging into an account with a correct password, then confirming a code sent to a registered phone number, is a common two-factor implementation of MFA.

MFA significantly raises the difficulty of account takeover, since a fraudster who has obtained stolen credentials (something the user knows) typically still lacks the second factor (something the user has).

Common second factors include SMS codes, authenticator apps, hardware security keys, and biometric checks — each with different tradeoffs in security and user friction.

A group of accounts that individually appear unrelated may share a device, a payment method, and overlapping IP ranges — a pattern that link analysis surfaces but single-account review would miss.

Organized fraud rings deliberately structure individual accounts to look unrelated; network analysis is often the only way to detect coordinated abuse that's invisible when each account is evaluated in isolation.

Graph-based techniques identify clusters of connected entities and flag unusually dense or suspicious connection patterns for review.

Requiring a government ID upload and a selfie liveness check adds friction compared to a signup flow that only requires an email and password, but may be necessary depending on the risk profile of the product.

Friction has a measurable cost — abandoned signups — that must be weighed against the risk-reduction benefit of additional checks; the right balance depends heavily on the specific product and its risk profile.

Risk-based approaches apply friction selectively — light checks for most users, escalating to stronger verification only for identities or behaviors that present elevated risk signals — rather than applying uniform friction to every signup.

A threat analyst receives a username tied to a phishing kit. A forum post, a matching social profile, and an archived web page connect that username to an email used in two earlier campaigns.

Manual OSINT means searching dozens of sites for one subject. Every hour spent stitching sources together delays case closure and raises the cost of each investigation.

Analysts start from one identifier, expand to connected identifiers, and verify each link against its original record. Provenance decides whether a finding holds up in a report, a compliance file, or a courtroom.

A name alone might not uniquely identify someone, but a name combined with a date of birth and address typically does — that combination is treated as PII even if no single element is.

PII handling is subject to data protection regulations in most jurisdictions (GDPR, CCPA, and others), and businesses that collect or process it for identity verification and fraud prevention purposes take on corresponding compliance obligations.

Common practices include minimizing the PII collected to what's genuinely necessary, encrypting it at rest and in transit, and limiting internal access on a need-to-know basis.

A fraudster sends an email that closely mimics a bank's official communication, directing the recipient to a fake login page that captures their username and password when entered.

Phishing is frequently the entry point for other fraud types — stolen credentials from a phishing attack can then be used for account takeover, and stolen personal information can feed synthetic identity construction.

User education helps, but technical mitigations — flagging logins immediately following a likely-phished credential entry, or requiring a second factor that phishing alone can't capture — are more reliable at scale.

A mobile number with a multi-year association to a consistent identity generally carries a different reputation signal than a newly issued VoIP number with no prior history.

VoIP and disposable virtual numbers are cheaper and faster to obtain than traditional mobile lines, making phone type and history a useful signal for distinguishing genuine users from those seeking to avoid traceability.

Phone reputation combines carrier-type data with historical association data, weighed alongside other identity signals rather than used as a standalone block.

A former government minister opening an account at a financial institution would typically be flagged as a PEP, triggering enhanced due diligence beyond standard onboarding checks.

PEP status doesn't imply wrongdoing, but regulations in most jurisdictions require additional scrutiny for PEPs given their elevated exposure to corruption risk by virtue of their position.

PEP screening relies on maintained databases of public officials and their known associates, cross-referenced against a customer's identifying information during onboarding.

A transaction claiming to originate from one country but routed through a commercial VPN service registered in a different country would be flagged by proxy/VPN detection.

While VPN use is common and legitimate for privacy reasons, it's also a technique used to evade geographic restrictions, mask true location during fraud, or obscure connections between related fraudulent accounts.

Detection relies on maintained databases of known proxy, VPN, and datacenter IP ranges, combined with technical signals (latency patterns, routing characteristics) that can indicate masked traffic even from services not in a known database.

Two models are tested on the same 12 months of labeled transactions. The model with an AUC of 0.92 ranks a randomly chosen fraud case above a randomly chosen good one 92% of the time.

AUC lets buyers compare models before choosing a cutoff, which makes it a common proof-of-concept metric. It says nothing about cost, though.

Pair AUC with results at the chosen threshold, such as precision, recall, and false positive rate, and with the dollar value of each type of error.

A customer claims a package never arrived despite delivery confirmation, or returns an empty box while claiming a refund for the full contents.

Refund fraud directly erodes margin, and generous, low-friction refund policies — while good for genuine customer experience — can be disproportionately exploited by repeat abusers if not monitored.

Behavioral patterns — a customer with an unusually high refund rate relative to typical customers, or claims that don't align with delivery and tracking data — help distinguish abuse from genuine refund requests.

A person purchases an item, uses it, then returns it claiming it was defective or unwanted, exploiting a liberal return window.

Retailers with generous, customer-friendly return policies are more attractive targets for this fraud type, creating a direct tension between customer experience goals and fraud exposure.

Tracking return frequency and patterns per customer, and flagging accounts with disproportionately high return rates relative to purchase volume, helps identify abuse without penalizing occasional genuine returns.

A business might explicitly decide it's willing to accept a certain fraud loss rate if it corresponds to a meaningfully higher approval rate and lower onboarding friction for legitimate customers.

Risk thresholds and model tuning decisions should be grounded in an explicit risk appetite rather than defaulting to maximum conservatism, since overly conservative settings suppress legitimate growth without necessarily being a deliberate business choice.

Risk appetite is typically set by weighing historical fraud loss data, false decline cost, and broader business growth priorities — and should be revisited periodically as those factors change.

A transaction with a mismatched billing address, a new device, and an unusually large purchase amount for that customer might receive an elevated risk score, prompting additional review.

Risk scores let a business set a single consistent policy (thresholds for approve/review/decline) across large transaction volumes rather than making ad hoc individual judgment calls.

Thresholds should be set and periodically re-validated against actual outcome data — confirmed fraud and confirmed legitimate cases — since a model's score distribution can drift as fraud patterns and customer behavior change over time.

"Email created 3 days ago" is a risk signal; it isn't itself a decision, but it's one input a risk model weighs alongside other signals to reach a score.

No single signal is reliably decisive on its own — a new email alone doesn't mean fraud, since many genuine customers also have new emails — which is why robust risk decisioning combines many signals rather than relying on any one.

Signals are typically weighted and combined within a model rather than evaluated with simple pass/fail rules, allowing the system to account for context (a new email plus a new device plus an unusual purchase pattern is more meaningful than any signal alone).

A fraudster impersonates a victim to their mobile carrier, claiming a lost phone, and requests the victim's number be transferred to a new SIM card, after which they can receive SMS one-time passcodes intended for the real account owner.

SIM swap fraud specifically undermines SMS-based multi-factor authentication — a factor many services rely on as their primary "something you have" check — making accounts protected only by SMS MFA vulnerable despite MFA being enabled.

Using authentication factors that don't rely on SMS (authenticator apps, hardware keys) reduces exposure; behavioral and device signals can also flag account access following a suspicious phone number change.

A financial institution checks a new customer's name and identifying details against the OFAC Specially Designated Nationals list and similar international sanctions lists before approving the account.

Transacting with a sanctioned entity can expose a business to significant legal and regulatory penalties, independent of whether any fraud occurred — this is a compliance requirement, not just a risk-reduction measure.

Screening typically involves fuzzy name-matching against sanctions databases (to catch spelling variations and transliterations) combined with additional identifying details to reduce false matches.

A retailer adds a small script to its checkout page. The script collects browser and hardware attributes and returns a device token that the retailer includes in its risk call.

Server-side data cannot tell whether the same phone or laptop keeps returning under new emails. A lightweight SDK adds that view without a long integration project, so engineering time stays on the core product.

Developers install the package, initialize it early with an API key, and pass its output with each risk request. Setup also covers user consent, privacy disclosures, and the allow-listed domains or app IDs.

A customer logging in from their usual device isn't prompted for anything extra, but the same customer attempting a large transfer to a new recipient is prompted for an additional verification step.

Applying strong authentication uniformly to every action creates unnecessary friction for low-risk activity; step-up authentication concentrates that friction where the risk actually justifies it.

Step-up prompts are typically triggered by a risk score crossing a threshold, an anomalous behavioral signal, or a specific high-value action type.

A fraudster pairs a real, stolen or purchased Social Security number with a fabricated name and address to open a new account. Because no existing credit file is being altered, standard identity-theft alerts don't trigger — the "person" simply doesn't exist yet, so the fraud can go undetected for months while the synthetic identity builds a track record.

Synthetic identities are built to pass single-attribute checks — email, phone, and device can each look individually legitimate. Losses are harder to attribute to a specific victim than traditional identity theft, since there's no real person to report it, which makes this fraud type both underreported and slow to detect through conventional means.

Because synthetic identities are fabricated rather than stolen, they lack a genuine history of connected, consistent behavior over time. Detection approaches that evaluate signal history and connectivity, rather than checking attributes in isolation, are generally more effective than single-signal verification.

A college student applying for their first credit product has no existing credit history and a short digital footprint, which can cause automated systems to flag them as high-risk by default, even though they present no actual fraud risk.

Systems that rely heavily on historical depth to establish trust risk producing false declines for legitimate thin-file customers — a segment that, over time, represents real and growing revenue if approved responsibly.

Evaluating a broader mix of signal types (not just credit history) — device consistency, verified contact information, behavioral plausibility — allows thin-file identities to be assessed on the signals they do have, rather than penalized for the ones they lack.

A fraudster uses a stolen credit card number to make an unauthorized purchase; the actual cardholder had no knowledge of or involvement in the transaction.

Third-party fraud is generally more amenable to identity-verification and device/behavioral signal detection than first-party fraud, since the perpetrator's identity or behavior genuinely differs from the legitimate account holder's.

Mismatches between the transacting party's signals (device, location, behavior) and the legitimate account holder's established patterns are the primary detection mechanism.

A fraudster lists a popular product at a below-market price on a fake marketplace listing; when a genuine buyer orders and pays, the fraudster uses a stolen credit card to purchase and ship that exact product from a real retailer directly to the buyer, pocketing the buyer's payment.

This fraud type is unusually hard to detect from the defrauded retailer's side, since the shipping address is a genuine, non-fraudulent recipient — the fraud signal is entirely in the payment method, not the delivery pattern.

Detection relies on identifying the stolen card itself (via card-network fraud signals) rather than shipping or recipient anomalies, since the delivery side of the transaction looks entirely normal.

A transaction flagged for review due to a mismatched device and identity graph inconsistency is confirmed as fraudulent after investigation.

True positive rate, alongside false positive rate, is one of the core metrics used to evaluate whether a risk model is actually performing well, rather than just generating a high volume of flags.

True positives require a confirmed outcome (a chargeback, a fraud report, an investigation finding) to count — a flagged transaction alone isn't yet a confirmed true positive until the outcome is known.

A trust score might combine device history, identity graph consistency, and behavioral signals into a single 0–1000 value used to automatically approve, decline, or route a transaction to manual review.

A single score allows risk decisions to be automated at scale and consistently applied, but a score is only as good as the signals and model behind it — the number itself doesn't explain the reasoning without accompanying reason codes.

Businesses typically set score thresholds (e.g., approve above X, review between X and Y, decline below Y) calibrated against their own risk appetite and historical outcome data, rather than using a universal cutoff.

A lender evaluates a loan applicant's identity, credit history, and other risk signals to decide whether to approve the loan and on what terms.

Underwriting decisions directly shape a business's risk exposure and growth — overly strict underwriting limits growth by rejecting viable customers, while overly loose underwriting increases losses.

Modern underwriting increasingly combines automated risk scoring with human review for edge cases, rather than relying entirely on either manual judgment or a fully automated black-box decision.

A single device attempting to create 20 new accounts within an hour would trigger a velocity check, since that frequency is implausible for genuine, independent users.

Velocity checks are effective at catching automated, high-volume abuse (bot-driven account creation, card testing) that wouldn't necessarily look suspicious evaluated one transaction at a time.

Velocity thresholds need to be calibrated per use case — what's a suspicious frequency for account creation is different from a suspicious frequency for repeat purchases from a loyal customer.

A sales platform runs 500,000 leads through two lower-cost providers first. The 80,000 records still missing a phone or email then go to a search platform.

Sending every record to every provider pays several times for the same data. Ordering providers by cost and coverage cuts duplicate spend, and the last step concentrates on the hard records that often drive conversion.

Teams rank providers, define what "filled" means for each record, and pass only misses forward. At the final step, match requirements and top_match keep each call billable only when the needed field comes back.