Re-onboarding from scratch
Every new product or channel makes an already-verified customer prove who they are all over again, from the first document scan.
The cost of starting over
A verified user, treated like a stranger
Most systems forget every customer the moment the session ends. The next login, the next product, the next high-value moment: each one restarts the full check, and that repetition is where good users walk away.
The document wall, twice
Re-uploading an ID is the single highest-friction step in onboarding, and legitimate users abandon rather than repeat it.
Over-verification
Treating known, low-risk customers like first-time strangers adds cost on every session and pushes genuine users toward a competitor.
0%
of consumers have abandoned a financial-services onboarding at least once
Signicat, 2022
0%
of legitimate users drop off because of verification friction
Incode customer data
How it works
The first check is the last hard one
A full document, biometric, and liveness check anchors the identity once. From then on, a returning user is recognized in seconds, and the full flow only comes back when risk demands it.
Two views, one return
What the user does, and what you see
The returning customer taps once and is on their way. Behind the glass, your team sees a recognized identity: scored, consented, and ready to reuse.
The experience
What reuse feels like for the user
The first visit earns trust; every visit after spends it. Each moment below is tuned so a known customer never has to start over.
-
Return with one selfie
A recognized user proves who they are with a single selfie: no ID, no re-typing.
-
Skip the document
The verified document on file is reused for returning users, never re-uploaded.
-
Consent on reuse
The user approves each share and controls exactly what a business receives.
-
On-device matching
Biometric matching can run on the user's device, so raw data never leaves it.
-
Step up only on risk
Low-risk returns stay one-tap; a risk signal escalates to the full check.
The payoff
Reuse compounds every metric
Cutting repeat onboarding down to a single selfie moves users through 11x faster and lifts completion: the certainty of the first check, without the friction on every one after.
0%
higher completion rates when returning users reuse a verified identity
Privacy by architecture
Reused as proof, never as data
Reuse works because identity travels as a verifiable proof, not as shared personal data. Privacy is the design, not a setting.
- Tokenized credentials The identity is reused as an encrypted, privacy-preserving credential. No raw biometric data travels with it.
- On-device options Biometric matching can run directly on the user's device, so sensitive data never has to leave it.
- Automated redaction PII is removed the moment it is no longer needed, minimizing what any business ever holds.
- Encrypted end to end All data is protected with 256-bit TLS in transit and at rest, under SOC 2 Type II certified handling.
256-bit
TLS encryption, end to end
SOC 2
Type II certified data handling
In the review dashboard
One returning user, seen from your console
When a verified customer comes back, the console recognizes the identity, reuses the checks already passed, and shows exactly where the trust came from.
Verified proof
Global banks, fintechs, and marketplaces onboard with Incode.
92%
of users complete verification on the first try.
4 of 5
top LATAM banks run on Incode
4.1B+
identity checks processed
200+
countries' documents supported
What is reusable identity?
Once a user completes a full verification on Incode, that trusted identity can be reused across services with their consent. A returning user proves who they are with a single selfie, no documents to resubmit, which cuts onboarding cost and drop-off at the same time.
How does a returning user re-verify?
They take a single selfie. It is matched against the biometric enrolled during the first full verification, confirming the same real person in seconds without repeating document capture or data entry.
Is reusable identity private?
Yes. The identity is reused as an encrypted, tokenized credential rather than shared personal data. Biometric matching can run on-device, data is protected with 256-bit TLS under SOC 2 Type II handling, and the user consents to every reuse.
What happens at high-risk moments?
A real-time policy engine steps up automatically. Low-risk returns stay a single selfie; when a signal warrants it, the session re-runs the full document and biometric check, so friction lands only where risk does.
How is this different from a one-time identity check?
A one-time check verifies a user and then forgets them; the next session starts from scratch. Reusable identity remembers the verified result, so genuine customers are recognized instantly while the full check is reserved for new users and risky sessions.
What's next
Verify once. Welcome them back forever.
See reusable identity recognize returning users in seconds, on your own flows.