Exchange Verification Tiers: What Each Level Actually Unlocks

A tier is a schedule of permissions

The word “verified” sounds like a single state, but the useful way to read it is as a row in a table. Each row grants a set of features and a set of limits. The identity checks are the price of admission to the row; the row itself is what determines what the account can do.

Kraken’s verification pages make that explicit. The article says that verification status determines what features, products and funding limits are available on the account. It then describes three paths rather than a ladder of many levels: a verified individual account, a verified individual account with higher limits, and a business account.

The three paths

The middle path is not a different identity check so much as a different limit schedule. The page describes it as the highest verification level available for a personal account and lists two concrete benefits: further increasing deposit and withdrawal limits, and higher API limits. It also notes that the higher tier is not required to use Kraken Pro.

What actually changes between the individual tiers

The comparison table on Kraken’s page is the part worth reading closely. The cash deposit and withdrawal line is:

Those are the two numbers the page attaches to the tier difference. The other listed features — buying and selling crypto instantly, staking and rewards, margin trading, OTC desk access and derivatives trading — carry a check under both columns, with footnotes about eligibility and geographic restrictions.

The API key row is easy to overlook and often the real reason a team moves up. Sixteen keys is enough for a handful of services; twenty-five is a different budget for a desk that separates market data, order entry, reconciliation and reporting into distinct credentials. The tier is therefore an operational decision as well as a funding decision.

Both figures in that table are bands rather than exact values, and that is the point of the wording. “Less than $100,000 per month” tells a client where the boundary sits, not what their own ceiling is; the same is true of “more than”. The number that applies to an account appears in the account itself, and it can also depend on the funding method, the currency and the jurisdiction recorded in the file. Reading the table answers “how big is the difference”, not “what is my limit”.

What the key allowance is actually for

Sixteen keys sounds like a lot until a team writes down what each one does. A production desk typically needs a credential for market data, one for order entry, one for the reconciliation job that reads balances and fills, one for reporting, and one per environment or per strategy. Keys are also the first thing to leak, and a leaked key with withdrawal permission is a worse event than a leaked key that can only read.

That is why the allowance is better read as a security budget than as a throughput figure. The practices that make the extra keys worth having are not about count at all:

• One key per job, scoped to the minimum permissions it needs. A reconciliation job has no reason to hold order-entry rights, let alone withdrawal rights.
• An IP allowlist per key, where the venue supports it, so a leaked credential is not usable from anywhere.
• A rotation schedule, and a way to revoke a single key without stopping the trading system.
• Separation between the credential and the account structure, which is what sub-accounts and API key isolation is about: the sub-account limits blast radius, the key limits what the blast can do.

If a team is moving to the higher tier specifically for the API keys, the migration is worth planning as a permissions exercise — nine extra credentials is nine more things that need an owner, a scope and a review date.

The documents

Kraken’s requirements page lists the information it asks for. The table below groups the items by what they establish, rather than reproducing the page’s order:

The page marks several items as conditional. A proof of address and a face photo carry notes that they may or may not be required depending on country of residence and current regulatory requirements. Where an address cannot be confirmed automatically, the page says a face photo may be requested instead of a proof of address. The document requirements for verification page goes further into what counts as acceptable evidence for each item.

The pattern is that the exchange is building a file that answers four questions: who you are, where you are, whether you can legally use the service, and how to reach you. The occupation and tax fields are not decoration; they are the parts a regulator or a bank would ask about.

What a tier does not change

A verification tier does not change the market, the order book or the risk of a position. It also does not, on the pages read here, change the trading fee schedule. The tier table is about access and throughput: how much can move in and out per month, how many API credentials can exist, and which products are available.

That distinction matters when comparing venues. Two exchanges can both call an account “verified” while attaching very different limits to the word. The number that matters is the one next to the feature you actually use — a monthly cash limit, an API key count, a derivatives permission — not the label.

A limit is also not a speed. A tier that raises the monthly ceiling says nothing about how long a single withdrawal takes, because that delay comes from somewhere else entirely: the venue’s own review and the network’s block confirmations. The two-stage structure, and how to tell which stage a transfer is sitting in, is the subject of crypto withdrawal holds versus confirmations.

A practical reading order

1. Find the limit line for the feature you need. For most people that is the monthly cash deposit and withdrawal limit; for a team it may be the API key count.
2. Read the footnotes, not only the checks. Eligibility and geographic restrictions sit in footnotes under the feature rows, and they can remove a feature that the main table appears to grant.
3. Match the document list to your jurisdiction. The requirements page is explicit that some items vary by country and current rules.
4. Submit once. The pages warn about processing delays and ask clients not to send multiple requests.
5. Re-check after a move or a status change. A tier is tied to the facts in the file; a change of residence or entity can change which row applies.

The word “verified” is a shorthand for a row in a table. Reading the row — the limits, the footnotes and the documents — is what tells you what the account can actually do.

Risk note. The tier names, limits, features and document requirements in this article were re-read from Kraken’s verification help pages on 2026-10-30 and were unchanged from the 2026-10-26 reading. Other exchanges publish different schedules, and limits can change without notice. Nothing here is investment advice.