Since AML/KYC compliance is a requirement in many jurisdictions, we offer an ID-scanning module that integrates with IdentityMind, which provides services tailored to the needs of bitcoin ventures.
We advise consulting with a legal professional in regards to any local regulation you may be subject to, and we may be able to recommend one in your area. Also, an introduction to AML/KYC terms can be found in IdentityMind's whitepaper, '10 Essential Terms for Bitcoin Regulation'.
NOTE: These instructions will change as we streamline the setup process during our beta testing period. At this time, the module supports scanning of indentity documents which feature PDF417 2D barcodes.
When using the IdentityMind plugin, the user experience flow is:
- Press Start
- Scan a bitcoin address QR code
- Hold an ID with 2D-barcode (PDF417) against the scanning window
- Machine submits information to IdentityMind
- If approved, machine prompts user to insert bills.
- If not approved, machine informs user of an identification problem and to contact the operator.
Register with IdentityMind
First, please contact IdentityMind at email@example.com in order to establish an account. Once provided with credentials, configure your KYC/AML settings following our settings guide. Ensure these settings are configured first before enabling the plugin on your server, as after running the setup script, your machine will begin to prompt for ID scanning.
Configure the compliance module
In your server's terminal, run the setup script which will prompt for your IdentityMind credentials:
When prompted for staging mode, depending on which set of credentials you've been provided by IdentityMind, hit Enter to put into production mode, or type Y and Enter for staging (also known as sandbox) mode. Staging mode will enable the machine flow for ID scanning and pass it through IdentityMind, though all scans will pass. IdentityMind will need to see that the data sent to them is parsed succesfully, after which, they'll provide production credentials.
To change these credentials and switch to production mode, run the above setup.js script again.
Afterwards, perform test transactions to confirm. If you have any questions on the process, we're happy to help. Please reach out to firstname.lastname@example.org.
If the maximum per transaction limit is changed within the admin, the machine will stop prompting for IDs. To resolve, run the setup.js script again. The updated transaction limit will still be imposed.