What an identity check usually asks for, and what it never needs
The document plus live confirmation pattern, why it fails on the second pass, and the credential no service should request.
We do not run the vendor's identity check and we cannot read its rulebook. What follows is what the flow asks in most reported cases, what it does not ask, and the one line that never moves on our side of the counter.
What the flow usually asks
In most reported cases two things are requested, and the second is the one people misjudge:
- A document. A government-issued photo ID, photographed by the person who owns the account. Which fields appear depends on region and on what the automated first pass decided, so two people describing the same check will not describe it identically.
- A live confirmation. A selfie-style capture taken at that moment, sometimes with a movement asked for. It is not a second photo of the document. It is an attempt to prove that whoever holds the device matches the document.
Where an account already has payment history, a billing detail can appear as well. That would be a request about a card you already used, not something we ask for, and we would never ask for a full card number.
What it does not need from you
- Your password. A verification never requires anyone to sign in as you.
- A 2FA code or recovery codes. No identity check needs a live one-time code.
- A second identity. One account, one person, one document.
We do not create, buy, supply or sell documents, and nobody working on an order for us should offer to. The service is a human completing the vendor's own flow for an account you already own. It is not a substitute set of papers, and it is not a way to give an account someone else's identity.
Where these checks fail most often
The failures we are handed are usually boring rather than dramatic. A document photo with glare or a cropped edge. A name that does not match what the account was registered with. A live capture in poor light. A submission made from a device different from the one the account keeps being used on. And language: a form presented in a language you are not fluent in gets misread, and the mismatch tends to surface on the second pass rather than the first.
None of that is a rule we can state as certain. It is the shape of what reaches us after a self-attempt has already bounced.
Our side of the line
For the verification service we need the Organization ID and the order number. For a subscription activation we need the Organization ID, and for ChatGPT the session token from the account's own sign-in session, which expires on its own and is not a password. Anything starting with sk-ant- is an API key and belongs to none of these flows.
Anything else a person asks for, stop and check with us before answering. The verification listing states the inputs again in one line, and this guide shows where the Organization ID is displayed.
Common questions
Do you tell me exactly which documents to upload?
No. The fields shown depend on region and on the vendor's own review, and they differ between accounts. We describe what is commonly asked, not what will be asked in your case.
Will you ask for my password or a 2FA code?
Never. If someone claiming to be cdkstore asks for either, that is not us.
Do you supply documents?
No. We do not create, buy or sell documents. The service is a human working the vendor's own flow on your account.
Is the Organization ID sensitive?
It identifies the workspace a subscription applies to; it is not a login credential and cannot be used to sign in. Still, do not post it publicly.
Guides
All guides →Claude Max 5x vs 20x: which tier you actually need
The difference is not quality — it is how many times you can hit the wall before lunch. A practical way to size your plan.
How to pay for Claude from mainland China (2026)
Four routes, ranked by how often they actually work — and the two that quietly cost you the account.