Screening Lists

SOLO offers two screening list products in the Fraud & Financial Crime category. Both answer a narrow question (is this consumer listed?) and return a listing indicator plus the details of the most recent listing. Unlike certificates, screening list queries never issue a reusable artifact; they are point-in-time checks.

	Bank-Specific Bad Actor List	314(b) Cross-Bank Financial Crimes Watch List
What it is	A sponsor-bank-scoped list of specific individuals who, as prior customers of one or more of the bank’s fintech partners, violated one or more documented bank policies.	A list shared across participating banks, beyond a single sponsor-bank network, for suspected financial-crimes activity.
Designed for	A single sponsor bank’s network.	A network shared by several banks.
Use case	Bad actor screening: catching repeat offenders re-applying within the same bank’s networks.	Watch list screening: surfacing financial-crimes reports from other participating banks.
Subject	Consumer	Consumer
Query path	`POST /v1/products/bank_specific_bad_actor_list/query`	`POST /v1/products/cross_bank_financial_crimes_watch_list/query`

Both lists work the same way: a query sees only the listings furnished to the networks named in its network_ids. Which institutions can see a listing therefore follows from which networks it was furnished to: a listing furnished to Bank A’s network is not visible to a query that names only Bank B’s network. Both lists are query-only over the API. Listings are contributed by participating institutions through the furnishing pipeline.

Participation in the 314(b) Cross-Bank Financial Crimes Watch List is intended for financial institutions that have filed a 314(b) notice with FinCEN. Each participant is responsible for its own regulatory obligations, including how it shares, uses, and acts on the information.

Querying

Both endpoints take the standard query request:

Field	Type	Required	Purpose
`consent_id`	string	one of¹	Consent token identifying the consumer.
`consumer_identity_id`	UUID	one of¹	Direct consumer profile reference, as an alternative to `consent_id`.
`network_ids`	UUID[]	yes	The networks whose listings to check.
`furnishing_entity_ids`	UUID[]	no	Only consider listings from these institutions.

¹ Exactly one of consent_id or consumer_identity_id; both or neither returns 400 VALIDATION_ERROR. Lists are consumer-only. The subject is identified only by the consent or the profile id. You don’t send SSN, date of birth, or other identifying attributes on the query.

Bank-Specific Bad Actor List

curl -X POST https://api.sandbox.solo.one/v1/products/bank_specific_bad_actor_list/query \
  -H "Authorization: Bearer $SOLO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "consent_id": "a3f0b9c7-…",
    "network_ids": ["9f1c0c2e-…"]
  }'

A clean result:

{
  "provenance_event_id": "7b2d9c4e-…",
  "consumer_identity_id": "c2a4e8d0-…",
  "is_listed": false,
  "furnishing_entity_id": null,
  "furnishing_entity_name": null,
  "bad_actor_reason_code": null,
  "bad_actor_reason_definition": null,
  "bad_actor_list_placement_date": null
}

When the consumer is listed, the detail fields describe the most recent listing:

{
  "provenance_event_id": "7b2d9c4e-…",
  "consumer_identity_id": "c2a4e8d0-…",
  "is_listed": true,
  "furnishing_entity_id": "e1d2c3b4-…",
  "furnishing_entity_name": "First Example Bank",
  "bad_actor_reason_code": "account_abuse",
  "bad_actor_reason_definition": "Opened multiple accounts to exploit promotional offers",
  "bad_actor_list_placement_date": "2025-11-04"
}

Response field	Type	Meaning
`provenance_event_id`	UUID	The billable query event id, also in the `X-Ref-Id` header.
`consumer_identity_id`	UUID	The resolved consumer.
`is_listed`	boolean	Whether any bad actor listing for the consumer is visible in the queried networks.
`furnishing_entity_id`	UUID, nullable	The institution that placed the most recent listing. `null` when not listed.
`furnishing_entity_name`	string, nullable	That institution’s name. `null` when not listed.
`bad_actor_reason_code`	string, nullable	Reason code of the most recent listing: `account_abuse`, `fraud`, or `policy_violation`. `null` when not listed.
`bad_actor_reason_definition`	string, nullable	The documented bank policy the consumer violated. `null` when not listed.
`bad_actor_list_placement_date`	date, nullable	When the most recent listing was placed. `null` when not listed.

