Sumsub verification failed.
“Rejected” is not an explanation.

Identity verification, under scrutiny · Sources checked September 11, 2026

Upload your ID. Look into the camera. Take another photo. Then: rejected. One obvious question remains unanswered: what went wrong, and what are you supposed to do next?

That is the question behind this article. Not every failed Sumsub check is a mistake. But calling something a security decision does not automatically make the experience acceptable. An identity-checking system should be judged on more than its ability to stop fraud. It also needs a workable path for real people who get stuck.

Sumsub complaints: reports from several countries

These are unverified user reports; countries are self-reported profile labels.

Source: Sumsub’s public review profile. These are complaints, not verified case findings.

Getting stuck between two support teams

In a NiceHash Reddit discussion, one participant described rejected address documents and being directed back to NiceHash after contacting Sumsub. That same person reported eventually withdrawing through account closure. Another participant said their first KYC attempt worked. Quoting only the angry part would leave out relevant outcomes.

A separate Tradeify thread describes a different problem: the author reported a verified status on Sumsub while the destination dashboard still showed incomplete KYC. In a later reply, the author said the issue took four days to resolve. The thread does not establish the technical cause. It also illustrates why not every problem associated with Sumsub is necessarily a rejection.

Does everyone dislike Sumsub? No.

G2’s professional reviews include positive experiences. In an April 29, 2026 review, a KYC team lead praised verification and fraud-prevention capabilities while criticizing the screening module’s reliance on external partners. A software buyer and a person stuck at an identity screen judge different parts of the experience. The buyer’s satisfaction does not erase the applicant’s frustration. The applicant’s frustration does not prove the entire product is broken.

Who actually decides when Sumsub verification fails?

Separate three things: your document, the technical check and the platform’s acceptance policy. An image may be unreadable. Information may not match. Or the platform may not accept that document type or applicant category in the first place. Those are different problems, even when the screen makes them look the same.

According to Sumsub’s official guidance on reporting verification issues, the platform you are joining manages its verification settings, final decision and appeals. Seeing Sumsub’s name on a screen therefore does not establish that Sumsub made every decision involved.

There is another side to that distinction. Sumsub’s own technical documentation describes automatic rejection when data cannot be recognized or does not match, and business-customer tools for manually reviewing certain rejected cases. So “human review is never possible” is not a sound blanket statement either. Having a review tool does not mean every platform offers it to every applicant, or that a particular application can be approved.

A person should not need to understand a software integration to find out why their identity check failed.

Three failures that “security” does not excuse

1. A result is being mistaken for an explanation

“Verification failed” tells you the outcome. It does not tell you what to do. If something can be corrected, a useful message should identify the next step. Asking someone to try again without explaining what needs to change can turn a security check into a guessing game.

This is not a demand to expose fraud-detection rules or confidential findings. A useful response can remain limited: the document type is not accepted; a required step is incomplete; or the next step is to request a review. These are our design recommendations, not a claim that every security detail must be disclosed.

2. The companies understand the handoff; the applicant does not

For the applicant, joining one service should come with an understandable route to help. Dividing responsibilities behind the scenes is reasonable. Making the customer discover that division through several unsuccessful support conversations is not a good experience.

Our criticism of Sumsub is that a verification product should help its customers deliver clear messages and workable escalation paths. Our criticism of the customer platform is just as direct: hiring a technology provider does not make your responsibility to answer the user disappear.

3. The real person who fails gets lost in the sales pitch

A large number on a software marketing page does not resolve an individual rejection. The applicant has an immediate question: what happens to my case? Speed matters, but so does the quality of the process when the easy path stops working.

We cannot calculate Sumsub’s false-rejection rate from the public material reviewed here. That would require a meaningful denominator, applicant characteristics, customer configurations and independently reviewed outcomes. A confident percentage without those inputs would be a slogan, not a research finding.

What to do after a failed Sumsub check

