HYDRA Documentation
  • Introduction to Hydra Chain
  • HydraGon
    • Migrate to HydraGon
    • Staking Calculator
  • Legacy Hydra
  • FAQ
  • Hydra web wallet
    • Create New Wallet
      • Key File Option
      • Mnemonic Words Option
    • Access Your Wallet
      • From Mnemonic Words
      • From Private Key
      • From Key File
    • Send and Receive Assets
      • Receive Assets
      • Send Assets
    • Add HRC20 Token
    • Setup Offline Wallet
  • Hydra web browser extension
    • How to integrate with dApps
  • Hydra for Beginners
  • Ledger Nano Guide
  • Hydra Bridge
  • HydraDEX
    • Adding and Removing Liquidity
    • Liquidity Mining on HydraDEX
  • Useful Links (Legacy)
  • Essentials
    • UTXOs Accounting
    • Test & Main Networks
    • Desktop wallet basic usage
    • Wallet Encrypt, Backup and Restore
    • Hydra Core Wallet Commands
    • Adding Nodes
    • Encrypt and Unlock Hydra Wallet
    • Wallet Recovery With Salvagewallet
    • bech32 support
    • Repositories
    • Hydra Exchange Usage Guide
    • How to Add Options
    • How to Use bootstrap.dat
    • Command Lines (RPC API)
    • Guidance of Hydra Deployment and RPC Settings
    • How to Build Hydra on Raspbian
  • HRC20 Tokens
    • HRC20 Token
    • HRC20 Raw Transactions
    • HRC20 With Hydrachainjs
    • HRC20 DApp
  • HRC721 Tokens
    • HRC721 Token - How to deploy
  • How Transactions Work
  • Hydra Economy (Legacy)
    • The Flexible Supply Mechanism
    • Legacy Staking Calculator
  • Installation Guides
  • Guide for Linux
  • Guide for Raspberry Pi
  • Guide for MacOS
  • Staking HYDRA Coins
    • Setting up Staking
    • Staking with Windows VPS on AWS
    • Staking with Linux on DigitalOcean VPS
    • How to Stake Hydra on Linux
    • Stake With Linux VPS
    • How to Stake on FreeBSD
    • Hydra node health check
    • Superstaking
    • Delegating to Superstaker
    • Delegating via Mobile App or Web Browser
    • Lydra Basics
    • Understanding LYDRA — Key Concepts and Dynamics
  • Hydra Chain Core Team
  • KYC/AML Policy
  • Privacy Policy
  • API Documentation
    • Explorer API (in work)
      • General Blockchain Info
      • Fetching Transaction History for HYDRA and HRC20 tokens
      • Block Info
      • Transaction Info
    • Hydra DEX API
  • Community Tools
    • Github repository
    • Docker image for Hydra Node
    • Hydradex.org Custom Lists
  • Security Audits Hydra Bridge
Powered by GitBook
On this page
  • Anti-money Laundering, Counter-terrorist Financing § Eligibility Policy
  • Introduction
  • 1. Identification
  • 2. High risk third countries
  • 3. Eligibility
  • 4. Politically exposed person /PEPs/ and affiliates
  • 5. Identity verification
  • 6. CFT verification
  • 7. Origin of funds

Was this helpful?

KYC/AML Policy

Anti-money Laundering, Counter-terrorist Financing § Eligibility Policy

Introduction

LockTrip LLC, with UIC 204752244, having its seat and management address at Sofia, post code 1799, Bulgaria, Mladost District, 78 Alexander Malinov Blrd., hereinafter as LockTrip, is not among the obliged entities which, according to the applicable European legislation, should apply the measures for prevention of the use of the financial system for the purposes of money laundering and terrorist financing regarding its clients.

Notwithstanding the above mentioned, for the purposes of the legitimate interests pursued by LockTrip to prevent its activity to be involved in any kind of illegal activity including but not limited to money laundering and terrorist financing as well as the public interests for prevention of abuses, LockTrip will implement effective Anti-money Laundering /AML/ and Counter-terrorist Financing /CFT/ internal procedures and mechanisms.

One of the international standards for preventing illegal activity is customer due diligence /CDD/. According to the CDD, LockTrip establishes its own verification procedures within the standards of AML and KYC frameworks.

1. Identification

LockTrip’s identity verification procedure requires the User to provide LockTrip with national ID or international passport, whose validity has not expired.

LockTrip reserves the right to collect User’s identification information for the AML/KYC Policy purposes.

In order to identify individuals, the following data are collected:

  • the names of the User;

  • the date and place of birth;

  • an official personal identification number or other unique element for establishing the identity, contained in an official identity document, the term of validity of which has not expired and on which there is a photo of the client;

  • any citizenship that the person possesses;

  • country of permanent residence and address (mailbox number is not sufficient).

In connection with the above identification, LockTrip will collect copy of the presented identity document.

User’s identification information will be processed strictly and in accordance with LockTrip’s Privacy Policy and applicable regulations.

2. High risk third countries

LockTrip accepts that certain third countries have been identified by the European Commission as having strategic weaknesses in AML measures and legislation and these third countries are listed in Commission Delegated Regulation (EU) 2020/855[1]. In this regard LockTrip has the right not to establish business relationship with Users, who are residents or citizens of these high-risk third countries which have provided a written high-level political commitment to address the identified deficiencies and have developed an action plan with FATF.

3. Eligibility

LockTrip may deny services to the users, who are residents or citizens of other third countries such as USA, China and Canada due to the threat of imposing regulatory or other sanctions to LockTrip.

4. Politically exposed person /PEPs/ and affiliates

LockTrip accepts that there is an increased risk of entering into business relations with individual who is or has been entrusted with a prominent public function /PEPs/, family members of PEPs and also individuals who are closely connected to PEPs, either socially or professionally /close associates /.

In this regard LockTrip will require from the Users to declare if they are or have been PEPs or family members of PEP or close relatives of PEP.

5. Identity verification

LockTrip may take steps to confirm the authenticity of documents and information provided by the Users. All legal methods for double-checking identification information will be used and LockTrip reserves the right to investigate certain Users who have been determined to be risky or suspicious.

LockTrip reserves the right to verify User’s identity in an on-going basis, especially when their identification information has been changed or their activity seemed to be suspicious (unusual for the particular User). In addition, LockTrip reserves the right to request up-to-date documents from the Users, even though they have passed identity verification in the past.

6. CFT verification

LockTrip will not provide services to Users who have been identified by the competent authorities as having access to terrorism or its financing or who have been subject to sanctions for terrorism or terrorist financing. Therefore, LockTrip will check the Users in lists of European and global counter-terrorism organizations.

7. Origin of funds

LockTrip will provide services only to Users who can prove that their origin of funds is from a legal source. In this regard, Users will be required to declare the origin of funds used in the business relationships.

This Policy was last updated on 7/3/2021. We may change its contents by updating this page to reflect changes in applicable legislation or LockTrip KYC practices.

[1] Commission Delegated Regulation (EU) 2020/855[1] of 7 May 2020 amending Delegated Regulation (EU) 2016/1675 supplementing Directive (EU) 2015/849 of the European Parliament and of the Council, as regards adding the Bahamas, Barbados, Botswana, Cambodia, Ghana, Jamaica, Mauritius, Mongolia, Myanmar/Burma, Nicaragua, Panama and Zimbabwe to the table in point I of the Annex and deleting Bosnia-Herzegovina, Ethiopia, Guyana, Lao People’s Democratic Republic, Sri Lanka and Tunisia from this table

PreviousHydra Chain Core TeamNextPrivacy Policy

Last updated 4 years ago

Was this helpful?