Reference: Friction Levels and Feature Flags
Friction Levels
Affirm offers several pre-configured friction levels, each determining the number and type of verification steps required in a verification flow. Use these as a guide to select the right balance of security and user experience for your scenario.
Friction Level Comparison
| Level | Phone Verification | Location | Document Auth | Liveness Check | Name Checking | Photo ID & Liveness | Chat/Video | Attestation | Approver Assignment |
|---|---|---|---|---|---|---|---|---|---|
| Highest | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | ✓ | Manager |
| High | ✓ | ✓ | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | Manager |
| Medium | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ | HYPR Automated |
| Low | ✓ | ✓ | ✗ | ✗ | ✗ | ✓ | ✗ | ✗ | HYPR Automated |
| Lowest | ✓ | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | HYPR Automated |
| None | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | HYPR Automated |
- ✓ = Enabled
- ✗ = Disabled
Tip: Choose a higher friction level for sensitive verification flows (e.g., onboarding, admin access) and a lower level for routine or low-risk scenarios.
Feature Flags
Feature flags are set by the HYPR deployment team to enable or customize Affirm functionality. Some common flags include:
| Name | Description |
|---|---|
| AFFIRM_PAID (Required) | Enables core Affirm functionality |
| AFFIRM_CC_ADMIN_ONBOARDING | Enables the CC Admin verification flow |
| ENABLE_AFFIRM_CITRIX_OPTIMIZATION | Enables Affirm Citrix media redirection optimization |
| AFFIRM_AWS_PINPOINT_SMS_V2_API | Uses v2 End User Messaging SMS APIs for international SMS support |
| AFFIRM_HELPDESK_SUPPORT | Enables helpdesk access & helpdesk code display to requestor |
| AFFIRM_WATCHLIST_STANDARD_ENABLED | Allows watchlist standard checks options for eligible CC admins |
Test Cases
Below are example test cases to help validate your Affirm deployment. These cover both functional and non-functional requirements.
| Test ID | Description | Expected Result | Type | Comment |
|---|---|---|---|---|
| 1 | Validate user can upload document and take photo with all options | User completes verification with all options | Functional | Test all 3 options: Scan QR, Copy Link, Get link via SMS |
| 2 | Validate system behavior if interrupted during upload/photo | Correct error message shown | Functional | Multiple error scenarios |
| 3 | Validate time to verify after submission | Verification completes within 5 min | Non-Functional | SLA check |
| 4 | Validate e-pass home page after verification | E-Pass home page shown, user can change password/unlock | Functional | |
| 5 | Validate login with new password | User can log in with new password | Functional | |
| 6 | Validate page response time | Page loads within SLA | Non-Functional | SLA check |
| 7 | Validate behavior after repeated verification failures | Meets compliance requirements | Non-Functional | |
| 8 | Verify National ID cards allowed only for certain countries | Only allowed for listed countries | Functional | |
| 9 | Validate options after selecting document | Continue on phone and Upload photo options available | Functional | |
| 10 | Validate upload photo option | User can complete verification with Upload Photo | Functional | |
| 11 | Validate 'Get secure link' button | Button is displayed and enabled | Functional | |
| 12 | Validate secure link options | Scan QR, Copy Link, Get link via SMS available | Functional | |
| 13 | Validate error for incorrect mobile number | Error message shown | Functional | |
| 14 | Verify 'Login with ID Verification' option | Option is available after valid email | Functional | |
| 15 | Validate 'Login with ID Verification' is clickable | User can click and proceed | Functional | |
| 16 | Verify 'Start Verification' button | Button is displayed and enabled | Functional | |
| 17 | Verify 'Issuing Country' dropdown | User can select country | Functional | |
| 18 | Verify allowed document types | Passport, National ID, Driver's license allowed | Functional | |
| 19 | Verify National ID cards for specific countries | Only allowed for listed work locations | Functional |
For a full list of test cases and details, consult your deployment or QA team.