Navigate to the Final Outcomes tab of the Dashboard Settings to view the Final Outcomes. This Settings page lets you view all your Final Outcomes, download our standardized templates, upload Final Outcomes via CSV or manually, and manage Final Outcomes data.
If you prefer to upload Final Outcomes data programmatically, our API also supports a Final Outcomes endpoint. Final Outcomes data can also be sent to Alloy via a secure link; reach out to Alloy Support at support@alloy.com to receive a secure sharing link.
Permissions
Before you get started, agents will require Final Outcomes permissions in order to upload and view their data. These permissions can be enabled for any role by going to Settings > Roles, expanding the Roles tab, then scrolling down and clicking the Final Access permissions boxes.
- Agent can create entity Final Outcomes
- Agent can view entity Final Outcomes
After those permissions have been granted, the Final Outcomes tab will appear within the Settings page. Under this tab, there is the option to import the list as a CSV. Please follow the steps below to prepare and share your final outcomes data.
Importing via CSV or Manually
Upload Step
To import a CSV file from the computer, start by clicking the Upload data from file button. The supported file types for the CSV are .csv and .tsv.
If you’re unsure of which format to create your CSV, click the text You can also download a template to get started from the modal to download a template that you can use.
You can also input the data manually through the modal. Inputting at least one piece of data will automatically take you to the Review step.
Note: Certain columns are required while others becoming conditionally required based on which columns you fill out. Refer to the Final Outcomes Schema at the bottom of this Knowledge Base Article to understand which fields are required or optional.
Set Header
1. Once the file is selected from the computer, you will be on the Set Header step. The modal will show a preview of the CSV file and you will be asked to confirm if the first row contains the column headers.
2. If headers were included in the file, you will need to let the CSV importer know which row contains the header so it’s not imported as Final Outcome data.
- Click Yes if the first row contains and you will be taken to the next step
- Click Select another row to select a different row. Once you confirm the row, you will be taken to the next step
- Click No if your file doesn’t contain any headers and you will be taken to the next step
3. You also have the option to change your encoding. By default, the best encoding option will be selected based on the CSV file.
Match Columns
1. On the Match Columns step, you have the option to change the header mapping, confirm header or ignore a column from being imported.
2. If you included a header in your CSV file and it was set in the Set Header step, Alloy will do its best to match the header to the correct mapping. If the mapping looks correct, there will be a Matched validation next to the column. You can either click Confirm Mapping or take no action (Confirm Mapping is selected for you by default). If you do not need a column to be imported, you can click Ignore this column. Alloy will ignore the column when completing the upload. If you made an error in your selection, you can click the Edit button to restore the column.
3. If you need to change the mapping, the mapping does not look correct, Alloy was unable to automatically match, or you did not include a header, you can select the header from the drop-down:
4. To proceed to the next step, click the Next button at the bottom. This will take you to the Review step.
Review
1. On the Review step, you will have the option to review the Final Outcome data and make any final adjustments. If there are any formatting errors that need to be corrected, they will be surfaced at this step by a cell highlighted in red. You can filter for problematic rows by toggling the Only show rows with problems option.
2. Certain columns have a required format. You can hover over the available info tip to learn more about the specific requirements for a header.
3. At this step, you can also input any new data manually into any column or row.
4. You may also click Finish to start the import.
5. If any formatting errors have been unresolved, you can either discard the rows with formatting issues while uploading the remaining rows or go back to correct the rows with formatting errors.
6. Before the import begins, you will confirm one final time to proceed to update the Final Outcomes with a new entry. New entries will be added and existing entries will be updated.
Once the import has been completed successfully, a banner will indicate a successful import.
Final Outcomes Schema
| Column Name | Parameter | Type | Description | |
|---|---|---|---|---|
|
Entity Token OR External Entity Identifier |
entity_token OR external_entity_identifier * | String | Identifies entity | |
| Is Fraud | is_fraud * | If true, then fraud_type, loss_amount, fraud_reported_date, confidence, and first_party are required parameters | Boolean | Is this entity fraudulent? 1 to indicate an entity is fraudulent and 0 to indicate an entity is not fraudulent |
| Active Account | active_account * | If true, then account_opening_date is a required parameter. If false, then account_closure_date is required. | Boolean | Is this entity’s account active? 1 to indicate the account is active; 0 to indicate the account is inactive, whether this is because the account was closed for fraud or because it was never opened |
| Fraud Type | fraud_type | String | Type of fraud; for example First Party, Synthetic, Identity Fraud, Funding, Money Mule, etc. | |
| Loss Amount | loss_amount | Int | Charge-off amount incurred as a result of fraud. | |
| Account Opening Date | account_opening_date | Date | Date on which the account was opened and active | |
| Fraud Reported Date | fraud_reported_date | Date | Date on which the fraud was identified | |
| Account Closure Date | account_closure_date | Date | Date on which the account was closed, if applicable | |
| Confident | confidence | Confidence that entity is fraudulent (confirmed or suspected) | ||
| Exposure | exposure | Total amount that could have been lost due to fraudulent activity | ||
| First Party | first_party | Boolean | If entity is fraudulent, is the fraud type first party? 1 to indicate First Party Fraud, 0 to indicate other | |
| Account Value | account_value | Amount of money in the account | ||
| Comment | comment | String | Any other context that would be useful for this evaluation |
(* denotes fields that are always required)
What types of fraud should be included for the fraud_type column?
The field fraud_type is a free-text form because there are no set definitions for fraud types. Clients may have different labels and definitions. Clients have the ability to report any type of fraud that they wish to via Alloy. In order to give guidance, the common fraud types requested are:
- Third-Party Fraud
- First-Party Fraud
- Identity Manipulation
- Synthetic Fraud
- Device Risk
- Other Fraud
Comments
0 comments
Article is closed for comments.