Persona Verification Evidence and Decision Boundary

Overview

Separate Persona verification lifecycle evidence from the application’s approve, reject, or review decision. Government ID, phone, selfie, document, and database verification types can evolve; the integration must tolerate unfamiliar types and values.

Prerequisites

• Inquiry ID with authorized access
• Versioned business decision policy and manual-review owner
• PII-minimized mapping for needed verification attributes

Instructions

Step 1: Read authoritative resources

Fetch the inquiry and related verification resources under the pinned API version. Record IDs, types, statuses, checks, and timestamps without copying unnecessary PII.

Step 2: Validate completeness