Skip to content

Universal Credential Verification

Overview

This user story covers the functionality for verifying credentials from the broader Velocity ecosystem, not just those issued through the REC platform. This enables staffing companies to have a comprehensive verification process that works with all valid Velocity Network credentials.

User Stories

US-CV-01: Verify Universal Velocity Credentials

As a staffing company user,
I want to verify credentials from the broader Velocity ecosystem, not just those issued through the REC platform,
So that I can have a comprehensive verification process that works with all valid credentials candidates might present.

Acceptance Criteria

Scenario 1: Verifying Non-REC Velocity Credentials 

Given I am logged in as a staffing company user
When I receive a credential disclosure from a candidate
And the credential was issued by a Velocity Network member other than REC
Then I should be able to verify the credential using the same verification process
And the system should correctly validate the credential's authenticity

Scenario 2: Consistent Verification Process 

Given I am verifying credentials from different sources
When I initiate the verification process
Then the verification steps should be consistent regardless of the credential source
And the user interface should present a uniform experience

Scenario 3: Standardized Results Display 

Given I have verified credentials from different sources
When I view the verification results
Then the results display should be standardized across all credential types
And all five verification areas should be checked and displayed
And the verification status indicators should be consistent

Scenario 4: PDF Report Generation for Any Credential 

Given I have verified a credential from any Velocity Network source
When I request a PDF report
Then the system should generate a report with the same format and information
And the report should include all verification details regardless of credential source

Scenario 5: Handling Different Credential Formats 

Given I receive a credential in any valid Velocity Network format
When I attempt to verify the credential
Then the system should correctly parse and process the credential
And any format-specific attributes should be properly interpreted

Scenario 6: Error Handling for Invalid Credentials 

Given I attempt to verify an invalid or non-Velocity credential
When the verification process runs
Then the system should clearly indicate that the credential cannot be verified
And provide appropriate error messages explaining the issue

Dependencies

  • Verification Process Integration
  • VerifyMyCreds Integration
  • Velocity Network Credential Type Support

Notes

  • The system should maintain a registry of all recognized Velocity Network credential issuers
  • Performance should be consistent regardless of credential source
  • The verification process should be updated as new credential types are added to the Velocity ecosystem
  • Special handling may be required for credential types with unique verification requirements