General Bytes tries to facilitate ease of reporting & compliance with local ordinances. Many features have been incorporated over the years towards this end. This article endeavors to provide more details describing these features.
OFAC
ATM server always uses following sanction lists: OFAC, EU, Canada, Czech Republic.
Customer’s name is checked against sanction list every time there is transaction being executed (buy or sell) if there is a match a transaction is not processed( operator doesn’t send coins or operator doesn’t dispense cash). Customer’s crypto address is also checked against sanction list( OFAC list contains also crypto addresses). Sanction list check can be also initiated manually by operator on the identity. Operator also receives notification each time sanctioned identity/address tries to perform transaction.
Exact implementation of OFAC list checking is here: https://github.com/GENERALBYTESCOM/batm_public/tree/master/server_extensions_extra/src/main/java/com/generalbytes/batm/server/extensions/extra/watchlists/ofac
only first name and last name is used. If user provides only one word it is considered to be last name. when user provides middle name then middle name is not used. Name entry is also tested against gibberish entry.
In case of OFAC list is implementation following:
when last name matches but first name doesn’t match the score is 50%. When both last name and first name matches score is 100%. When only last name is provided and matches the score is 100%. When crypto address fully matches (case insensitive) score is 100%. 100% = fail, 50% = passes.
Answered in later point.
Data are downloaded from Treasury every 24hours from here:
https://www.treasury.gov/ofac/downloads/sanctions/1.0/sdn_advanced.xmlwe believe it is the latest version.Every 24 hours. ATM server scans always locally downloaded sanction list.