November 2026 community data on Claude KYC: China passport results, Pro-to-Max triggers, iOS payments that never deliver, and the risks of paid KYC passing.
Since November 2026, two things about Claude have tightened at once: KYC verification now covers more ground, and subscriptions bought through iOS have become unreliable, both to attach and to deliver.
Drawing on Anthropic's official documentation, threads on linux.do, and feedback on X, a few conclusions hold up:
Stuck at any step? Ask support. Paid orders can also continue on the order page.
The community data here comes from linux.do polls and X posts and is an unofficial sample. Polls are self-selected, the sample is small, and survivorship bias applies. The percentages show direction only, not official probability.
According to Anthropic's Help Center article "Identity verification on Claude":
Anthropic also runs a Cyber Verification Program (CVP) for security professionals. It is not the same thing as KYC for ordinary Claude accounts, and the two should not be conflated.
The community calls the verification page "Portal KYC." Judging by recent polls and posts, the triggers look roughly like this:
| Scenario | Community feedback | Risk assessment |
|---|---|---|
| Newly registered account | Some are prompted instantly at signup; many are not | Medium; depends heavily on environment, IP, and email |
| Free to Pro | Some prompted instantly, others sail through | Medium-high; web card binding triggers it more easily |
| Pro to Max | The most concentrated feedback; many "get prompted the moment they tap upgrade" | High, especially upgrades from older accounts |
| Renewal | Some get prompted, some do not | Medium; it is not a one-time verification |
| Web card binding | Widely seen in the community as higher risk | High |
| iOS / Google Play subscription | Some never prompted, some prompted from day one | Medium-high; not a KYC-free channel |
| Older account suddenly prompted | Verification demanded out of the blue after a period of use | Medium; tied to recent risk controls |
Several sets of community poll data:
These numbers are not official probabilities, but they do point to one trend: web card binding carries higher risk, Pro to Max is the hardest-hit scenario, and store subscriptions do not fully avoid KYC.
This is the most disputed part right now.
On one side are plenty of "instant ban" reports: users say Portal KYC with a China passport gets them "instantly suspended"; others say they contacted several sellers, all of whom said Portal KYC cannot be passed; and some posts claim that everything seen that day on X and linux.do involving a China passport and Portal KYC ended in an instant suspension.
On the other side are counterexamples: one person's passport KYC was still alive after more than a month; another upgraded to Max via Apple in-app purchase with a China passport and had not been banned two hours later; someone else "passed easily" using a friend's passport.
Why the divergence? Community discussion points to several possible factors:
It is worth stressing: "a China passport always gets instantly suspended" is inaccurate, and "a China passport always passes" is equally inaccurate. No official country-level pass rate has been published, and community samples are small, so this is a risk reference only, never a promise.
Separately, according to Anthropic's list of supported countries and regions, mainland China is not supported, Hong Kong is not on the list either, and Taiwan is. Third-party articles likewise note that Persona's support for mainland China is limited. That means mainland users who are willing to verify compliantly may still run into regional restrictions at the verification entry point or in later use; the verification page is the final word.
Since November 2026, the iOS problem has shifted from "slow delivery" to "payment succeeds but the subscription cannot be bound to the Claude account." Community and X feedback mainly includes:
Apple charges successfully, Claude says the purchase cannot be added The typical message reads: "We were unable to add your purchase to your Claude account. We suggest canceling the subscription and requesting a refund from Apple." Posts on linux.do dated November 9–12 carried several similar reports: Apple charged successfully, Pro never arrived; tapping upgrade produced "you are already subscribed through the App Store"; the account kept showing Free and refreshing did nothing.
New iOS subscriptions have been tightened, and top-up resellers are delisting Feedback on X dated November 6 said that several top-up resellers had been delisting iOS Claude Pro since November 5, that new accounts "can barely get through Apple purchase at all," and that renewals of existing subscriptions were unaffected for now but should not be interrupted and re-ordered. Apple gift cards and card payments both failed to top up.
iOS requires KYC too, and subscriptions may not activate without it Community feedback: "You need to pass KYC, otherwise the subscription won't arrive — that is how the iOS channel mostly works now." Some paid without seeing a KYC prompt, only for identity verification to appear a while later; without KYC, a successful payment may keep showing Free.
Some sellers cite an experience-based threshold, but it is not an official rule One top-up reseller said the currently steadier condition is an account registered before 2026-09-15 that has already passed KYC; accounts that do not meet this are more likely to see the subscription fail to arrive. This comes from seller experience — Anthropic has published no such threshold.
Max upgrades tend to get stuck in Apple review A case from X on November 5: to activate Claude Max, every payment triggered Apple review; after waiting through two 72-hour rounds, buying again after approval still demanded review. The iOS problem is not just whether the subscription arrives, but also review delays on Apple's side.
iOS costs more, and regions and gift cards are unstable iOS subscriptions cost about 25%–30% more than the official website because of Apple's cut; Max 5x is about $125 and Max 20x about $250. Gift cards, regional price gaps, and the Apple ID region all affect delivery. Some users report gift cards "can no longer subscribe," while others can still open Pro — it is unstable at the moment.
Renewing an old subscription is not safe, only relatively steadier Current feedback: old subscriptions that auto-renew, are not actively canceled and re-ordered, and do not switch Apple IDs often run a lower risk than new Pro subscriptions, Max upgrades, and first purchases on new accounts — but that is not safety. The community has already seen a Pro auto-renewal hit KYC three days in, and accounts in use for over six months suddenly hit KYC mid-use; switching iOS accounts at renewal can also trigger verification. The steadier approach is not to cancel and re-order proactively, not to switch Apple IDs often, to confirm account status and payment method before renewal, and to be ready to be asked for verification at any moment.
Refunds only go through Apple, and some have been rejected iOS payments happen on Apple's side, and the platform cannot operate Apple refunds directly; when a subscription does not arrive, you can usually only provide the Apple ID used for payment and go to Apple yourself. There have also been recent reports of refunds being rejected.
For buyers: iOS is not a "KYC-free" channel, nor is it "pay and it arrives"; an old account is not the same as safe either. Before ordering, confirm the account's registration date, KYC status, and whether the paying Apple ID is under your control; new Pro subscriptions, Max upgrades, and first purchases on new accounts carry the highest risk.
For sellers: do not package iOS as a stable channel, and do not advertise "renewing an old subscription" as safe. After-sales terms should state clearly that "payment may succeed without delivery, KYC may be triggered, old accounts may also be asked to verify, and refunds go through Apple."
Some people in the community pay for "KYC passing" services, but from a risk standpoint this is not a stable long-term arrangement.
One user offered a detailed warning: Persona passes information about the verification process to Anthropic, including video recordings, ID images, how long the KYC took, the IP that initiated it, and whether verification had been done before. Anthropic can access this information; if the same person does KYC for several accounts, later checks may link them; and a KYC IP that differs from the usual login IP gets recorded as well.
In other words, KYC does not stick a "verified" label on an account; it binds the account to a real identity and to one specific verification event. After someone passes it for you, the account may still be asked to verify again during upgrades, renewals, or environment changes; and once identity, IP, or device stops lining up, the risk of a ban is actually higher.
So if you see claims like "KYC accounts are stable and never banned," "guaranteed KYC pass," or "permanent verification," treat them as marketing language, not anything you can verify.
If a verification page has already appeared:
First confirm whether you can verify compliantly. If you have a physical passport, driver's license, or ID card and can complete the selfie, follow the official process; if you cannot, do not keep submitting someone else's documents.
Do not keep paying while verification is pending. Some community members kept paying while "pending verification," which left both the order and the account status more tangled.
Store subscriptions go through store refunds. For Apple / Google Play subscriptions, try requesting a refund from the relevant store; web card-binding and top-up orders follow the site's refund policy — do not promise "refund guaranteed if banned."
Keep the evidence. Save order numbers, payment records, screenshots of the verification page, and email notices; when taking screenshots, mask sensitive details such as ID numbers and email addresses.
Do not retry repeatedly or switch IPs constantly. That can make risk assessment more complicated rather than speeding approval.
A reminder: "instant refund on ban" is no longer as common in community reports as it once was. Pending verification, suspended, and banned are different states with different refund paths; the specifics depend on the payment channel and account status.
If you are considering a Claude account that has already passed KYC, a ready-made account, or a paid top-up service, confirm these points first:
The same applies to sellers: packaging KYC accounts as a "stable, never banned" long-term solution may sell well in the short term but generates a large volume of after-sales disputes over time. The steadier approach is to state clearly that KYC status may change, bans are not covered, Max upgrades carry extra verification risk, and iOS payments may succeed without delivery.
Community feedback is polarized: most recent cases are instant suspension, but there are counterexamples where a passport passed and stayed alive for over a month. There is no official country-level pass rate, and no guarantee can be given.
No. Store subscriptions can change the payment risk path, but the community has seen Google Play trigger KYC from the start and Apple in-app purchases require KYC after a Max upgrade.
Not 100%, but community feedback puts it in the high-probability category, especially for upgrades from older accounts. Some get prompted the moment they tap upgrade; others do not, for now.
It can. Upgrades, renewals, environment changes, and payment-method changes may all trigger it again; KYC is not a one-time permanent pass.
First confirm the Apple subscription is valid and that you are signed in to the same Claude account used for payment; iOS may also require KYC right now, and the subscription may not activate without it. Refunds can only go through Apple.
The risk is very high. Persona records verification recordings, documents, IPs, duration, and other details; linked accounts and mismatched IPs can both surface in later checks.
Yes. Community reports include "a new ready-made account was banned the next day" and "bulk accounts from registration farms died en masse"; KYC is only one layer of risk control.
A failed verification is usually not a ban by itself, and you can retry; but violating the Usage Policy / ToS can lead to a separate ban — the two are not the same thing.
You can, but look clearly at KYC status, ban risk, and after-sales coverage. Do not treat it as a "permanently stable" account, and do not read "KYC passed" as "no more verification ever."
It may. The community has cases where auto-renewal prompted nothing, and reports of KYC three days after a Pro auto-renewal. Auto-renewal is relatively steadier than new subscriptions or upgrades, but it is not a safety promise; do not proactively cancel and re-order, and do not switch Apple IDs frequently.
This article is based on Anthropic's official documentation as of November 12, 2026, linux.do community threads, and feedback on X. Official policy, verification entry points, iOS subscription rules, and risk controls may all keep changing, and community polls reflect only a self-selected subset of users; they do not constitute official probabilities or service commitments.
If you are about to upgrade to Max, buy a KYC account, or are already dealing with pending verification, a ban, or an iOS non-delivery, the safest principle is this: first confirm whether you can verify compliantly, then decide whether to pay; do not treat "passing KYC for you" as a long-term solution, and do not treat an "iOS subscription" as a channel that skips verification and always delivers.