Integrating & optimizing data flows
Updated on 29.11.24
1 minute to read
Copy link
Overview
Effective financial crime prevention hinges on one critical task: identifying bad actors while protecting legitimate users. This challenge becomes increasingly complex in high-volume transaction environments where determined fraudsters aim to blend seamlessly into the crowd. SEON equips you with the tools and data needed to tackle this complexity head-on.
The right data is key
Maximizing detection capabilities while minimizing operational overhead starts with identifying the right data. SEON helps strike this balance by supporting diverse data types to enhance fraud detection and AML compliance.
There are several data types you can provide:
- Customer data: Information about customers, including their identity and any known affiliations or relationships.
- Transaction data: Details of individual transactions, such as amounts, currencies, locations, parties involved and transaction methods.
- Geographic data: Location-based information that may help identify trends or anomalies in transaction patterns, such as transactions originating from high-risk jurisdictions or unusual cross-border activity.
- Counterparty data: Information about entities involved in transactions, such as businesses, individuals, or intermediaries, including their identities.
- Organization data: Setting up detailed organization information and contact details will enable automated prefilling of any SAR form, reducing repetitive manual workload.
And there are additional data types that SEON will provide:
- Behavioral data: Based on your transaction data, SEON will identify patterns of transactions and account behavior that may indicate suspicious activity, such as unusual transaction amounts, frequency, or timing.
- Alert data: Information generated by SEON’s alerting systems to flag potentially suspicious activity for further investigation, including alert details, severity levels, and timestamps.
- Compliance data: Records of compliance-related activities, such as due diligence checks, investigations, SAR filings, regulatory reports and audit trails.
- Fraud signals: Email verification, identification of risky emails, IP address data and phone numbers, along with a risk score based on Digital Footprint analysis.
- AML customer screening: This process involves checking individual or entity names against various watchlists and databases to identify potential matches with known criminals, terrorists or sanctioned individuals/entities. Additionally, it includes screening for politically exposed persons (PEPs) and adverse media mentions to assess reputational risk and ensure compliance with regulatory requirements.
Providing data in the right format
One of the main advantages of using SEON is its highly flexible format. With our easy-to-integrate API, automating the entire data flow is effortless. Check out our API reference site.
However, for a quick start with SEON and seamless integration, leveraging our default AML transaction rules and enabling SAR autofill capabilities, we recommend using the following data points and format. If this doesn't suit your needs, SEON can provide customized mapping according to your requirements. Please consult with your onboarding officer.
Setting up organization data to enable autofill capabilities for regulatory filings
Say goodbye to repetitive manual work. By inputting your organizational data once in Settings - Case Management - Filing Information, all future regulatory report filings will automatically include prefilled data. This ensures consistency, saves time, and allows your team to focus on high-priority tasks.
Customer data
Field name | Value/Description | Type | Usage in SEON |
API request/ user_fullname | User’s registered full name. Can be hashed in ASCII encoding as well (e.g. MD5, SHA-2 family). Example: John Doe | string | alert engine, SAR |
API request/ user_lastname | Last name of the user. | string | alert engine, SAR |
API request/ user_firstname | First name of the user. | alert engine, SAR | |
API request/ user_middle_name | Middle name of teh user. | string | alert engine, SAR |
API request/ user_dob | User’s date of birth in the format of YYYY-MM-DD. Example: 1983-01-01. | date | alert engine, SAR |
API request/ customfield: user_aka | Alternate name of the user. | string | SAR |
API request/ customfield: user_occupation | This element identifies the description of the occupation, profession, or type of business of the user. Use specific descriptions such as doctor, carpenter, attorney, used car dealership, plumber, truck driver, hardware store, etc | string | SAR |
API request/ customfield: user_NAICS | NAICS Code: select the North American Industry Classification System (NAICS) code for the occupation of the user | numeric | SAR |
API request/ customfield: user_TIN | U.S. taxpayer identification number (TIN) or foreign equivalent without formatting or punctuation. | SAR | |
API request/ user_phone_number | Registered phone number of a user, including country code. Cannot include spaces or hyphens, the + sign is optional. Maximum length is 19 characters. Example: 36704316088 | string | alert engine, SAR |
API request/ customfield: user_phone_type | Phone number – type Home, Work, Mobile, Fax | string | SAR |
API request/ email | Full email address of the registered user. | string | alert engine, SAR |
API request/ customfield: user_websiteurl | If the user has web address | string | alert engine, SAR |
API request/ customfield: photoid_type | Type of the photo ID number for the user. | string | SAR |
API request/ user_photoid_number | Photo ID number for the user. | string | alert engine, SAR |
API request/ customfield: user_relationship | This is the field for information about the users relationship to the institution where the transaction occured. For example: client, employee, borrower, owner, director etc) | string | SAR |
API request/ customfield: user_suffix | A name suffix may be abbreviated, i.e. Junior can be JR, Senior can be SR, the Third can be III, etc. | string | alert engine, SAR |
API request/ customfield: user_gender | a. Male b. Female c. Unknown | string | SAR |
Transaction data
Field name | Value/Description | Type | Usage in SEON |
API request/ action_type | inbound/outbound | string | alert engine, SAR |
API request: payment_mode | Method of payment used. Examples: cash, check, card, paypal, wire transfer, bitcoin, online, ATM, POS, unknown | string | alert engine, SAR |
API request/ transaction type | The type of transaction, basically purpose. Examples: bill_payment, salary, intra_actor, fee, principal_payment, interest_payment, reverse, refund, loan instalment payment, chargeback, closing. | string | alert engine, SAR |
API request/ user_bank_account | User’s bank account number for monetary transfer, for example the IBAN number. | string | alert engine, SAR |
API request/ transaction_amount | Full transaction amount. Decimal point should be . Example: 539.99 | float | alert engine, SAR |
API request/ user_balance | User’s current balance. Example: 1010.25 | float | alert engine, SAR |
API request/ customfield: commodity_type | If a commodity is involved in the transaction, you can record the type of commodity. Examples: oil, gold, coffee | string | alert engine, SAR |
API request/ customfield: instrument_type | FinCEN requires keeping track of any of the following instrument types/payment mechanisms involved in the suspicious activity. You can add to the type of instrument here: Bank/cashier’s check, Foreign currency, Funds transfer, Gaming instruments, Government payment, Money orders, Personal/Business check, Travelers checks, U.S. Currency, Other. | string | alert engine, SAR |
API request/ customfield: product_type | If any financial product is involved in the transaction, you can add it here. Examples include: Bonds/Notes, Commercial mortgage, Commercial paper, Credit card, Debit card, Deposit account, Forex transactions, Futures/Options on futures, Hedge fund, Home equity line of credit, Home equity loan, Insurance/Annuity products, Microcap securities, Mutual fund, Options on securities, Prepaid access, Residential mortgage, Security futures products, Stocks, Swap, hybrid or other derivative, Other (specify type in space provided). | string | alert engine, SAR |
API request/ customfield: cusip_number | If the transaction involves any securities products such as stocks and bonds, you can add the CUSIP (Committee on Uniform Securities Identification Procedures) number here. Should be 9 digit. | numeric | SAR |
API request/ customfield: reference_text | Reference text of the transaction | string | alert engine, SAR |
API request/ customfield: branch_office_name | Branch name where the transaction occurred | string | alert engine, SAR |
API request/ customfield: branch_address | A branch is a location (such as an office or ATM) owned by the financial institution but located separately from the financial institution’s headquarters | sring | alert engine, SAR |
API request/ customfield: branch_rssd | Enter the RSSD (Research Statistics Supervision Discount) number of the branch, if known. | string | SAR |
API request/ customfield: branch_city | City of the branch | string | alert engine, SAR |
API request/ customfield: branch_state | Only if US | string | alert engine, SAR |
API request/ customfield: branch_postal_code | Postal code of the branch | string | alert engine, SAR |
API request/ customfield: branch_country | Country of the branch | string | alert engine, SAR |
API request/ customfield: loan_funding_datetime | Loans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules. | date | alert engine, SAR |
API request/ customfield: loan_settlement_datetime | Loans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules. | date | alert engine, SAR |
API request/ customfield: loan_expected_repayment_datetime | Loans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules. | date | alert engine, SAR |
API request/ customfield: loan_monthy_expected_installment_amount | Loans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules. | numeric | alert engine, SAR |
API request/ customfield: customer_credit_limit | Large cash advances, especially on low-limit credit cards, may suggest money laundering. Use this data for transaction monitoring rules. | numeric | alert engine, SAR |
Geographic data
Field name | Value/Description | Type | Usage in SEON |
API request/ user_street | User’s registered street address line 1. Can be hashed in ASCII encoding as well (e.g. MD5, SHA-2 family). Example: 157 W 26th St | string | alert engine, SAR |
API request/ user_city | Full name of city associated with the user’s registered address. Examples: London, New York | string | alert engine, SAR |
API request/ user_state | The user registered their home state if it is in the USA. | string | alert engine, SAR |
API request/ user_zip | Zip/postal code of a user’s registered address. Examples: 10005, PH1 1EU | string | alert engine, SAR |
API request/ user_country | Country code for the user’s registered address. Uses the two-character ISO 3166-1 format. Examples: US, DE | string | alert engine, SAR |
API request/ customfield: photoid_country | Country code of the user’s photo ID. Uses the two-character ISO 3166-1 format. Examples: US, DE | string | alert engine, SAR |
API request/ customfield: photoid_state | State where the user’s photo ID was issued, if is is in the USA. | string | alert engine, SAR |
API request/ customfield: counterparty_bank_country | The country in which the receiving bank operates. | string | alert engine, SAR |
API request/ customfield: counterparty_bank_city | The city in which the receiving bank operates. | string | alert engine, SAR |
API request/ shipping_country | A two-character ISO 3166-1 country code for the country associated with the user’s shipping address. Examples: US, DE | string | alert engine, SAR |
API request/ shipping_city | Full name of city associated with the user’s shipping address. Examples: London, New York | string | alert engine, SAR |
API request/ billing_country | Country code for the user’s billing address. Uses the two-character ISO 3166-1 format. Examples: US, DE | string | alert engine, SAR |
API request/ billing_city | Full name of city associated with the user’s billing address. Examples: London, New York | string | alert engine, SAR |
API request/ merchant_country | Country code for the merchant’s address. Uses the two-character ISO 3166-1 format. Examples: US, DE | string | alert engine, SAR |
Counterparty data
| Value/Description | Type | Usage in SEON |
API request/ receiver_fullname | Receiver’s full name for a monetary transfer. | string | alert engine, SAR |
API request/ receiver_bank_account | Receiver’s bank account number for monetary transfer, for example the IBAN number. | string | alert engine, SAR |
API request/ customfield: counterparty_bic | Receiver's bank's SWIFT/BIC code. | string | alert engine, SAR |
API request/ counterparty_type | person/entity | string | alert engine, SAR |