This guide explains how to use test mode to simulate different verification results. Testing helps you see what your customers will experience when they use your program.
When you are in test mode, or using test mode features in live testing, the results you see depend on how you enter first and last names into the form. Any other information you enter, like birth dates or addresses, will not change the result.
Use of the trigger words for simulation is primarily intended to check styling, copy, and CTA function throughout the verification process.
It is best to use a real email address that you can access so you can check the emails received at each verification step for correct styling, links, and copy. We strongly recommend that you do not use real personal data on the form besides your email.
Important rules for testing
- One at a time: You can only test one scenario at a time. If one test needs a specific first name and another needs a specific last name, you must do them as separate tests.
- One step only: Test mode simulates only one step of a process. For example, if you test the SSO step and then cancel to try to see document review, it may not work correctly. If you want to switch between steps, reload/restart the form and enter a different trigger word.
- Not just the flow: This is your chance to review ALL aspects of your program. Make sure you are clicking links, checking copy and appearance, and generally inspecting each part of the process.
- Check your settings: A test will only work if that verification method is turned on for your program. For example, testing an email loop will not work if your program does not use email loops.
- Each program has a set of default verification methods enabled - you can view the list here
- Get help: If you have made changes to the default verification methods or you are not sure which methods your program uses, check your settings in MySheerID or contact Product Support.
You can use these steps in test mode or during live testing.
Authoritative Instant Success and Success Email
What is Authoritative Instant Success?
Authoritative instant success is when the system confirms a user is eligible in real time, using an authoritative data source. This usually happens in less than 20 seconds. The approved user gets their reward right away and can use it immediately.
How to test Authoritative Instant Success
- Go to your verification form
- Fill out the form using any name that is not a trigger word
The form will show a success message
Notes
If you use coupon codes, you will see a shortened, partially redacted version of a code instead of a real one.
If SheerID hosts your success email and you have entered a real email address, the success email will also trigger.
If you are using webhooks, the success webhook will also fire - double check that it has fired successfully and the expected outcome has occurred.
SSO
What is SSO?
SSO stands for Single Sign-On. It allows users to verify their status by logging into and existing account from their school or work.
How to test SSO
- Go to your verification form
- Enter SSO as the first name
- Fill out the rest of the form
- The form will move to the SSO login step
- Enter the appropriate SSO login information (provided on the screen)
The success step will appear if all information has been entered correctly
Notes
This only works if your program has SSO verification enabled.
If the SSO login information was not entered correctly due to a spelling error, or the SSO window is closed, the verification form will proceed to the next step in the verification process.
If the SSO step is not completed appropriately and the verification has proceeded to the next step (typically document review), you should end your test and either try SSO again from the beginning, or start a new test verification to simulate document upload.
Email Loop with Domain Validation (ELDV)
What is Email Loop with Domain Validation?
With ELDV, an email loop verifies a user by sending a link to their official email address, such as a school or work email. The user must click that link to prove they own the email account.
How to test ELDV
- Go to your verification form
- Enter EMAILLOOP as the first name
- Fill out the rest of the form
- Check your email inbox
- Click the link in the email received to simulate the success step
Notes
Ensure your program is set up to use email loop.
You must enter a real, accessible email address to test this functionality.
All Upload scenarios will have the name entered as below:
Upload: Document Review (Approve)
What is Document Review Approval?
If a user cannot be verified instantly, they may need to upload a document. The uploaded documentation will be reviewed by SheerID and approved if it is valid. This test simulates the scenario where a document is approved.
At the bottom of this article, there are links to three testing documents that can be used in different upload scenarios. For this test, you will need the file starting with "approve". You may also use any file of your choosing, so long as you change the file name to being with "approve" before uploading.
How to test Document Review Approval
- Go to your verification form
- Enter UPLOAD as first name
- Fill out the rest of the verification form
- Upload your testing file starting with "approve"
- The system will simulate an approved review
Notes
If you have entered a real email address, you will receive an approval email as part of this test.
Upload: Document Review (Reject)
What is Document Review Rejection?
This happens when a user uploads a document that does not prove they are eligible. The document is rejected and the user is told why.
At the bottom of this article, there are links to three testing documents that can be used in different upload scenarios. For this test, you will need the file starting with "reject". You may also use any file of your choosing, so long as you change the file name to being with "reject" before uploading.
How to test Document Review Rejection
- Go to your verification form
- Enter UPLOAD as first name
- Fill out the rest of the verification form
- Upload your testing file starting with "reject"
- The system will simulate a rejected review
Notes
If you have entered a valid email address, you will receive a rejection email explaining the result of the verification and what is needed on future uploads to increase chances of success.
Rejection emails will look something like below. Please note that the text outlined in red is dynamic and will change based on the reason for rejection selected during review of the end user's document. The rejection reasons are preset by SheerID and are not editable.
Upload: Document Review (Pending)
What is Document Review Pending?
This is the state a user sees after a successful upload, while they are waiting for SheerID to review their documentation.
At the bottom of this article, there are links to three testing documents that can be used in different upload scenarios. For this test, you will need the file starting with "needs_review". You may also use any file of your choosing, so long as you change the file name to being with "needs_review" before uploading.
How to test Document Review Pending
- Go to your verification form
- Enter UPLOAD as first name
- Fill out the rest of the verification form
- Upload your testing file starting with "needs_review"
- The form will show the "Processing" screen, and when the timer runs out, it will transition to the "Reviewing" screen
Notes
The status will stay as pending for this test - it will not transition to show additional screens like you would see after SheerID had reviewed the documentation.
Upload: Max Rejection
What is Max Rejection?
Users have three tries to upload a valid document for review. Once they reach the limit, they can no longer continue verification attempts on that specific verification request.
At the bottom of this article, there are links to three testing documents that can be used in different upload scenarios. For this test, you will need the file starting with "reject". You may also use any file of your choosing, so long as you change the file name to being with "reject" before uploading.
- Go to your verification form
- Enter UPLOAD as first name
- Fill out the rest of the verification form
- Upload your testing file starting with "reject" three times (3x)
- The system will show that the review limit has been exceeded for the request
Notes
This test helps you see the final rejection email sent after too many failed attempts, so be sure you are entering a real email address.
This effectively ends the consumer journey at this step, however, customer support is able to assist with verifications that have reached max upload if contacted, and the consumer may also start a new verification request on their own.
Three times is the default amount of uploads offered per verification request.
Upload: Reminder Email
What is a Reminder Email?
If a user starts the verification process but does not finish it, SheerID can send a reminder email to help them complete their verification.
How to test a Reminder Email
- Go to your verification form
- Enter UPLOAD as the first name
- Stop the process at any point before success
- Wait the designated time, and check your inbox
Notes
If you have reminder emails configured for your program, you should receive one on any verification that has not reached the success step, after the designated time has passed.
The link in the reminder email will take you back to the step in the verification process where you left off.
The default time for receipt of reminder emails is 15 minutes. For customers working with SheerID's Professional Services team, the reminder email may be configured for a different amount of time.
Errors
In some scenarios, an individual may be told they are unable to proceed with the verification process. The following can be used to simulate each of these paths.
General Error
What is an Error?
This simulates a general technical error in the system.
How to test an Error
- Go to your verification form
- Enter __ERROR__ as the first name
- Fill out the rest of the verification form
- The form will display an error message
Notes
The entry is a double underscore _ _ ERROR _ _. The underscores must be joined together, no spaces may be used.
This step is generally only needed when testing API programs. There is only one error trigger, however the error screen and messaging therein is variable.
General errors contain a CTA to allow the end user to try again.
Limit
What is a Limit?
This simulates a user who has already verified for the offer the maximum number of times allowed, or who has attempted to verify too many times without success and has been blocked.
How to test a Limit
- Go to your verification form
- Enter LIMIT as the first name
- Fill out the rest of the verification form
- The form will show a message stating the verification limit has been exceeded
Notes
Use this to check your messaging for users who try to verify more than the allowed amount of times.
No emails are sent on limited requests and there is no option offered for the end user to begin a new request.
Reject - Offer Protections
What is an Offer Protections Rejection?
The messaging shown in this simulation is generally triggered when users hit certain offer protection rules.
How to test an Offer Protections Rejection
- Go to your verification form
- Enter REJECT as the last name
- Fill out the rest of the verification form
- The form will show a message stating the user is unable to be verified
Notes
No emails are sent on this simulated step.
Trigger Words Quick Reference Chart
Trigger Words Quick Reference Chart | ||
| Step | Trigger Word | Document(s) Needed |
| Authoritative (Instant) Success | First Name = Approve | None |
| Single Sign On | First Name = SSO | None |
| Document Review (For Approval, Rejection, or Pending) | First Name = UPLOAD | Approval document Reject document Needs Review document |
| Error | First Name = __ERROR__ | None |
| Limit | First Name = LIMIT | None |
| Offer Protections Reject | Last Name = REJECT | None |