Skip to main content
A label is a fraud type you want Fraud Score to detect. Each label trains its own model for each platform. A workspace can have up to 100 labels.

​
Create a label

You can create a label by uploading a CSV file with a new column, or while labeling events in the Dashboard. To create a label while labeling events:
  1. Click Add label on an event, or Label as in the events table.
  2. Type the label name and click Create new label.
  3. Enter the label details:
    • Name: a display name of up to 128 characters. You can rename the label later.
    • Slug: the label identifier used in the API and CSV files, generated from the name. Use lowercase letters and numbers, separated by single hyphens or underscores. You can’t change the slug after you create the label.
    • Category: the fraud type the label belongs to. You can’t change the category after you create the label.
  4. Click Create label.
Don’t include personal information, such as names or email addresses, in label names or slugs. Name labels after the fraud type, for example chargeback_fraud.

​
Categories

Every label belongs to one of these predefined categories:
  • Payment fraud
  • Account takeover
  • Multi-accounting
  • Fake account
  • Promotion abuse
  • Platform abuse
  • Content abuse
  • Other fraud
A label without a category can’t train a model. If a label is uncategorized, for example because it was created from a CSV column you didn’t map, open the label and click Assign category.

​
Confirmed non-fraud

Confirmed non-fraud is a built-in label for events you have verified as legitimate. All your models use it as their non-fraud examples. An event labeled Confirmed non-fraud can’t have any other label. Adding a fraud label to the event removes Confirmed non-fraud, and labeling an event as Confirmed non-fraud removes its other labels after you confirm. Only label events you have actually confirmed as legitimate. An event that wasn’t flagged as fraud isn’t necessarily non-fraud, so leave unconfirmed events unlabeled.

​
Rename or archive a label

Open a label from Fraud Score > Models and click More model actions:
  • Rename label changes the display name. The slug stays the same.
  • Archive label permanently retires the label. You can’t undo this. An archived label stops accepting new labeled events and trains no new model versions, and its slug can’t be reused. Existing labeled events and past model versions stay available until they expire.
You can’t archive a label that has an active model returning scores in your API. To archive it, contact the Fingerprint support team to disable the model first.

​
Label events

Uploading a CSV file is the recommended way to label events, including large imports such as your historical fraud data. You can also label events from the identification events table, from event details, or with the Server API. All methods update the same labels, and the most recent submission for an event wins. You can label events up to 180 days old. Very recent events can’t be labeled for a few minutes after they’re recorded.

​
Upload a CSV file

  1. Go to Fraud Score > Models and click Upload data.
  2. Click Download CSV template to get a file with the expected columns.
  3. Fill in the file and upload it.
  4. If the file contains columns that don’t match an existing label, choose a category for each new column, then click Confirm import.
The CSV file must meet these requirements:
  • UTF-8 encoded and comma-separated, up to 10 MB
  • One event_id column with the event IDs
  • Between 1 and 100 label columns. Each column header is a label slug, such as payment_fraud, or non_fraud for Confirmed non-fraud.
  • One row per event, with 1 for each label that applies and 0 otherwise
After the upload, you can close the dialog. Processing continues in the background, and you can follow it in Fraud Score > Dataset > Uploads.

​
Label multiple events

  1. Go to Identification and select the events you want to label. Your selection is kept across pages, and is cleared when you change filters.
  2. Click Label as and select a label.
  3. Click Apply.
If some events couldn’t be labeled, click Details to see each event ID and the reason, for example an event that is too old.

​
Label a single event

  1. Go to Identification and open an event.
  2. In the event details, click Add label.
  3. Search for a label and select it, or select Confirmed non-fraud.
To remove a label from the event, click the remove icon on the label.

​
Submit labels with the Server API

To submit labels from your backend as you confirm fraud outcomes, use the POST /labels endpoint of the Server API. Labels submitted through the API appear in the Dashboard with the Server API source. POST /labels accepts events up to 30 days old. To label older events, up to 180 days old, use the Dashboard or a CSV upload.