Look up a word to get its definition or description
An AML officer can leave comments on any client profile and attach a file.
You can customize your FinchGuard experience:
- 3.Workflows. You are able to create a specific onboarding pipeline with the necessary steps for your clients to follow
Your client data is stored at AWS servers in the EU (if you are a European client) or in Switzerland (if you are Swiss)
As every exception to the AML Policy must be documented, a user of FinchGuard can add a comment to any client profile and attach a file.
A politically exposed person (PEP) is identified by checking thousands of sources.
FinchGuard offers real-time monitoring of both company data (incl. directors, shareholders, UBOs etc.) and blockchain transactions. If negative news comes up after a while, an AML officer will be notified.
Notifications about suspicious transactions can be easily automated if there is a specific template required by the regulator.
FinchGuard offers real-time monitoring of the companies, their key personnel and UBOs. If adverse information is found, a user is notified about it.
An AML officer can manually set a high or normal risk level for each client.
FinchGuard supports the following user roles: admin (all rights), AML officer (no rights to change settings), and read/only access.
FinchGuard allows checking a great number of sanction lists such as OFAC, UN, HMT, EU, DFAT and more.
Push notifications to a dedicated Slack channel will help keep not only the compliance team but also your sales force informed about the current status of clients being onboarded.
FinchGuard currently allows to set up the following alerts:
- daily turnover per client
- monthly turnover per client
- domicile (country of incorporation) of a client
- (for fiat transactions) payment country (where the bank of a client is located)
- (for blockchain transactions) a risk score that is calculated based on the share of high-risk sources associated with the transaction (examples are known hacks, scams, child abuse, gambling etc.)
The travel rule requires verification of the ownership of the wallet from/to which digital assests are sent. A VASP has to identify a sender for incoming and a recipient for outgoing blockchain transactions.
- 2.If a sender or a recipient of a transaction is an independent party(for transfer from/to third parties), information must be exchanged between the VASPs involved. FinchGuard has not implemented this feature yet. ETA Q4 2023.
FinchGuard supports the following methods of wallet verification (as per the Travel Rule requirements):
- 1.Satoshi test
- 2.Print screens (screenshots)
- 3.Connecting a Web3 wallet (such as MetaMask)