How it Works
Each SheerID verification follows a distinct flow, which is made up of discrete steps. As your user proceeds through the steps, our API will return a step name for what it expects to receive next, to progress the verification through its flow. In this section you’ll learn about flows and steps, and what to do if you encounter an error along the way.
A SheerID flow is the series of steps that lead to a verification outcome. If a subject can be instantly verified, the flow is very simple:
In the case of a successful instant verification, we will receive the data from the user, run it against
an authoritative data source for verification, and return a
success response, indicating that you may
now proceed to checkout.
Unfortunately, not all verifications will be successful on the first try, so you must account for all possible user journeys, including an unsuccessful instant outcome, which sends a user to the document review step, data entry errors, and so on.
The image below represents a complete flow for a US student verification, which is typical of most segment flows. If an instant verification is not possible, the flow proceeds to the Doc Upload step, in which the user is asked to upload documentation verifying their eligiblity for the offer. If the documentation is successfully uploaded, proceed to the Pending step, and so on, until an outcome is determined, either successful or unsuccessful.
See Flow Diagrams for detailed flows for the various supported segments.
A SheerID verification happens one step at a time. Steps combine together into a flow. Step names may vary slightly depending on the segment, e.g., “Collect student info” vs. “Collect military status,” but the basic steps are similar from one segment to the next.
Below we will discuss the basic details of the different steps you will encounter in the verification process.
Collecting information from a user is the first step in a verification. This is where you render a form.
Instant verification may not be possible for a given user or verification type. In these cases, we will require that the user uploads documentation in order to complete the verification. Documents will be reviewed manually by SheerID staff.
The image below is an example of a student experience for the
docUpload step, giving
the user the option to upload the required documentation.
When the user uploads documentation, the flow moves to the
pending step, during which time SheerID staff will review the provided documentation to verify its authenticity and adherence to the rules of the offer.
Below is an example user experience for a student who has successfully uploaded the requested documentation.
Since the document review process is manual, it takes some time, and you should assume that the user will not wait on your site for the approval. Provide an experience that allows them to redeem their offer from the approval email that you configured in MySheerID.
If the user fails to provide valid documentation, after 3 attempts the verification will move to the error step. At this point the verification has failed, and you must start a new verification process.
Currently we support the following six segments in our self-service platform: US Student, Military, First Responder, Senior (age verification), Teacher, and Medical Professional. The links below will take you to detailed flow diagrams for each segment.
If you are looking for a segment other than those listed above, please see Who We Verify on our corporate website, and contact your Account Manager for more details.
Within certain Segments, there may be eligible Subsegments to which you can offer a narrower targeted offer. Available subsegments include:
|Student||- Full + part time college students
- College-bound high school students
|First Responder||- Firefighter
- Emergency Medical Technician
|Military||- Active Duty
|Senior||Subsegments are determined by an age range selector.|
The verification flow for a subsegment is inherited from the parent segment. We recommend including all available subsegments in your offer for maximum reach, and using subsegments only when they align with your specific offer criteria.
You can configure Eligible Subsegments in the Programs Settings section of MySheerID.
Errors may occur during verification flows, primarily due to improperly inputted data from the user. Fortunately, such errors are recoverable, and when encountered, our API will provide you with the information you need to retry the step.
Certain rare errors are non-recoverable and may require you to start the verification process anew.
To learn more about errors and how to handle them, see Errors in our REST API documentation.
For a complete list of possible