CDK activation failed: five causes, ranked by likelihood

Nine out of ten failures are a truncated copy, a wrong network, or an API key pasted where the Organization ID belongs.

First, the flow: after payment you get an order number and a code that serves as your order record. Nothing is redeemed on the vendor site — there is no redemption page — because activation is done by a person against the account identifier you supply. So most failures below are not about the code itself; they are about the identifier, the network, and the order state.

1. An incomplete copy

The most common by far. Organization IDs contain dashes and lowercase letters, and selecting them by hand from a chat window truncates the tail. The symptom is a format error, or a reference that cannot be found.

Fix: go back to the settings page, use the copy button rather than selecting by hand, and count the length after pasting. Typing one by hand fails more often than feels plausible.

2. The wrong identifier

Claude needs the Organization ID, from Settings, then Account, beginning org_. Many people hand over an API key instead, which begins sk-ant-. Nothing says "wrong field type" — it just fails, or activates in a workspace you did not intend. For ChatGPT the required input is a session token taken from the official page, and it is likewise not a password.

Worth repeating: an API key is billing plumbing. It is not an account identifier, and a subscription on your account does not travel with it.

3. Wrong network or amount

Payment problems leave the order at "pending", which looks like a failed activation but is a failed payment. Three typical shapes: the wrong chain, when the invoice said TRON and you sent ERC20; an amount off by cents; or a wallet that deducted the network fee from the transfer. One invoice means one network and one amount, and splitting a payment across two transfers lands here too.

Fix: check whether the order still says pending; if it does, find the transaction hash and follow the reconciliation path instead of the activation path.

4. The account itself is conditioned

A minority of accounts already hold the same tier, or are restricted or in appeal, or sit behind an organisational policy that blocks changes. This only surfaces after submission.

Fix: confirm in the browser that the account logs in normally and its subscription page looks healthy, screenshot that state, then contact support.

5. The same identifier submitted twice

Less frequent but real: the same order resubmitted, or an identifier from a previous account pasted into this one. The symptom is orders overwriting each other, or a message that a request is already in progress.

Fix: do not place a second order. A second payment does not speed up the first; it makes the explanation harder, because two pending orders are worse than one.

The order to debug in

1. Check the order status — pending or paid. This decides what to look at next.
2. If paid, verify the Organization ID prefix, length and the page it came from.
3. Confirm the account is healthy in the browser and not restricted.
4. Look the order number up on the status page
5. If still nothing, message @cdkstorebot with the order number, the transaction hash and a screenshot of the identifier prefix. English or Chinese both work.

What the identifier actually is: the Organization ID guide. Why a correct payment sits unmatched: payment not matched. Rules on money back: the refund policy.

Common questions

Back to plans →