Glossary
customer
A company or other organization that pays to use Jumio’s products and services to help keep fraudsters and financial criminals off of their platform.
tenant
A secure, isolated environment for a customer. Each tenant includes its own configuration, users, and transactions. A tenant belongs to a customer. A customer can have multiple tenants.
user
An individual working for a Jumio customer who is using Jumio products and services to create, configure, and maintain business applications. A user belongs to at least one tenant that belongs to the customer.
end user
A person who is a customer, patient, constituent, or client of a Jumio customer and who participates in the “customer journey” as part of their interaction with the Jumio customer.
role
A set of permissions that define what a user can see and do in the Jumio Portal.
group
A named set of roles. A user belongs to at least one group and has all of the permissions defined by each role in the group or groups to which he or she belongs.
Jumio Portal
The Jumio website is where users log in to perform the tasks associated with their assigned role(s).
account
A grouping of credentials and transactions associated with an end user.
credential
A form of identification that is associated with an account. Jumio currently supports these types of credentials: Government ID; Selfie; Facemap; Document; Data, which can be either Prepared Data or Device Data.
transaction
An executed business process that is associated with an account. The transaction applies credentials for the account to a workflow and contains the decision rendered by the workflow.
customer journey
The end-user experience for uploading required credentials. Customers can integrate the Jumio Web Client and/or SDKs into their apps, or implement the customer journey themselves and use Jumio APIs to upload credentials and initiate transactions.
service
An identity verification service provided by Jumio that evaluates a set of credentials and renders a decision. A service is invoked by a workflow. A workflow can invoke a single service or a sequence of services and/or risk signals.
risk signal
Risk signals are additional third-party services that can be invoked by a workflow. They are typically used to augment the standard services and provide extra assurance for determining the end user’s fraud risk.
workflow
A workflow is a business process definition that calls a Jumio service or sequence of services and/or risk signals. Each transaction executes a workflow.
capability
A low-level business process that implements all or part of a service or risk signal. Individual capabilities provide the reasons for determining the transaction decision.
decision
Each transaction renders a decision about the credentials that were evaluated. The decision includes one of the following values: PASSED, WARNING, REJECTED. It also includes a risk score. The value is based on the score.
Mobile SDK
The Jumio mobile SDK is one of the channels through which your company can integrate with Jumio. The mobile SDK can be embedded in iOS or Android apps to allow your end users to upload credentials and trigger workflows that evaluate the credentials.
web client
The Jumio web client is one of the channels through which your company can integrate with Jumio. The web client can be embedded in a web application to allow your end users to upload credentials and trigger workflows that evaluate the credentials.
REST API
The Jumio REST application programming interface (API) is one of the channels through which your company can integrate with Jumio. Your applications can call the REST API directly for uploading credentials and finalizing the workflow.
risk score
A numeric value calculated for a capability or workflow indicates the level of fraud risk associated with the evaluated credentials.
supporting data
Data is uploaded in addition to an ID or document that helps identify the end user. These are typically values such as a phone number or email address that cannot be extracted from the ID.