If prediction market identity verification failed, record which stage failed before uploading anything again. Check the authenticated request, profile data, document support and validity, image quality, liveness step, eligibility, and manual-review status without altering evidence or disguising your location.

Key Takeaways

Confirm the verification prompt inside the official account.

Separate profile mismatch, document capture, liveness, eligibility, and manual review.

Submit only current, unedited evidence through the authenticated flow.

Preserve the error, timestamp, document type, and case reference before retrying.

Never send passwords, codes, private keys, or identity files to unofficial support.

Which stage broke if your prediction market identity verification failed?

Do not treat every rejection banner as the same problem. Record the exact message and stage shown in the official app or website.

Stage	Check	Evidence to preserve
Account details	Name, birth date, address, country	Entered fields and error text
Document selection	Type, issuer, expiry, support	Document type and instructions
Document capture	Edges, focus, glare, color	Unedited original and capture error
Face or liveness	Purpose, camera permission, prompts	Stage and failure code, not biometric copies
Eligibility	Age, residence, jurisdiction, product	Authenticated notice and applicable terms
Manual review	Submission accepted but undecided	Confirmation, case ID, displayed status

Kalshi's document-verification guide separates profile information, supported evidence, document images, and face capture in its named process.［1］ Its flow is an example, not a universal checklist or guarantee of approval.

How do you prove the request is genuine?

Close the email or message and open the venue through a known bookmark or installed app. Sign in and find the matching verification request. If no request appears, contact support from the authenticated help route rather than using the message link.

Look for misspelled domains, shortened URLs, attachments, urgent threats, payments, browser extensions, screen sharing, or requests to move to a private chat. A real-looking logo or accurate personal detail does not authenticate the sender.

Save the official request type, fields, deadline as displayed, status, and case number. Do not expand a narrow request into a larger disclosure. Ask official support to identify the minimum acceptable evidence and permitted redactions when instructions are unclear.

Do your profile and documents match?

Compare the legal name, birth date, residential address, nationality or residence fields, and document details. Use the venue's documented correction route for a genuine error. Do not create a second profile, change facts to match a document, or submit another person's evidence.

Kalshi lists identifying and account information required for its verification process.［2］ Another venue may ask for different fields based on entity, product, country, and law. The authenticated form controls what you should submit.

Use an accepted, unexpired document issued to you. Check whether the platform requires a passport, national identity card, driver's license, proof of address, or another item, and whether both sides are required. Do not digitally edit identity fields or crop away required edges.

Is the document image usable?

Place the original document on a plain surface under even light. Keep all required corners and machine-readable areas visible. Avoid glare, blur, shadows, fingers over data, extreme perspective, screenshots of scans, filters, compression artifacts, and unrelated documents in the frame.

Follow the official file-type and size instructions. Do not repeatedly upload altered versions to guess what the system wants. Record the first error, correct one identifiable issue, and retry only through the same authenticated flow.

If proof of address is requested, use an accepted recent document and follow the venue's redaction rules. Do not reveal unrelated transactions when a permitted, narrower document is available.

What should you check during liveness or face capture?

Read the purpose and permissions before enabling the camera. Use a device you control, close screen-sharing software, ensure the lens is clean, use even front lighting, and follow the live prompts without another person in frame. Never let someone else complete the check for you.

A liveness failure can be a capture problem rather than an identity decision. Preserve the stage and error code, but do not email biometric images unless an authenticated case explicitly provides an approved channel and scope.

If camera permission, browser support, or app version is the problem, use the venue's supported environment. Do not install an extension or remote-access tool suggested by an unsolicited helper.

Could eligibility or location be the real issue?

Identity approval and account eligibility are related but separate. A clear document cannot establish eligibility if the venue or product is unavailable for the reader's age, residence, physical location, or jurisdiction. Kalshi's individual sign-up guidance illustrates venue-specific eligibility checks.［4］

Do not use a VPN, proxy, remote desktop, borrowed address, or false residence to bypass a location or eligibility decision. Ask the venue to identify whether the failure concerns evidence quality, profile data, eligibility, or another review.

