Duplicate Account
Understanding and fixing this common KYC rejection
⚠️ What This Error Means
This error means the platform's verification system matched your ID, your face, or your device against an identity it already has on file for another account. It is a duplicate detection flag, not a document quality problem, so glare, blur, or lighting have nothing to do with it.
Most KYC providers run this check silently in the background of every single verification, whether you notice it or not. During your selfie step, the system converts your face into a numerical value called an embedding and compares it against every face already stored in that platform's database. If the similarity score crosses a set threshold, you get flagged, even if you have never knowingly used that platform before. Separately, the system also does an exact match on your document number, since a passport or driver's license number showing up twice is one of the strongest signals of a repeat applicant.
Device fingerprinting adds a third layer. Your phone or laptop leaves a signature made up of screen resolution, installed fonts, timezone, browser version, and dozens of other small technical details, and that signature persists even if you switch browsers or turn on a VPN. So if two accounts were verified from the same physical device, the system can connect them even when the names, emails, and photos look completely different on the surface. None of these three checks work alone. Providers typically only hard-block when at least two of them agree, which is why a similar name by itself rarely causes this, but a similar name plus a shared device usually does.
✅ How to Fix It
Almost every platform enforces one verified identity per person, so this cannot be resolved by retaking your photo or trying a different angle. Work through these steps in order instead of guessing.
- Stop resubmitting immediately. Uploading a new photo, switching phones, or trying incognito mode does not touch the underlying match, since the flag lives in the platform's database, not in your image file.
- Check whether you already have an account. Search your email for old sign-up confirmations, including any nicknames or spelling variations of your name, and try the account recovery or "forgot password" flow before assuming the system made an error.
- Contact platform support directly and in writing. Explain your exact situation, ask whether your identity is linked to a prior account, and request a manual review rather than resubmitting through the app again.
- Be ready to prove you are a distinct person. If a parent, sibling, or partner already verified an account on the same device, network, or address, tell support that upfront and offer your own government ID for a side by side check.
- Never open a second account to get around it. Registering again with slightly altered details while the first identity is flagged almost always makes the fraud score worse instead of clearing it.
🔍 Legitimate Reasons This Happens By Mistake
The same detection built to catch fraud also catches honest people in specific, predictable situations. Here are the ones that come up most often, and what actually works for each.
| Scenario | Why it triggers the flag | Realistic fix |
|---|---|---|
| Family sharing one device | Device fingerprinting sees the same laptop or phone verifying multiple identities, which is exactly the pattern used to catch one person opening several accounts. | Have each family member verify from their own phone if possible, and tell support plainly that the device is shared by more than one adult in the household. |
| A previously deleted or forgotten account | "Deleting" an account rarely erases the underlying identity record. Your face embedding and document number are often retained for compliance, so a new signup years later still matches the old one. | Search your inbox for any old confirmation email and use account recovery instead of registering fresh. Ask support to reactivate the old profile rather than create a second one. |
| A sibling or relative with a similar name | A matching or near-matching name is a weak signal on its own, but combined with a shared address or a facial similarity score between close relatives, it can be enough to trip the threshold. | Ask support to compare document numbers and date of birth, which should differ even when names and addresses overlap. This usually clears the flag faster than arguing about the name itself. |
| A new phone that inherited old browser data | Restoring a phone backup or syncing a browser profile can carry over cookies, saved logins, and session data tied to an old account onto what looks like a brand new device. | Clear the site's stored data and cookies for that domain, or try a fully separate browser profile, then contact support if the flag persists after that. |
Let Us Help You Fix This
Try our free AI analysis first, or let our experts fix it for you.
Frequently Asked Questions
Can sharing a family computer trigger a duplicate account flag?
Yes. Device fingerprinting looks at the hardware and browser signals of the device you verify from, not just your identity, so multiple family members verifying from the same laptop can look like one person opening several accounts. Using each person's own phone for the selfie and document steps usually avoids this.
What if I forgot I had an old account years ago?
This is one of the most common causes of this exact error. Your face and ID were already stored from the earlier signup, so the system correctly recognizes you, it just does not know you forgot. Search your email for old confirmations and try account recovery before contacting support.
Is one account per person a platform policy or a legal requirement?
It is mostly a platform policy driven by fraud and bonus abuse prevention, though it overlaps with real regulatory expectations around anti-money laundering and having one clear identity per customer. Very few laws state one account per person outright, but the underlying compliance pressure is genuine.
Will creating a second account to get around this make things worse?
Yes, almost always. A new account using slightly altered details while the original identity is already flagged is exactly the pattern fraud systems are tuned to catch, and it typically escalates a review instead of resolving it.
Can a sibling with a similar name cause this error on my own account?
It can contribute to a flag, but a similar name alone rarely triggers a block by itself since names are treated as a weak signal. It usually needs to be paired with something stronger like a shared device, shared address, or a facial similarity score to actually trip the system.