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_fullnameUser’s registered full name. Can be hashed in ASCII encoding as well (e.g. MD5, SHA-2 family). Example: John Doestringalert engine, SAR
API request/ user_lastnameLast name of the user.stringalert engine, SAR
API request/ user_firstnameFirst name of the user. alert engine, SAR
API request/ user_middle_nameMiddle name of teh user.stringalert engine, SAR
API request/ user_dobUser’s date of birth in the format of YYYY-MM-DD. Example: 1983-01-01.datealert engine, SAR
API request/ customfield: user_akaAlternate name of the user.stringSAR
API request/ customfield: user_occupationThis 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, etcstringSAR
API request/ customfield: user_NAICSNAICS Code: select the North American Industry Classification System (NAICS) code for the occupation of the usernumericSAR
API request/ customfield: user_TINU.S. taxpayer identification number (TIN) or foreign equivalent without formatting or punctuation. SAR
API request/ user_phone_numberRegistered phone number of a user, including country code. Cannot include spaces or hyphens, the + sign is optional. Maximum length is 19 characters. Example: 36704316088stringalert engine, SAR
API request/ customfield: user_phone_typePhone number – type Home, Work, Mobile, FaxstringSAR
API request/ emailFull email address of the registered user.stringalert engine, SAR
API request/ customfield: user_websiteurlIf the user has web addressstringalert engine, SAR
API request/ customfield: photoid_typeType of the photo ID number for the user.stringSAR
API request/ user_photoid_numberPhoto ID number for the user.stringalert engine, SAR
API request/ customfield: user_relationshipThis is the field for information about the users relationship to the institution where the transaction occured. For example: client, employee, borrower, owner, director etc)stringSAR
API request/ customfield: user_suffixA name suffix may be abbreviated, i.e. Junior can be JR, Senior can be SR, the Third can be III, etc.stringalert engine, SAR
API request/ customfield: user_gendera. Male b. Female c. UnknownstringSAR

 

Transaction data

Field name

Value/Description

Type

Usage in SEON

API request/ action_typeinbound/outboundstringalert engine, SAR
API request: payment_modeMethod of payment used. Examples: cash, check, card, paypal, wire transfer, bitcoin,  online, ATM, POS, unknownstringalert engine, SAR
API request/ transaction typeThe type of transaction, basically purpose. Examples: bill_payment, salary, intra_actor, fee, principal_payment, interest_payment, reverse, refund, loan instalment payment, chargeback, closing.stringalert engine, SAR
API request/ user_bank_accountUser’s bank account number for monetary transfer, for example the IBAN number.stringalert engine, SAR
API request/ transaction_amountFull transaction amount. Decimal point should be . Example: 539.99floatalert engine, SAR
API request/ user_balanceUser’s current balance. Example: 1010.25floatalert engine, SAR
API request/ customfield: commodity_typeIf a commodity is involved in the transaction, you can record the type of commodity. Examples: oil, gold, coffeestringalert engine, SAR
API request/ customfield: instrument_typeFinCEN 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.stringalert engine, SAR
API request/ customfield: product_typeIf 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).stringalert engine, SAR
API request/ customfield: cusip_numberIf 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.numericSAR
API request/ customfield: reference_textReference text of the transactionstringalert engine, SAR
API request/ customfield: branch_office_nameBranch name where the transaction occurredstringalert engine, SAR
API request/ customfield: branch_addressA branch is a location (such as an office or ATM) owned by the financial institution but located separately from the financial institution’s headquarterssringalert engine, SAR
API request/ customfield: branch_rssdEnter the RSSD (Research Statistics Supervision Discount) number of the branch, if known.stringSAR
API request/ customfield: branch_cityCity of the branchstringalert engine, SAR
API request/ customfield: branch_stateOnly if USstringalert engine, SAR
API request/ customfield: branch_postal_codePostal code of the branchstringalert engine, SAR
API request/ customfield: branch_countryCountry of the branchstringalert engine, SAR
API request/ customfield: loan_funding_datetimeLoans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules.datealert engine, SAR
API request/ customfield: loan_settlement_datetimeLoans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules.datealert engine, SAR
API request/ customfield: loan_expected_repayment_datetimeLoans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules.datealert engine, SAR
API request/ customfield: loan_monthy_expected_installment_amountLoans can be used for money laundering. Early lump sum repayments may signal suspicious activity. This data can inform transaction monitoring rules.numericalert engine, SAR
API request/ customfield: customer_credit_limitLarge cash advances, especially on low-limit credit cards, may suggest money laundering. Use this data for transaction monitoring rules.numericalert engine, SAR

 

Geographic data

Field name

Value/Description

Type

Usage in SEON

API request/ user_streetUser’s registered street address line 1. Can be hashed in ASCII encoding as well (e.g. MD5, SHA-2 family). Example: 157 W 26th Ststringalert engine, SAR
API request/ user_cityFull name of city associated with the user’s registered address. Examples: London, New Yorkstringalert engine, SAR
API request/ user_stateThe user registered their home state if it is in the USA.stringalert engine, SAR
API request/ user_zipZip/postal code of a user’s registered address. Examples: 10005, PH1 1EUstringalert engine, SAR
API request/ user_countryCountry code for the user’s registered address. Uses the two-character ISO 3166-1 format. Examples: US, DEstringalert engine, SAR
API request/ customfield: photoid_countryCountry code of the user’s photo ID. Uses the two-character ISO 3166-1 format. Examples: US, DEstringalert engine, SAR
API request/ customfield: photoid_stateState where the user’s photo ID was issued, if is is in the USA.stringalert engine, SAR
API request/ customfield: counterparty_bank_countryThe country in which the receiving bank operates.stringalert engine, SAR
API request/ customfield: counterparty_bank_cityThe city in which the receiving bank operates.stringalert engine, SAR
API request/ shipping_countryA two-character ISO 3166-1 country code for the country associated with the user’s shipping address. Examples: US, DEstringalert engine, SAR
API request/ shipping_cityFull name of city associated with the user’s shipping address. Examples: London, New Yorkstringalert engine, SAR
API request/ billing_countryCountry code for the user’s billing address. Uses the two-character ISO 3166-1 format. Examples: US, DEstringalert engine, SAR
API request/ billing_cityFull name of city associated with the user’s billing address. Examples: London, New Yorkstringalert engine, SAR
API request/ merchant_countryCountry code for the merchant’s address. Uses the two-character ISO 3166-1 format. Examples: US, DEstringalert engine, SAR

 

Counterparty data


Field name

 

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_accountReceiver’s bank account number for monetary transfer, for example the IBAN number.stringalert engine, SAR
API request/ customfield: counterparty_bicReceiver's  bank's  SWIFT/BIC code.stringalert engine, SAR
API request/ counterparty_typeperson/entitystringalert engine, SAR