Identities

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. This check is forced on the GB Cloud. On a Standalone CAS, you can eliminate any (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!


Identity List

Manually add an Identity. After Entering the basic information & saving it, you can return to upload documents and other required registration pieces.


Identity Details

List all transaction conducted by this Identity.

General Data Protection Regulation / California Consumer Privacy Act

Use these options for compliance where required (currently the EU and California).

Blacklist Identity’s Buy Transaction Addresses: used to prevent an Identity from purchasing coin from any source.

Merge Identities: when 2 (or more) Identities have been created for the same customer, use this option to consolidate the records.

Assign/Create Tag: enables simpler listing options.

Suspend Identity: disables this customer temporarily.

Calculate Limit Expiration: when provided with the BATM & amount of transaction, a date is calculated for a specified amount to be permitted by the applicable AML/KYC limits.

Download All Identity Images: for compliance & audits.


Who, What, When

Your BATM customers will have their supporting documents scanned (if applicable) and their data stored in this area.

State:

The current class of the Identity. Change as desired.

Organization:

The Organization that “owns” the Identity.

Identity Suspended:

Temporarily suspends the identity from transacting on the machine - for example when the identity is under investigation.

Public ID:

A pseudo-random ID used as a common reference for the Identity.

Created by Terminal:

the Terminal the customer was at when signing up.

Created At:

the date and time the Identity was added to the CAS database.

Organization:

the Organization this Identity belongs to.

Updated At:

the last update date & time.

External ID:

used with extensions & external identifiers. See: https://generalbytes.atlassian.net/wiki/spaces/ESD/pages/982482997

Last Watchlist Scan At:

the most recent Watchlist scan date & time.

Last Watchlist Scan Result:

the most recent Watchlist scan result.

The Watchlist is provided by various governmental agencies to scan for individuals flagged as malicious actors. You must ensure a name is properly entered in the details.


Identity Piece Personal Info

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).

“Document Valid To” should be set accurately where possible. See: Document Expiration


Supporting Info

Cell phone numbers used for registration/authorization are listed here.

All documents submitted are located under this tab.

Any selfies collected are found here.


Watchlist Scans

Watchlist scans are automatic (by default). Manual scans may be performed on demand.

All identity watch lists (sanction lists) are re-downloaded by CAS every 24 hours.


Analytics

Statistics provided for quick analysis here. You may also look at all transactions by clicking the TRANSACTIONS button (at the top of the page).


Limits

Remaining limits for this customer will be displayed on their “Identity” profile. Use this data to help identify limit rejections during a transaction. Each implemented limit will be displayed.


VIP

Use these options to grant any person additional “VIP” limits. You may adjust the limits for this person as you see fit, and/or apply automatic discounts.

Any VIP limits supersede normally applicable limits, however every limit that is defined in “normal” limits (e.g. REGISTERED) should also be defined in the VIP section, or they won’t be applied.

Example:

Period

Normal REGISTERED

VIP

Resulting Limit

Period

Normal REGISTERED

VIP

Resulting Limit

Cash Limit Per Day

2000

3000

3000/day

Cash Limit Per Week

6000

 

6000/wk

Cash Limit Per Month

10000

 

10000/mo

  • In this case, the Identity would only enjoy the “per Day” increase in his/her limits. The remaining limits for non-VIP would be applied to the transaction.


Notes

Save any notes about this Identity and/or approvals/rejections.


Save it!

  • SUBMIT & CLOSE returns you to the Identity list.

Copyright © 2022 General Bytes USA LLC