Objective

Prevent use of an unverified customer wallet.

Evidence

  • Expected evidence: wallet address, network, screening result, verification method, result, approver and timestamp.
  • Evidence location: Odoo customer or transaction record.
  • Retention: according to the AML record-retention policy.
  • Testing method: sample approved wallets and confirm evidence predates first use.
  • Testing frequency: quarterly.

Assurance

Runtime effectiveness results are maintained in Odoo and assessed through the Hermes workflow tracked in ISS-HERMES-001. This note defines design, ownership, evidence expectations and testing method; it does not contain a manually maintained operation, evidence or overall effectiveness rating.

  • Design status: implemented design; runtime effectiveness pending system-derived assessment

Assurance Assertions

  • No customer wallet is used before successful verification and approval.

History

  • 2026-07-26: Normalized evidence metadata and separated design status from runtime effectiveness.
  • 2026-07-26: Added the evidence-system relationship required for Hermes assessment mapping.