Identities are your customers, or more specifically, the details about your customers. Every transaction is initiated by an Identity, but how you treat that information is determined by your regional requirements. Some localities require every detail about your customers be tracked, some jurisdictions require no details at all. It’s up to you to know the laws that apply in your individual case.
The Identity information logging by CAS has been determined to satisfy all currently known requirements - but you’ll have to acquire that information by first setting up your AML/KYC settings.
OFAC (and other) watchlists are automatically checked when a new Identity attempts registration. You can eliminate any specific (or all) lists from these automatic checks. Contact Support for specific information on implementing that procedure.
Identities are quickly viewable by clicking on the Identity listed in the Transaction log.
Identity State Types
The possible classes of Identities are determined by your AML/KYC Settings.
If your settings only permit Anonymous, then Registered and Not Registered Identities won’t be able to use your BATM. If you only permit Registered identities, then Identities marked as Not Registered or Anonymous won’t be able to transact.
Be careful with Identity Class assignment.
Anonymous: no details are collected about these customers. All anonymous customers are grouped together as one single entity when considering transaction limits.
Awaiting Registration: your customer has initiated a transaction that requires registration. You must authorize them to proceed.
Awaiting Verification: your customer has been registered, but it’s “on hold” while the documents are further verified.
Not Registered: the customer is not anonymous, is approved for transactions, but isn’t permitted the higher transaction levels offered to Registered customers.
Registered: the customer is fully authorized.
Rejected: the customer has been found wanting. No transactions will be permitted.
Identities should be processed, reviewed, and approved to meet your local AML/KYC requirements.
Retain local legal counsel to advise you on your specific jurisdictional requirements.
General Bytes CANNOT and WILL NOT advise you on your local AML/KYC requirements. As an Operator, you must recruit suitable legal counsel to ensure your compliance!
Create, test, and select a notification policy for your terminal. If a customer registers, you won't be automatically notified unless you specifically create and activate a policy!
Personal Info should reflect the contents of the identifying document whose “Number” is required to verify the Identity’s identity. All info is optional, and may not be required for every Organization.
Check for duplicates (based on first & last name only).
In North America, this queries the selected provider for the information attached to the phone number.
This is paid service (currently about 13 cents per query).