When uploading over an untrusted local network, AethoVPN can protect traffic between your device and the VPN server, but it cannot authenticate the venue, verify your identity, change residence or physical location, influence approval, or bypass eligibility. The venue still receives the information you submit and may record account, device, and connection signals.

Is the identity verification rejected or still under review?

A submitted package may enter manual review instead of failing. Kalshi describes a sign-up-under-review state and directs users to await or respond through the official process.［3］ Record the confirmation, submission time, displayed status, requested correction, and case ID.

Avoid opening duplicate cases or sending several different document sets unless instructed. If the displayed estimate passes, reply in the same authenticated case with the reference and ask which stage remains incomplete. Do not assume silence means rejection.

If the broader account becomes restricted, follow the prediction-market account restriction guide while keeping the verification evidence as a separate track.

What evidence should you send to support?

Prepare a minimal package:

Account email or user ID in the form the venue requests, not your password.
Failure stage, exact error, time and time zone, device, app or browser version.
Document type, issuing country, expiry status, and whether the front/back was requested.
Confirmation or case reference from the authenticated submission.
A concise statement of the expected result and observed result.

Keep unredacted originals privately. Ordinary troubleshooting screenshots should hide document numbers, full address, account balances, QR codes, and unrelated personal information. Never provide MFA codes, recovery codes, seed phrases, private keys, or remote access.

How should you manage retries and records?

Create one row for each attempt: time and time zone, device, app or browser version, document type, stage reached, exact error, and case number. Do not store identity images in a shared notes app or attach them to several tickets. Keep originals in controlled storage and delete temporary copies from shared scanners or computers when the approved process permits.

Change one known variable per retry. For example, correct glare without changing the document, or use a supported browser without changing profile data. If the error remains identical, stop repeating the same attempt and ask official support what evidence or environment it accepts.

Summary

Identify the failed stage before trying again.
Authenticate the request and follow only the official submission route.
Match truthful profile data with a supported, current, unedited document.
Correct capture or liveness conditions without altering identity evidence.
Separate rejection, eligibility, and manual review, then escalate with minimal records.

Frequently Asked Questions

Why was my identity document rejected?

Possible categories include unsupported type, expiry, profile mismatch, missing side, unreadable capture, incomplete fields, eligibility, or review. Only the authenticated error or support case can identify your reason.

Can I edit the photo to make it clearer?

Do not alter identity fields or use filters. Retake the original document under better light and follow the venue's exact capture instructions.

Is liveness the same as document verification?

No. Liveness checks whether a live person is present, while document verification evaluates identity evidence. A venue may require one or both.

Should I send my ID by email?

Use only the authenticated upload route or a channel explicitly documented in an official case. Do not send identity files to an unsolicited address or social account.

How long does manual review take?

There is no universal duration. Use the status and estimate displayed for your venue and case rather than another user's timeline.

Can I use another person's document?

No. Submit only truthful evidence issued to you. Borrowed identity or a replacement account can violate rules or law.

Can a VPN fix verification or eligibility?

No. It cannot verify identity, change residence or physical location, or override platform eligibility and compliance decisions.

What should I do after repeated capture failures?

Stop speculative retries, preserve the latest error, verify the supported device and document requirements, and contact authenticated support with the minimal evidence package.

Disclaimer: This article provides general privacy and security information, not legal, financial, investment, identity, or individualized platform advice. Verification, biometric processing, retention, eligibility, review rights, and remedies vary by venue, provider, product, jurisdiction, and current terms.

Sources:

Kalshi — Document Verification — https://help.kalshi.com/en/articles/15581140-document-verification-on-kalshi
Kalshi — What Information Is Required — https://help.kalshi.com/en/articles/13823782-what-information-is-required-to-verify-my-kalshi-account
Kalshi — Sign-up Under Review — https://help.kalshi.com/en/articles/13823779-sign-up-under-review
Kalshi — Signing Up as an Individual — https://help.kalshi.com/en/articles/13823778-signing-up-as-an-individual

Sources checked 12 September 2026.

Related articles:

Prediction Market Identity Verification Failed