Preparing to Deploy HYPR Affirm

Solution deployment overview

Affirm is simple to configure, but preparation is key to meeting business requirements. Before deploying Affirm, use the following checklist to ensure a successful deployment:

• Identify the Affirm verification flow steps that align with your business requirements
• Determine what the outcome of successful and unsuccessful flows should look like
• Ensure you have access to the HYPR Control Center
• Request the HYPR deployment team to enable the relevant functionality in your HYPR Control Center (see Feature Flags)
• Configure your IDP integration or external data source
• Configure your verification flow

Configuration tips and tricks

IDV failure modes

Understand the possible failure modes for document and data validation (e.g., data comparison, image integrity, visual authenticity, data consistency, age validation, etc.)

 "breakdown": {
      "data_comparison": {
        "result": "consider",
        "breakdown": {
          "first_name": "consider",
          "last_name": "consider"
        }
      },
      "data_validation": {
        "result": "consider",
        "breakdown": {
          "gender": "clear",
          "date_of_birth": "clear",
          "document_numbers": "clear",
          "document_expiration": "consider",
          "expiry_date": "clear",
          "mrz": "",
          "barcode": "consider"
        }
      },
      "image_integrity": {
        "result": "clear",
        "breakdown": {
          "image_quality": "clear",
          "supported_document": "clear",
          "colour_picture": "clear",
          "conclusive_document_quality": "clear"
        }
      },
      "visual_authenticity": {
        "result": "consider",
        "breakdown": {
          "fonts": "clear",
          "picture_face_integrity": "clear",
          "template": "clear",
          "security_features": "consider",
          "original_document_present": "consider",
          "digital_tampering": "clear",
          "other": "clear",
          "face_detection": "clear"
        }
      },
      "data_consistency": {
        "result": "consider",
        "breakdown": {
          "date_of_expiry": "",
          "document_numbers": "consider",
          "issuing_country": "",
          "document_type": "",
          "date_of_birth": "consider",
          "gender": "",
          "first_name": "consider",
          "nationality": "",
          "last_name": "consider",
          "multiple_data_sources_present": "clear"
        }
      },
      "police_record": {
        "result": "",
        "breakdown": {}
      },
      "compromised_document": {
        "result": "clear",
        "breakdown": {}
      },
      "age_validation": {
        "result": "clear",
        "breakdown": {
          "minimum_accepted_age": "clear"
        }
      },
      "issuing_authority": {
        "result": "",
        "breakdown": {
          "nfc_active_authentication": "",
          "nfc_passive_authentication": ""
        }
      }
    }

Reference: Onfido Document Report Breakdown

Adding an Integration (Directory Source) to HYPR

• HYPR Affirm verifies user attributes such as email, phone number, and address from a directory source.
• Directory sources can be added via HYPR integration settings or advanced settings.
• Required attributes for all target users:
  • Username (UPN for Azure, Username for Okta)
  • Email Address
• Additional attributes may be required depending on the verification flow:
  • Mobile Phone Number (for Phone Number Verification)
  • First and Last Name (for Identity Verification)
  • Manager Information (if Approver type is Manager)
  • Address details (for Location step)

Adding an Integration (Entra / Okta)

• For Entra, configuration on the Entra tenant is required. See Entra ID Integration for steps.
• Once the Entra configuration is complete, the integration can be configured in HYPR.