Skip to main content
The customers module covers the full investor lifecycle: creating customer records, verifying identities on-chain via the contract, sending KYC verification links, and bulk-synchronizing with your existing databases. 
const trusset = new TrussetClient({ apiKey: '...' })

// All customer operations live under trusset.customers
trusset.customers.manage    // CRUD, search, wallet linking
trusset.customers.identity  // On-chain verification and compliance checks
trusset.customers.idLinks   // KYC verification links via Sumsub
trusset.customers.sync      // Bulk import/export for database migration

​
Sub-modules

Management

Create, update, search, and archive customer records. Link wallets to pre-registered customers. Query by name, address, external ID, or reference key.

Identity Verification

Verify identities on-chain, check KYC status, run transfer compliance checks. Single and batch operations with full transaction receipts.

ID Links

Generate and manage Sumsub-powered KYC verification links. Send via email or SMS, track status, revoke or resend.

Database Sync

Bulk-import customer records from existing systems. Configurable conflict resolution, optional on-chain verification, progress tracking.

​
Typical integration flow

A bank onboarding existing customers onto tokenized assets typically follows this sequence:
1

Import existing customers

Use sync.importRecords to batch-import customer records from your core banking system, mapped by your internal customer ID (externalId). Customers without a wallet address receive a referenceKey for later linking.
2

Collect wallets and KYC

Send KYC verification links via idLinks.create to investors who need identity verification. Investors complete KYC through the hosted Sumsub flow and optionally connect a wallet.
3

Link wallets

For customers who already passed KYC in your system, use manage.linkWallet to associate their Ethereum address with their Trusset record.
4

Verify on-chain

Call identity.verify or identity.batchVerify to register verified identities on the IdentityRegistry contract. This enables compliant token transfers for those addresses.
5

Ongoing compliance

Use identity.canTransfer before token operations to check real-time compliance. Use identity.getStatus to monitor KYC expiry and on-chain state.