Terms and Definitions
This section defines the special terms used in the documentation. In order to use RAVEN clients must first be configured within RAVEN. A typical client configuration looks something like the following:
Client: This is the company that is contracting for services.
Service Definition: This is a definition of what services have been contracted for and at what price.
Account: One or more accounts may be defined, which may be in multiple currencies. Each account has its own balance and will receive reports separate from other accounts.
Payee: These represent the various “doing business as” names a client might have. For example, the company Senoma Ltd. may have two DBA names: Value Wines and Senoma Wines. Since payments will be sent to these accounts, they are listed as a Payee. A client may have as many Payees as they wish.
Payment Routing Number: The Payment Routing Number, or PRN, indicates where and how an incoming payment should be processed.
Channel: Channels provide the actual processing mechanism under the Payment Routings. Channels are not generally visible to clients except when no suitable channel has been configured, which results in a “No Channel” error.
Submitter: The submitter role allows a user to submit payment to one or more payment routing numbers. Submitters are able view the payments they have submitted and release files they have submitted. Submitters are not able to access payments submitted by others or view client accounts.
Submitter Manager: The Submitter Manager role allows a user to view payments and release files for one or more payment routing numbers. A Submitter Manager is not able to view client accounts.
Account Manager: The Account Manager role allows users to view account statements for the accounts they have access to. They may also request that account statements be emailed to them as a PDF document.
User: Only users are able to interact with RAVEN. Users are created independently of clients and are then related to clients through various ‘roles’. A user may be related to more than one client and may have more than one role with a client. A user can represent either a person or another computer system that interacts with RAVEN automatically. Users should not be shared among multiple people as it then becomes impossible to reliably identify the actual submitter of any given payment. Users have one user name no matter which part of RAVEN they are interacting with, however, they may need to use different passwords/passphrases to access different parts of RAVEN.
Webfolder: Each user may have a webfolder. If a user has a webfolder configured for them, they can use it to submit batch files and receive response files from RAVEN. Logging into a webfolder requires a URL that has been customized for the user as well as a password.
RAVEN Online: A user may be given access to RAVEN Online. There are two levels of access:
- Full access is provided to users who have an RSA token that provides a secure one-time token code to use along with their password.
- Limited access is provided to users who access RAVEN Online with a password only. These users may only view statement information and use the Card Terminal to debit credit cards.
RAVEN API: A user may be given access to the RAVEN API. This is typically done for users that represent another computer system. Interactions with the API must be signed using a passphrase and cryptographic functions.