This article describes some particular considerations when deploying AML/KYC Compliance options.
Please check back as this article is expanded.
Basis of customer accounts
Accounts are created through the verification of a customer's phone number during the first step of the KYC flow. The fiat threshold at which the customer is prompted for their phone number is configured by the 'SMS' option within the admin's 'Global Settings > Compliance' panel.
For instructions on configuring SMS, please see the article 'Phone number collection'.
Subsequent verification tiers, such as ID Card Data and ID Card Photo, must be invoked at a fiat threshold higher than that of SMS, and with SMS remaining enabled.
Prior to IDs being requested of them, customers will first confirm their phone number. In this way, the ID documents are thereafter associated with their phone number, so that on subsequent visits, the customer need only to confirm via SMS (their 'account') to identify with the cryptomat.
Location of customer data
Customer profiles may be viewed within the admin's 'Maintenance > Customers' panel. Currently, phone numbers, scanned ID card photos, and daily volumes will appear within this panel, along with information about the tiers the customer has verified with.
Scanned ID card data (back of card barcodes), if enabled, are stored within your server's database tables, available for export via the customers-log script.
Upcoming compliance features
In addition to the features detailed in our Compliance section, the v7.3 (Crafty Chnemu) release is scheduled to bring customer-facing camera support; ID photo text parsing; configurable periods for ID card expiration; and limits for volume per period, transactions on consecutive days, and number of transactions per period.
Please follow our @LamassuSupport handle for notices on the latest updates.