The distinction from the other lists is its focus on attributes: each
listing ties a confirmed fraud event to discrete identifying data (the
fraud_attribute_label and its content), so consumers of the list learn not
just that fraud occurred but which identity attributes were involved. The
events behind it are contributed by network participants through governed
furnishing flows.
At a glance
"is_listed": false (always 200 OK, never 204). When the
consumer is tied to a confirmed fraud event, the attributes from the product’s
FraudVerificationEvent schema are populated:
Matching & fields
Subjects are matched on the consumer identity behind your consent record. SSN and date of birth are mandatory match inputs; name, phone, and email refine the match. The fraud attributes are defined by the product’sFraudVerificationEvent
schema. Field is the display name and API name is the field_name used in
policies.
Loss-event categories include
financial-theft, account-takeover, and
synthetic-identity; malicious-intent methods include phishing and
card-not-present. A network’s
querying policy can restrict which
categories and methods a query considers.
Related
Products
The full product catalog.
Bank-Specific Bad Actor List
Sponsor-bank-scoped repeat-offender screening.