Identity & verification
Separate record matching from assurance, bind verification to one purpose and session, limit disclosure by current assurance, and represent third-party authority independently.
Identification answers “which customer record might this be?” Verification answers “what assurance did this participant establish for this purpose now?” Authority answers “what may this participant receive or do?”
Verification lifecycle
Create a purpose-bound session
curl -X POST "$BASE/v1/servicing/verification-sessions" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: verify-maya-account-access-call-91" \
-d '{
"customerId": "412",
"caseId": "case_HBR_COL_51",
"purpose": "account_access",
"channel": "voice"
}'{
"verificationSessionId": "ver_MAYA_81",
"customerId": "412",
"purpose": "account_access",
"status": "challenge_required",
"expiresAt": "2027-05-01T10:30:00-07:00",
"attemptsRemaining": 2
}The API returns allowed challenges, never stored expected answers. Answers are submitted to /v1/servicing/verification-sessions/{verificationSessionId}/answers and evaluated without echoing secrets.
Disclosure matrix
| State | Permitted behavior |
|---|---|
| Unidentified | Generic greeting and safe routing only. |
| Identified, unverified | Non-sensitive process guidance; no account detail. |
| Verified standard | Facts permitted by the purpose and session assurance. |
| Verified elevated | Specifically approved higher-risk disclosure or action. |
| Failed/expired | Sensitive content sealed; alternate journey or handoff. |
Verification is not reusable forever. Expiry, channel change, higher-risk action, contradictory signal, or handoff may require a new or elevated session.
Challenge design
Do not rely solely on knowledge visible in a portal, statement, public record, or compromised credit file. Configure independent possession, provider, authenticated-session, or approved document factors. Attempt counters and fraud controls are shared across workers so channel hopping cannot reset them.
Authorized parties
A verified person still needs authority. Loan-party records represent borrower, co-borrower, guarantor, authorized representative, legal representative, and other supported roles with effective interval, scope, evidence, and verification. A limited authority to receive statements does not permit a payment, promise, address change, or contract modification.
AI boundary
AI workers see verification state and permitted disclosure scope—not challenge answers or raw identifiers. They cannot lower the required assurance, invent a satisfied factor, or continue sensitive disclosure after failure or expiry.