Trigger Verification
Identity Verification
IDENTITY
Verify government-issued ID
Banking Verification
BANKING
Verify bank account ownership
License Verification
LICENSE
Verify professional license status
Employment Verification
EMPLOYMENT
Verify employment and income
Sanctions Screening
SANCTIONS
Check sanctions and watchlists
About Verification-Driven Transactions
The verification domain ensures agreements are not completed based only on claimed identity or manually entered data, but can be conditionally validated against trusted internal or external evidence sources.
Key Features
- Multi-source verification support (Identity, Banking, Employment, License, Sanctions)
- Workflow gating based on verification results
- Evidence linking and provenance tracking
- Time-sensitive validity windows
- Exception handling and manual review queue
- Verified vs unverified transparency
- Provider response normalization
- Confidence scoring
- Remediation path guidance
Business Requirements (BR-03)
This implementation satisfies the following BR-03 requirements:
- BR-03-R1: Material agreement conditions may be marked as verification-required
- BR-03-R2: Platform differentiates between self-attested and verified values
- BR-03-R3: Transaction gating based on verification state
- BR-03-R4: Confidence scoring for verification results
- BR-03-R5: Freshness windows with expiration tracking
- BR-03-R6: Exception decisions traceable to authorized reviewers
- BR-03-R7: Evidence artifacts linked to verification records
- BR-03-R8: Provider response normalization
- BR-03-R11: Remediation paths for failed verifications
- BR-03-R12: Verified data lineage for downstream workflows