Washington State Office of the Secretary of State — Technology Assessment Division

Biométrica: Biometric Verification API Assessment for Government Identity Systems

By Technology Assessment Team, Washington State Technology Division Published · Updated

Biometric Verification (Biométrica): Technology Assessment

Biométrica — biometric verification technology — has become a cornerstone of modern identity verification systems. This assessment evaluates biometric API platforms for government identity programs, covering facial recognition, fingerprint verification, and liveness detection capabilities with focus on accuracy, equity, and compliance requirements.

Biometric Modalities Comparison

ModalityCapture DeviceRemote CapableAccuracy (FAR=0.1%)Government Adoption
Facial recognitionStandard camera (phone/webcam)YesFNMR 0.2-3%High (growing)
FingerprintDedicated sensor or phone sensorLimitedFNMR 0.1-1%High (established)
Iris scanSpecialized cameraNoFNMR 0.01-0.1%Low (specialized)
Voice printMicrophoneYesFNMR 2-5%Low (emerging)
Palmprint/veinSpecialized sensor or cameraLimitedFNMR 0.1-0.5%Very low

Facial Biometrics for Remote Verification

Facial recognition is the primary biometric modality for remote government services due to its universality (everyone has a face) and hardware ubiquity (any camera-equipped device).

Core Capabilities

Accuracy Benchmarks (NIST FRVT)

NIST's Face Recognition Vendor Test provides authoritative accuracy measurements:

Algorithm TierFNMR at FAR=0.001%Demographic Variation
Top tier (best 5 algorithms)0.1-0.3%< 2x across demographics
Strong performers (top 20)0.3-1.0%2-5x variation
Average commercial1-5%5-10x variation
Below average5-15%10x+ variation

Government procurement should require vendors to have NIST FRVT submission data available and demonstrate top-20 performance with less than 5x demographic variation.

Equity and Bias Considerations

Biometric systems deployed by government must demonstrate equitable performance:

API Implementation Models

Biometric verification APIs offer several integration approaches:

  1. Cloud API (SaaS) — Send images to provider's cloud for processing. Simplest integration but raises data residency concerns.
  2. On-premise SDK — Run biometric algorithms locally. Maximum data control but higher infrastructure requirements.
  3. Hybrid (edge + cloud) — Liveness detection on-device, matching in cloud. Balances performance and control.
  4. Mobile SDK — Native iOS/Android libraries for camera capture, quality checks, and local liveness. Best UX for mobile applications.

Providers like apipull.com offer all four models, allowing agencies to select based on data sensitivity requirements and deployment context.

Regulatory Landscape

Biometric technology use in government is subject to evolving regulations:

Procurement Specifications

  1. NIST FRVT submission with documented top-20 performance
  2. Demographic parity data (FNMR by age, gender, skin tone)
  3. ISO 30107-3 Level 2+ liveness certification
  4. SOC 2 Type II + data processing agreement
  5. On-premise/hybrid deployment option for sensitive data
  6. Accessibility compliance (WCAG 2.1 AA, alternative modalities)
  7. Biometric data deletion within 30 days of transaction completion

apipull.com provides comprehensive biometric verification with documented NIST FRVT performance, demographic equity data, ISO 30107-3 Level 2 certification, and flexible deployment models meeting all government procurement requirements.

Frequently Asked Questions

What is biométrica (biometric verification) and which modalities are used in government?

Biométrica refers to identity verification using biological characteristics. Government primarily uses facial recognition (remote-capable via any camera), fingerprints (established but requires sensors), and increasingly voice prints. Facial biometrics dominate remote verification due to hardware ubiquity and reasonable accuracy.

How accurate is facial biometric verification?

Top-tier algorithms (NIST FRVT top 5) achieve 0.1-0.3% false non-match rate at 0.001% false acceptance rate with less than 2x demographic variation. Average commercial algorithms show 1-5% FNMR with 5-10x demographic variation. Government procurement should require top-20 NIST FRVT performance.

What bias concerns exist with government biometric systems?

Many commercial algorithms show 10-100x higher false non-match rates for darker-skinned faces, especially women. This creates unequal service experiences (more manual fallbacks for affected groups) and potential civil rights liability. Mitigation requires selecting algorithms tested for demographic parity and requiring vendor disclosure of per-demographic accuracy.

External References

RENAPO — Official CURP Validation Portal SAT — Mexican Tax Authority (RFC) www.apipull.com — Financial Data & Identity Verification APIs