The most recent listing is the one with the latest placement date; listings without a placement date rank last, and ties go to the most recently furnished.

314(b) Cross-Bank Financial Crimes Watch List

curl -X POST https://api.sandbox.solo.one/v1/products/cross_bank_financial_crimes_watch_list/query \
  -H "Authorization: Bearer $SOLO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "consent_id": "a3f0b9c7-…",
    "network_ids": ["9f1c0c2e-…"]
  }'

A clean result:

{
  "provenance_event_id": "7b2d9c4e-…",
  "consumer_identity_id": "c2a4e8d0-…",
  "is_listed": false,
  "furnishing_entity_id": null,
  "furnishing_entity_name": null,
  "event_date": null,
  "event_category": null,
  "signal_level": null
}

When the consumer is listed, the detail fields describe the most recent report:

{
  "provenance_event_id": "7b2d9c4e-…",
  "consumer_identity_id": "c2a4e8d0-…",
  "is_listed": true,
  "furnishing_entity_id": "e1d2c3b4-…",
  "furnishing_entity_name": "First Example Bank",
  "event_date": "2026-02-19",
  "event_category": "money_laundering",
  "signal_level": "high"
}

Response field	Type	Meaning
`provenance_event_id`	UUID	The billable query event id, also in the `X-Ref-Id` header.
`consumer_identity_id`	UUID	The resolved consumer.
`is_listed`	boolean	Whether any watch list report for the consumer is visible in the queried networks.
`furnishing_entity_id`	UUID, nullable	The bank that reported the most recent event. `null` when not listed.
`furnishing_entity_name`	string, nullable	That bank’s name. `null` when not listed.
`event_date`	date, nullable	Date of the most recent reported event. `null` when not listed.
`event_category`	string, nullable	Category of the most recent event: `money_laundering`, `terrorist_financing`, or `fraud`. `null` when not listed.
`signal_level`	string, nullable	Strength of the most recent signal: `high`, `medium`, or `low`. `null` when not listed.

The most recent report is the one with the latest event date; reports without an event date rank last, and ties go to the most recently furnished.

Screening list queries always return 200 OK. A clean result is expressed as "is_listed": false, not as a 204. Both queries are billable events and carry the X-Ref-Id header.

Field reference

The listing fields behind each product. Field is the display name and API name is the field_name used across the platform; each appears in the query response under the same name.

Bank-Specific Bad Actor List: BadActorEvent

Field	API name	Type
Bad Actor Reason Code	`bad_actor_reason_code`	String
Bad Actor Reason Definition	`bad_actor_reason_definition`	String
Bad Actor List Placement Date	`bad_actor_list_placement_date`	Date

314(b) Cross-Bank Financial Crimes Watch List fields

Field	API name	Type
Event Date	`event_date`	Date
Event Category	`event_category`	String
Signal Level	`signal_level`	String

Using a listing

A listing reflects what a participating institution furnished. It is a screening input, not a determination. Route hits to your compliance review process; decisions based on a listing, including any adverse action, are your institution’s.

Querying

Request anatomy, billing, and the X-Ref-Id header.

Products

The full product catalog.

Furnishing API

Query API

GraphQL API

Querying

Bank-Specific Bad Actor List

314(b) Cross-Bank Financial Crimes Watch List

Field reference

Bank-Specific Bad Actor List: BadActorEvent

314(b) Cross-Bank Financial Crimes Watch List fields

Using a listing

Querying

Products

​Querying

​Bank-Specific Bad Actor List

​314(b) Cross-Bank Financial Crimes Watch List

​Field reference

​Bank-Specific Bad Actor List: BadActorEvent

​314(b) Cross-Bank Financial Crimes Watch List fields

​Using a listing

​Related

Querying

Products

Querying

Bank-Specific Bad Actor List

314(b) Cross-Bank Financial Crimes Watch List

Field reference

Bank-Specific Bad Actor List: BadActorEvent

314(b) Cross-Bank Financial Crimes Watch List fields

Using a listing

Related