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 areas require no details at all.

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.

To manually add a new Identity, select the type of Identity (Registered, Unregistered, etc) from the left menu bar, and click on “+ADD”. After submitting the basic info, you can re-visit the new Identity and add images or phone numbers.

Identity Classes:

Identities are quickly viewable by clicking on the Identity listed in the Transaction log.

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

These identities will need to 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!

Awaiting Registration

This Identity has requested a transaction that requires registration. They have submitted the requested information to you. You must now review their submission, verify its authenticity, and decide the applicant’s fate.

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

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.

 

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 “State” is adjusted to define the permissions granted to this Identity. Your choices are:

Registered

This Identity has been reviewed and is completely approved.

Rejected

This Identity has been rejected for all transactions requiring registration.

Not Registered

This Identity may still be permitted to conduct minimal transactions that don’t exceed certain limits and don’t require complete AML/KYC registration.

Identity Piece Personal Info

Personal Info should reflect the contents of the identifying document whose “Number” is required to verify the Identity’s identity.

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

Data

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

All documents submitted are located under this tab.

Any selfies collected are found here.

Statistics of individual customer transactions are enumerated here.

Remaining limits for this customer will be displayed on their “Identity” profile:


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.

Save it!

Please note that all identity watch lists (sanction lists) are re-downloaded by CAS every 24 hours.