Before uploading again, identify the problem more precisely. The following is a route for legitimate troubleshooting and escalation, not a way to bypass identity checks or a promise of approval.

1. Record the message and the stage. Keep the date, platform name, exact error and case reference if available. Remove personal information before sharing any screenshot publicly.
2. Ask whether correction is possible or the decision is final. Sumsub’s rejection-label documentation distinguishes a label from the actual rejection type. Do not assume that every red message can be fixed with another photo.
3. Check whether the document type is accepted. The official identity-document guide explains that the customer platform’s settings affect acceptance. A document accepted by one service is not automatically acceptable to another.
4. Contact the platform about its account decision. Ask for the explanation it can provide and whether a review is available. Requesting human review is not the same as being entitled to a successful outcome.
5. Use Sumsub’s official help route for technical or data-processing concerns. Its Applicant Support contacts page lists a portal, live chat and support@sumsub.com. Technical assistance does not give Sumsub authority to override a platform’s acceptance policy.
6. Do not create a second, inconsistent identity. Do not borrow someone else’s details, alter documents to get through checks or share passwords and login codes with intermediaries. Keep a legitimate complaint separate from attempts to deceive the system.

A support message that asks useful questions

This does not guarantee a favourable answer. It turns a broad complaint into specific questions that can be followed up. Send identity documents only through a secure route confirmed by the service, not in a public comment thread.

If I am rejected, what happens to my ID and face data?

That is a reasonable question. A rejected application does not automatically mean its data is immediately deleted. The Sumsub Service privacy notice describes retention conditions and the business customer’s role. Retention and deletion depend on the processing context and applicable requirements. Ask the responsible party about the retention basis and the route for access or deletion requests; a general article cannot determine the answer for your individual case.

There is also a substantial difference between “I am worried about my data” and “this company sold my documents.” The first expresses a concern. The second is a serious allegation that needs evidence. This research provides no basis for alleging document sales, collusion or theft of users’ funds by Sumsub.

What businesses should test before choosing a KYC provider

Do not test only the perfect application. A useful evaluation also asks what happens when an applicant gets stuck. Using authorized test data, check:

• Can applicants see the main acceptance requirements before submitting information?
• Does the error message make sense to a nontechnical person?
• Does the verification result stay consistent with your own dashboard?
• Does the user know who will respond and where to follow up?
• Do you measure the outcome and handling time of substantiated appeals?

These are editorial recommendations, not laboratory scores for Sumsub. A system that produces a rejection quickly is not necessarily a system that manages a failed verification well.

Common questions about Sumsub rejections

Does Sumsub reject everyone?

No. The material in this article does not support that claim, and successful checks are reported too. Our criticism concerns specific complaints and the quality of explanations and follow-up, not a claim that every applicant fails.

Does a rejection mean my document was fake?

Not necessarily. A generic failure message does not establish the cause. The issue may concern the document, a verification stage or the platform’s requirements. Ask the responsible team for the explanation it can provide rather than drawing a conclusion from one word.

Why can one service accept me while another rejects me?

Acceptance requirements can differ. The Sumsub ID help guide itself separates verified documents from acceptance by a partner app. Sumsub ID is also not interchangeable with every customer’s KYC workflow.

Can someone guarantee that my rejection will be reversed?

Nothing in this research supports such a promise. Buying assistance does not transfer the platform’s decision-making authority to an intermediary. This article does not advertise guaranteed approval.

The bottom line: strict checks need not mean a confusing process

Asking for better verification is not asking for weaker security. A service can take fraud seriously while giving legitimate applicants understandable instructions and a clear route to follow up.

Here is our criticism in plain terms: if “rejected” is all a person receives after handing over highly sensitive information, the user experience has failed—even if there is a technical reason behind the decision. Fixing that experience is a shared responsibility. Sumsub should answer for its technology and messaging; the customer platform should own its decision and the handling of the case.