<\/p>\n
If your identity check came back with anything other than Approved<\/strong>, this article walks you through what each non-approved badge means, what’s likely going wrong, and exactly how to retry. Its companion is What identity verification checks (and why)<\/a>.<\/p>\n Open Below the badge the launcher form is still there, with the same Start verification<\/strong> button you used the first time. The note next to it says: “If [the provider] asks for another try, you can start a fresh session here again.”<\/em><\/p>\n <\/p>\n When the provider sends a reason, it appears verbatim under the badge \u2014 the exact wording is set by the verification partner (not by us) and may differ slightly from the summaries below. The eight buckets cover the vast majority of cases:<\/p>\n If the reason on your page doesn’t match any of the eight above, paste it into the support ticket and we’ll help you interpret it.<\/p>\n For all the non-approved states except Declined-with-fraud-flag<\/strong> and under-18<\/strong>, the path is the same: start a fresh session and try once more. Before you click Start verification<\/strong>, run this 60-second pre-check:<\/p>\n Then click Start verification<\/strong>. The badge will move from Not started<\/strong> \u2192 Started<\/strong> \u2192 Submitted<\/strong> \u2192 In review<\/strong> or directly to Approved<\/strong> within a few minutes for most cases.<\/p>\n There’s no hard cap on attempts from our side. Practically: if you fail three sessions in a row with the same reason<\/strong>, stop retrying and open a support ticket. Keep retrying with the same setup that just failed will produce the same fail.<\/p>\n If three sessions fail with different<\/em> reasons (one was a blurry photo, one was a document type, one was a selfie mismatch), it usually means the device or environment is the problem, not you \u2014 switch to a different device and retry once.<\/p>\n Open a ticket under Verification & onboarding<\/strong> at Contacting support<\/a> if any of these apply:<\/p>\n Include in your ticket:<\/p>\n Q: Will failed attempts charge me anything?<\/strong> Q: My friend used the same device and passed. Why didn’t I?<\/strong> Q: Can I appeal a Declined decision?<\/strong> Q: I changed my legal name. Will my old ID cause a fail?<\/strong> Q: What if I don’t have a passport, national ID, or driving licence?<\/strong> Q: I’m a non-EU resident with EU residency permit. Which do I use?<\/strong> Q: I keep getting “Error” before I even reach the camera step.<\/strong> Q: How long is the launcher form available before it gets disabled?<\/strong> For anything not covered above, open a ticket under Verification & onboarding<\/strong> at Contacting support<\/a>. Include the exact badge text, the verbatim “Reason:” line, the timestamp of your most recent attempt, and the device + browser combination. We typically respond within one working day.<\/p>\n1) Look at the badge first<\/h2>\n
https:\/\/staging.lewdden.com\/store-manager\/verification\/<\/code>. The status badge at the top of the page is the single source of truth \u2014 the message just under it tells you in plain English what to do next. The seven non-approved states are:<\/p>\n\n
2) The 8 most common rejection reasons (and how to fix each)<\/h2>\n
\n
3) How to retry \u2014 clean session checklist<\/h2>\n
\n
4) How many retries are too many?<\/h2>\n
5) When to wait, and when to act<\/h2>\n
\n
6) When support is the right next step<\/h2>\n
\n
\n
7) FAQ<\/h2>\n
\nNo. Verification sessions don’t cost the creator anything \u2014 only one needs to land in Approved<\/strong> for the gate to open.<\/p>\n
\nThe session matches you to your ID, not the device. The selfie \/ ID match is per-person \u2014 a different person on the same device will get a different result.<\/p>\n
\nYes \u2014 for human-review cases. Open a support ticket with the reason text and a one-line explanation of what you think went wrong. We can ask the provider to re-examine the session if there’s a clear factual error (e.g. they read your DOB wrong). For genuinely failed checks (blurry photo, mismatch, expired ID), the appeal path is just to retake and retry.<\/p>\n
\nUse the names exactly as they appear on the ID you’ll show. If your storefront has a stage name or a deadname concern, those live on your storefront profile \u2014 see Customising your store<\/a>. The verification check only matches against the ID itself.<\/p>\n
\nMost countries support multiple document types. If yours doesn’t, open a support ticket \u2014 in some cases we can route you through an alternate verification path with the provider.<\/p>\n
\nEither: your home-country passport or the EU residence permit. Try the passport first \u2014 it’s the most universally supported.<\/p>\n
\nThat’s almost always a browser permission issue. Check the camera and microphone permissions for lewdden.com (or the verification provider’s domain) in your browser settings. On macOS Safari and iOS, system Settings \u2192 Privacy \u2192 Camera \u2192 make sure the browser is allowed. After fixing, hard-reload the verification page (Cmd<\/kbd>\/Ctrl<\/kbd>+Shift<\/kbd>+R<\/kbd>) and try again.<\/p>\n
\nForever, in every state except Approved<\/strong>. As long as the badge is anything other than green, you can start another session.<\/p>\nNeed more help<\/h2>\n