Why is a request called a request?
A request is called a "request for a variety of reasons." They are that:
-
-
- You request information from the user (via email)
- You request permission to run the verification (via explicit or implicit consent)
- You request Evident generate a billable event
- You request the Evident platform un-encrypt certain attributes for you to see
-
You request information from the user (via email)
By default, every request that gets sent out via the Evident platform is associated with an email. Whether or not an email is actually sent is governed by your personal account and template notification preferences. Regardless, Evident has to have information from the user in order to process the request. We can receive that information from the user directly, when they access the submission page, or we can receive that information from you on behalf of the user via the integration. If you are providing information on behalf of the user, then you are using what we call a "full" or SubmitAPI integration.
You request permission to run the verification (via explicit or implicit consent)
Evident's platform was conceived out of a desire to protect both businesses and consumers from unnecessary data exposure. In that vein, the design of the platform requires that all Evident verifications receive implicit consent and some require both implicit and explicit consent. Your user provides implicit consent by accessing the submission page to provide their submission, providing their submission and clicking the "Submit" button. If your business has a 'full' integration or is submitting inputs to Evident on behalf of the user, then we receive this consent through the integration. For background checks, we require explicit consent in the form of the Authorization and Disclosure language in addition to the implicit consent.
You request Evident generate a billable event
Most requests with Evident involve the use of a "service attribute" that is associated with a billable event. If you don't know what a service output attribute is, we recommend reading this article to gain an understanding of what input and output attributes are, and then reading this article to further distinguish between service output attributes and informational output attributes. You can also read more about how billing works at Evident here.
You request the Evident platform un-encrypt certain attributes for you to see
When you create a request in the Evident platform, you are actually telling the Evident platform which pieces of encrypted information you would like it to unencrypted so that you can view. When a request is created, Evident will always search the collection of stored encrypted data for an individual to see if we have the encrypted information that you are looking for in the form of output attributes.
Note: The two requirements that exist for a request to process are that it receives its required inputs and the implicit consent. Without both of these items a request will not move forward from a Pending status into a Complete status.