The right client is onboarded.
Documents, biometrics, databases and screening establish identity and authority. The firm records trusted contact details and begins the relationship on a sound foundation.
Vericode vs KYC and VOI · Complement, not competitor
KYC and VOI establish identity. Vericode checks the trusted phone at transaction time.
Keep the onboarding controls that prove who your client is. Add a fast, possession-based check for the later call or message that asks your team to do something consequential.
What KYC and VOI tools do brilliantly
Build a reliable identity foundation.
KYC platforms, VOI providers and identity verification tools solve demanding onboarding problems. They can validate identity documents, compare biometrics, interrogate reliable data sources and support sanctions and politically exposed person screening. Those capabilities help firms establish identity, authority and customer risk with a level of rigour that an informal conversation cannot provide.
That foundation matters for the whole relationship. Good providers make checks consistent, reduce manual handling and produce evidence that supports the firm's own policy and regulatory program. Vericode does not replace any of it. It uses the trusted contact point created around that onboarding relationship when a different question appears later.
The day-41 interaction
A correct day-1 identity check does not authenticate every future caller.
A high-risk instruction arrives.
A caller changes bank details or requests sensitive information. The real client still exists and passed onboarding, but the immediate risk is who controls this interaction. Repeating identity evidence does not test possession of the trusted phone now.
“Day 41” is a memorable example, not a prescribed interval. The transaction-time layer belongs wherever a later interaction carries enough consequence to justify an independent check.
Side-by-side scope
Adjacent controls for different moments.
| Scope | KYC / VOI tools | Vericode |
|---|---|---|
| Primary job | Establish who a person or organisation is and support the firm's customer risk process. | Check whether the person in a consequential interaction controls the trusted phone number already held for the authorised contact. |
| When it happens | At onboarding, then again when policy, regulation or changed risk calls for a refresh. | At every high-risk interaction: for example, a changed payment destination, sensitive disclosure or unexpected representative. |
| What it checks | Identity documents, biometrics, databases and sanctions or politically exposed person screening, depending on the platform and program. | Possession of a pre-established trusted phone through an independently delivered challenge. |
| Frequency | One-off or periodic, with ongoing review shaped by the firm's risk-based process. | Event-driven throughout the relationship, whenever the consequence justifies a live check. |
| Evidence produced | Identity and onboarding evidence appropriate to the provider, checks selected and customer process. | A timestamped, hash-chained record of the authorised-contact check: requester, masked target, method and outcome. |
| Typical pricing model | Often billed per check or verification event at onboarding and review volumes; commercial models vary by provider. | A subscription with an included verification allowance. Current options are listed on the pricing page. |
Provider capabilities and commercial models vary. See Vericode's current subscription options on the pricing page.
Recommended architecture · Use both
Identity at the entrance. Possession at the moment of risk.
Treat KYC or VOI as the identity foundation and Vericode as a transaction-time control that draws on the trusted relationship. The layers reinforce each other without asking either product category to perform the other's job.
- 01
KYC / VOI at onboarding
Establish identity, authority and customer risk using the documents, biometrics, databases and screening appropriate to the engagement.
- 02
Maintain the relationship
Keep customer information and risk current. Record a trusted phone number through an independently controlled source before a suspicious request arrives.
- 03
Vericode at the high-risk event
Challenge possession of that trusted phone during the live interaction, record the outcome, then apply the firm's existing approval and escalation controls.
Verification evidence, not client files
Keep the evidence boundary clear.
Vericode does not require identity documents, biometric templates or matter-file uploads. It stores the verification metadata needed for the authorised-contact check, including recipient details, message and provider metadata, timestamps, actors, outcomes and audit events.
Each authorised-contact check creates a timestamped, hash-chained record: who requested it, the masked target, method and outcome. Compliance-authorised users can export the record as PDF or CSV.
Add the transaction-time layer
Keep KYC and VOI. Close the interaction gap around high-risk requests.
See the possession challenge in practice, or read the fuller CDD vs caller verification explainer for the regulatory context and worked examples.