Usernames, Client IDs, and Web Clerk Logins
Slim CD offers multiple levels of user access and multiple methods of authentication.
1. ClientID, Password – The CLIENTID is used as a UserName, and a password is provided. This gives administrative access to the user over the entire client setup, including the ability to create web clerks (additional users that can log into the website or mobile applications and additional users that can be used to perform web service calls).
2. UserName, Password
a. MetaBank level – gives access to all banks (chains), clients (merchants), and sites (terminals) for a hierarchy and can total across the entire level or for any sub-level
b. Bank/Chain level – gives access to all clients (merchants), and sites (terminals) for a hierarchy and can total across the entire level or for any sub-level
c. ClientID level – gives access to all sites (terminals) for a hierarchy and can total across the entire merchant or for individual sites.
i. ClientID can be used as as a username
ii. Web Admin user (of which the ClientID is one)
iii. Web Clerk (has less permissions than a normal clerk)
3. API Access Credential
a. Are at the CLIENTID or CLIENTID/SITEID level, and are restricted accordingly.
b. Created on the SLIM CD website by a user with authority to do so.
c. Can only call SLIM CD API functions, and cannntegrated ot be used to log into a the SLIMCD.COM webbsite,
d. Requiires no password (password should be set to blank)
e. Can be restricted to specific web service calls or transaction types
REPORTING HEIRARCHY
Slim CD’s API allows developers to access any information at or under the hierarchy level for which they authenticated. For example, if a user is authenticated at the bank/chain level, that user has access to all clienits and sites under that bank/chain (see SLIM CD’s Merchant Hierarchy for more information on hierarchical relationships)
Web clerk logins can log into the website. These userids can also be used to perform web services, depending on their authentication permissions (admin vs clerk),’
For larger merchants, SLIM CD can create custom username/passwords at the chain or bank level for API access upon request. This is useful for creating an automated system that pulls reports for reconciliation purposes. Note that the METABANID or BANKID can perform the same function. Also note that API ACCESS CREDENTIALS can be stored per CLIENTID to achielve the same results without the need for password management.
THE DIFFERENCE BETWEEN USERS AND CLERKS
SLIM CD also supports the concept of a “clerkname field. This field is used when sending transactions to SLIM CD and retrieving reports from SLIM CD. The clerkname can be included in either ProcessTransaction,PostXML or PostHTTP. If clerknaame is not provided, one will be determined based on the authentication credentials. For example, if a username/password is sent to ProcessTransaction, that username becomes the clerk name, The clerkname is not used for authentication, but merely for reporting purposes, This allows software developers to design a system where the authentication of users is automatically included as the clerk reporting or one where they use a standard authentication method for SLIM CD and provide their own clerk/waiter designators for individual employees that access their system.
DEVICEIDS
SLIM CD allow an additional reporting feature, the DEVICEID. This value allows developers to send different information for each device connected in a multi-computer environment, MasterCard has required that each device is exposed to the device level, and this feature allows per-device indicators to be created. Slim CD accepts this information as the DEVICEID on all ProcessTransaction, PostXML and PostHTTP fields,
The SLIM CD website supports DreviceID and Clerk reporting