Core Concepts
Key concepts for understanding the VerifiMe platform
VerifiMe is an identity verification and risk assessment platform. Before integrating, developers need to understand these key concepts:
VerifiMe Wallet
Every customer who verifies through VerifiMe gets a VerifiMe Wallet. The wallet holds their verified identity credentials. Key points:
- A wallet can contain multiple identity types (individual + organisations)
- Individual identity is always required as the foundation
- Organisation identities are optional and linked to the individual
- Customers can share their verified credentials with multiple service providers
Identity Types
VerifiMe supports five identity types. See Identity Types for details:
- Individual
- Company (Private or Public)
- Trust (SMSF, Regulated, Unregulated)
- Partnership
- Sole Trader
Client Organisations
A client organisation is your business as registered in VerifiMe. See Client Organisations for details. Each client organisation has independent configuration, risk rules, and organisation codes.
Permissions
VerifiMe uses an explicit permission model. A client organisation must request permission from a customer before accessing their risk assessment data. The customer must grant consent. This protects customer privacy whilst enabling compliance checks.
Key Terminology
| Term | Definition |
|---|---|
| Wallet Holder | A customer with a VerifiMe account |
| Tracking Reference | UUID tracking a customer's verification session |
| Organisation Code | Unique code for your client organisation, used in API calls |
| Risk Assessment | Automated evaluation based on your configured rules |
| DVS | Document Verification Service - government database checks |