KYC & Perpetual KYC

Verified Once, Forgotten Since

KYC is done carefully at onboarding and then left behind. The same customer opens a card, a loan and a business account, moves house and changes their email, and each product system holds its own version. The risk view stays frozen at the first check.

Customer Risk RatingWithout an identity layer
onboarding.kycPriya RamanVerified 2022 · low riskLow risk
cardsP. RamanNew address 2024 · not re-verifiedNot linked
business.accountsPriya Raman-IyerDirector, high-risk counterpartyNot linked

Low risk on file. The same customer now has a business account with a high-risk counterparty.

The Problem

KYC Goes Stale Between Reviews

Onboarding checks a customer at one moment, through one product. After that, the customer’s relationship grows in other systems: new products, new addresses, a married name, a business they direct. Each of those systems keys the customer differently.

Periodic reviews then work from the onboarding record and miss what changed elsewhere. Perpetual KYC is meant to fix this by reacting to change, but it can only react to changes it can attribute to the right customer.

The result is risk ratings that describe who the customer was, duplicate verification work when the same person onboards again for another product, and blind spots that auditors find before the bank does.

Frozen Risk Ratings

Ratings reflect the onboarding moment, not the customer’s current relationship.

Changes Lost In Other Systems

Address, name and role changes in product systems never reach the KYC profile.

Repeat Onboarding

Existing customers are verified again from scratch when they open a new product.

The Solution

Keep One Profile That Follows The Customer

Resolve every product relationship to the same customer, across onboarding, cards, lending, business banking and third-party data, and give the customer one stable ID that outlives any single product.

Then drive perpetual KYC from that profile. When a linked record changes, the change is attributed to the right customer, so reviews are triggered by real events and existing customers are recognized when they come back.

One Profile Over Time
Product systems3 records
onboarding.kycPriya RamanVerified 2022
cardsP. RamanNew address 2024
business.accountsPriya Raman-IyerDirector
Zingg
Resolved by Zingg1 entity
ZINGG_ID · 1d7f-a903Resolved
Priya Raman
onboarding.kyccardsbusiness.accounts

The risk rating can now be reviewed against everything the customer holds today.

One Customer, Every Product

Product records resolve to one customer, whatever name or address each uses.

Changes Trigger Reviews

Updates in any system reach the right customer profile.

Recognize Returning Customers

A known customer opening a new product is matched to their existing profile.

Where Zingg Sits

The Identity Layer Under Financial Crime

Zingg runs as a workload inside your data platform and gives every entity one persistent ZINGG_ID. Everything above it reads the same resolved entities.

Used by
BI & dashboardsAI agents & RAGOperational appsReverse ETLData science

Reads your tables in placeWrites golden records and ZINGG_ID backNo copies leave the platform

Your data platform
DatabricksSnowflakeMicrosoft FabricGCPAWS

The same layer powersCustomer Analytics & MarketingPrivacy & ComplianceSupply Chain & ProcurementProduct 360Master Data ManagementAI and Agentic Foundations

A Customer Profile That Stays Current

Names That Change

Learned matching handles married names, nicknames, transliterations and address changes.

Stable ZINGG_ID

The ZINGG_ID persists as the customer adds products and changes details.

Incremental Updates

New and changed records join the existing profile through the incremental flow, without a full rerun.

Audit-Ready Links

Every link between records shows the evidence behind it. Explainability

FAQ

KYC Questions

What does entity resolution add to KYC?

It links every product and system record to the same customer, so KYC reviews and risk ratings reflect the customer’s whole relationship, not just the onboarding record.

How does this support perpetual KYC?

Changes in any connected system are attributed to the right customer through the persistent ZINGG_ID, so reviews can be triggered by real changes instead of fixed schedules.

Does Zingg verify identity documents?

No. Zingg resolves records you already hold. Document and identity verification stay with your existing KYC providers.

Where does Zingg run?

Inside your data platform: Databricks, Snowflake, Microsoft Fabric, Google Cloud or AWS.

KYC That FollowsThe Customer

Resolve every product relationship to one customer profile in your own data platform.