feat(identities): add Address Document Verification (Adv) endpoints

[armando-rodriguez-cko]

Summary

Adds the new Address Document Verification (Adv) API family introduced in the Checkout.com swagger on 2026-07-16 (INT-1665). This mirrors the existing ID Document Verification client and reuses the identity-verification OAuth scope (no new scope).

Changes

New AddressDocumentVerification client exposing the 7 endpoints, plus request/response models and status enums, wired into the SDK entry point next to IdDocumentVerification:

• POST /address-document-verifications — create
• GET /address-document-verifications/{id} — retrieve
• POST /address-document-verifications/{id}/anonymize — anonymize
• POST /address-document-verifications/{id}/attempts — create attempt
• GET /address-document-verifications/{id}/attempts — list attempts
• GET /address-document-verifications/{id}/attempts/{attemptId} — get attempt
• GET /address-document-verifications/{id}/pdf-report — PDF report

Request model: applicant_id, user_journey_id, declared_data. Attempt request: document. Responses cover AdvVerificationStatuses / AdvAttemptStates, response_codes, _links and the extracted address_document result.

API Reference

Swagger schemas: AdvAddressDocumentVerification*, AdvAttempt*, AdvAddress, AdvAddressDocumentResult, AdvVerificationStatuses, AdvAttemptStates.

Tests

Unit tests covering all 7 endpoints; integration tests scaffolded (skipped, require sandbox entitlement). Build + tests green locally.

[agent-wall-e]

🟡 Risk Classification: MINOR

Approval route: AI Review + Human Approval
Rollback controls: Staged rollout + rollback

Classification reasons

• no_low_class_matched
• prod_source_modified

Operational gates

• ✅ jira_ticket (INT-1665)
• ✅ independent_review

Files analysed: 6

---

_{wall-e 2026.06.19-02 · policy 376219bc71e6…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[agent-wall-e]

🟡 Risk Classification: MINOR

Approval route: AI Review + Human Approval
Rollback controls: Staged rollout + rollback

Classification reasons

• no_low_class_matched
• prod_source_modified

Operational gates

• ✅ jira_ticket (INT-1665)
• ✅ independent_review

Files analysed: 6

---

_{wall-e 2026.06.19-02 · policy 376219bc71e6…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud