This article describes some particular considerations when deploying AML/KYC Compliance options.
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 threshold at which the customer is prompted for their phone number is configured by the 'Add Trigger > Transaction amount > SMS verification' option within the admin's 'Compliance > Triggers' panel.
For details on configuring SMS, please see the article 'SMS Phone Verification'.
Subsequent verification tiers, such as ID Card Data and ID Card Photo, must be invoked at thresholds higher than that of SMS.
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 needs only to confirm their account via SMS at the ATM.
Location of customer data
Customer profiles may be viewed within the admin's 'Compliance > Customers' panel.
Phone numbers, ID card data, ID card photos, customer photos, daily volumes, and more appears within this panel, along with information about the tiers the customer has verified with.
Raw ID card data (PDF-417 barcodes on card backs), are stored within your server's database tables, and are also available for export via the customers-log script.
Upcoming compliance features
Please follow our @LamassuSupport handle for notices on the latest updates.
Article is closed for comments.