DefCrypt — Crypto Exchange Verification Failed: What to Fix in KYC

When crypto exchange verification fails, the system or reviewer has rejected a particular document, image, or data match. Verification compares your identity with a government-issued document and often a live selfie. This differs from a risk-control hold after a deposit or a Source of Funds request, which concerns the origin of assets rather than photographing an identity document correctly.

Major platforms publish similar rejection reasons: failed facial liveness checks, an invalid or expired ID, blur or glare, an incomplete frame, a screenshot instead of the original document, or another account already verified with the same identity. Bybit and OKX list these reasons in their help centers. Follow the wording shown in your own account rather than advice from chat groups.

Also check the KYC level. An inability to withdraw a large amount may mean the account requires the next verification level rather than that verification is broken. For the broader context behind account restrictions, see the top exchange-freeze reasons.

Document. Use the original, in color: a passport, national ID, residence permit, or driver's license, but only if it appears on the verification screen's accepted list. An expired document, a visa instead of an ID, a black-and-white copy, a photo of a screen, or a screenshot will usually be rejected. Keep all four corners in the frame and make the full name, date of birth, document number, and expiry date readable.

Lighting and framing. Use even light from the front, without a bright window behind you or flash reflected from a laminated surface. Place the document on a contrasting surface and hold the phone parallel to it rather than shooting at an angle. Do not cover fields with your fingers. For a facial check, center your face in the oval, remove glasses, hats, and masks, and follow movement prompts slowly. The exchange's mobile app camera is often more reliable than a browser webcam.

Data mismatch. The full name, including any patronymic or middle name, date of birth, and issuing country must match the profile exactly. Transliteration as shown in a passport may differ from a separate translation and is a common source of mismatch. If the profile was saved with an error, ask official support to correct it instead of making a tenth attempt with the same incorrect name. If the rejection concerns the origin of assets rather than identity, see Source of Funds.

1. Save the rejection reason shown in the account and email as both a screenshot and copied text.
2. Compare the full name, date of birth, and document number with the profile character by character.
3. Prepare a current original document from the accepted list on the verification screen.
4. Photograph it again in good light, in color, with all corners visible, no glare, and no cropping.
5. Complete the facial check in the exchange app rather than through an arbitrary browser flow.
6. Submit one attempt. Do not send five different documents in quick succession; some systems may move the case to manual review or impose a temporary pause.

The order is straightforward: correct the KYC submission first, then open a ticket. If three careful attempts with corrected lighting and data produce the same generic rejection, contact support and include a screenshot of the reason, the document type, the issuing country, and what you already corrected.

Contact support when the account shows no readable reason, you cannot correct profile data yourself, the document was accepted but the status remains pending longer than the usual processing time, or the system reports a duplicate identity even though you have only one account. Keep the message concise: date of the attempt, rejection code or text, what you corrected, and the document used. Demands for an urgent unlock and threats in the ticket generally do not accelerate review.

• Never send a seed phrase, private key, or unrelated identity documents "just in case."
• Do not repeat five attempts with the same poor images; correct the lighting, framing, and data first.
• Do not confuse a KYC rejection with a withdrawal hold after a deposit; they are different problems.
• Do not give documents to third-party "helpers" in chat groups; use only the account's official channel.

If verification has passed but withdrawals remain paused, the cause may be an AML review, SoF request, P2P dispute, or security hold. Prepare an evidence package for the official ticket and follow the exchange-unfreezing process. For a platform-specific example, see first steps after a Bybit withdrawal freeze. The outcome is not guaranteed because platform and KYC-vendor policies differ.