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.

Activation failures are almost never "the key is broken". Five causes, ranked by how often they actually happen.

1. An incomplete copy

The most common by far. Keys contain dashes, and copying from a chat window truncates them — usually the last block. The symptom is a format error or a reference that cannot be found.

Fix: go back to the purchase record, use the copy button rather than selecting by hand, and count the length after pasting.

2. The wrong identifier

Claude needs the Organization ID, which starts with org_. Many people paste an API key (sk-ant-) instead. It does not say "wrong field type" — it just fails, or activates somewhere you did not intend.

Fix: copy it again from settings; do not type it.

3. Wrong network or amount

Payment problems leave the order at "pending", which looks like a failed activation but is really a failed payment. Wrong chain, a slightly different amount, or fees deducted from the transfer all produce this.

Fix: check whether the order still says pending; if it does, find the transaction hash.

4. The account itself is restricted

A minority of accounts already hold the same tier, or are suspended, or cannot upgrade. This only surfaces after submission.

Fix: confirm the account state first, then contact support.

5. The key was already used

Rarest but real: resold or second-hand keys. The symptom is "already used" at submission.

The order to debug in

1. Check the order status — pending or paid
2. If paid, verify the Organization ID's format and source
3. If both are fine, look up the reference on the status page
4. If still nothing, contact support with the reference, order number and a screenshot

Do not place a second order. It does not speed up the first one; it only makes reconciliation harder.

Back to plans →