Details About 'Test' Behaviors

On a live program, the exact steps your customers see will vary based on the community being verified, the country the person is located in, and the anti-fraud protections in place. Therefore, in order to test your program setup, we have provided the option to invoke special testing behaviors that enable you to step through different verification states. This empowers you to undertake end-to-end testing of your customer journey, by easily mimicking verification success (aka approval), as well as understand the various paths a customer may take in the process of getting verified. 

Please note: before launching publicly, ensure your program is set to 'live' so that real data sources are used. 

Test behaviors are expected under 2 scenarios:

1. The program is in test mode, as indicated by a label within MySheerID on the program install page as well as at the top of the rendered form, in a red banner.
2. You are using the testing allowlist feature, to invoke test behaviors on a specific verification.

Getting an Instant Approval

To see the customer happy path:

1. Navigate to the page where you have placed the verification form.
2. Enter any dummy data you want into the form.
   1. If you want to see the success email notifer, use a real email address you have access to
3. Submit the form.
4. The verification will be immediately go to Success state.
5. If you’re using a single-use code reward strategy, and codes have already been uploaded to your program, then you will be given one of the real codes. Check you can successfully apply the discount to you cart.

Alternative Paths to Get Verified

SheerID is the industry leader in authoritative verification data, so we have a high rate of instance success. However, there are still many cases in which an individual won't match an instant data source or will be required to show additional proof of eligibility. See this article for an explanation of typical steps in the verification journey.

To see each of these paths, use the following First Names. In each case, you'll be able to complete the step and get to Success.

If First Name equals	And the source is configured on your program, then
SSO	User is prompted to log in to their organization's online portal. Clicking the button will open the testing portal (using SAML), with clear instructions on the page on how to enter an acceptable username and password to simulate successful login.
EMAILLOOP	User is told to check their email inbox and click on the button in the email. Clicking the button simulates successful completion of this step.
UPLOAD	User is prompted to upload a document to prove their eligibility. Uploading a document with a filename that starts with 'approve' will simulate a document review approval.

In the Doc Upload step, there are a total 5 different scenarios to test. Upload the test documents listed below to simulate the different outcomes.

Scenario	How to trigger	Expected
Review approval + email	upload a file with the name  approve_sheerID_docReview_testMode.png	Within 20 seconds after submitting the document, you’ll be taken to the Approved step. Success email notifier will be sent
Review pending	upload a file with the name  needs_review_sheerID_docReview_testMode.png	The verification will stay in doc review pending mode.
Review rejection + email	upload a file with the name  reject_sheerID_docReview_testMode.png	Within 20 seconds after submitting the document, you’ll be taken back to the Doc Upload step and be given the chance to try again. Rejection email notifier will be sent.
Max rejection + email	on the same verification, upload a rejection file 3 times	Within 20 seconds after submitting the final document, you’ll see the Max Failure step. Max failure email notifier will be sent.
Reminder email	once the verification is on the Doc Upload step, wait 15 minutes without further action	If a reminder email notifier is configured on your program, it will be sent.

Hard Stops

In some situations, an individual will be told they cannot continue verifying. To see each of these paths, use the following First Names. 

__ERROR__  (note, that's a double underscore)	User is told there was an error performing the verification.
LIMIT	User is told that they have already redeemed this offer and cannot verify again. This simulates someone hitting your prescribed redemption limit.

 

Looking Up Test Outcomes

To see information about test verifications, click on the Search tool in the left navigation found within MySheerID.

By default, the tool only searches live verifications; to find test mode verifications, add “testing:” as a prefix to the search term. Eg if you started a test verification with the email “[e-mail]”  then you would search “testing:[e-mail]”