查看中文版 →

Deutsche Version ansehen →

Открыть русскую версию →

Ver versión en español →

Log inChoose a plan
Blog · Setup guides

Claude Code popped up Verification Portal? Understand the risk control first

Your terminal stops mid-session with API Error: 400 Identity verification is required, or your browser redirects to portal.anthropic.com for a physical ID and live selfie. With the updated Supported Regions Policy taking effect on November 12, this Persona-backed check is driving a much stricter enforcement wave.

You are halfway through a refactor when Claude Code stops and prints a red error in your terminal:

API Error: 400 Identity verification is required to continue

Or you open claude.ai to upgrade to Claude Pro or Max and your browser redirects to portal.anthropic.com, asking you to complete an identity check within minutes.

The short version: Verification Portal is not a routine CAPTCHA. It is a mandatory compliance check handled by Persona Identities. In the first half of 2026, Anthropic banned 11.4 million accounts and overturned only about 10.5% of appeals. If your daily work depends on Claude Code, the real fix is decoupling your workflow from personal account risk controls rather than trying to game the check.

11.4 million bans in six months: what changed

Anthropic's enforcement focus has shifted sharply from basic bot filtering to regional compliance, anti-reselling, and anti-distillation. Data from the Anthropic Transparency Hub shows how steep the jump is:

Anthropic account bans and appeal outcomes
Reporting periodBanned accountsAppeals receivedAppeals overturned
H2 20251.45M—~3.3%
H1 2026 (Jan–Jun)11.4M398,00042,000 (~10.5%)

Ban volume multiplied nearly eightfold in six months. Then, announced on October 8 and taking full effect on November 12, Anthropic raised the bar again with an updated Usage Policy and Supported Regions Policy:

  • Three regional red lines (allowlist model): Only 185 countries and territories are supported; mainland China, Hong Kong, Macau, and Russia are excluded. The policy now enforces all three constraints at once: the user must be physically located in a supported region, the company's registration and headquarters must be in a supported region, and any entity majority-owned or controlled (directly or indirectly) by persons or entities in unsupported regions is prohibited even if incorporated elsewhere.
  • 30-day multi-signal telemetry: Enforcement no longer relies on a single login IP. The system retains 30 days of security monitoring data and scores accounts across request timezones, language signals, multi-account concurrency, browser fingerprints, and payment methods.
  • Routine Persona KYC: Whenever those signals or a subscription upgrade cross a risk threshold, Verification Portal steps in as a hard gate.

How Verification Portal triggers and what Persona checks

The Permissions-Policy header on portal.anthropic.com explicitly grants camera access to withpersona.com (inquiry.withpersona.com, verify.withpersona.com). Anthropic outsources the entire verification flow to Persona Identities, a San Francisco-based KYC provider.

Based on Anthropic's support documentation and developer reports, five signals commonly trigger the prompt:

  1. Network and IP anomalies: Flagged datacenter IPs, shared proxy nodes, or rapid IP jumps across regions.
  2. Payment risk flags: Virtual cards heavily flagged by Stripe during Claude Pro or Max checkout.
  3. Device and environment mismatches: Concurrent logins across mismatched device fingerprints, or local timezone and language settings conflicting with the connection IP.
  4. High-frequency or automated patterns: Long, high-concurrency Claude Code runs or unapproved automation scripts.
  5. Account and billing transitions: Upgrading to Pro or Max, or switching organization and workspace permissions.

Once you enter Verification Portal, the requirements are much stricter than phone verification:

  • Individuals: An unexpired, physical, government-issued photo ID (passport, driver's license, or national ID card) plus a live selfie via phone or webcam. Scans, photocopies, screenshots, and digital IDs are rejected.
  • Organizations: Legal business name, address, and registration number, alongside a representative's physical photo ID and live selfie.

Anthropic's documentation states that verification data is used strictly for identity confirmation, fraud prevention, and compliance, not model training. However, Persona collects and processes the raw images and biometric data, and Anthropic retains access to records for appeals and compliance reviews.

Why verified accounts still get banned

Across r/ClaudeAI, r/ClaudeCode, and tech press reports, the loudest complaint is not the check itself, but getting banned right after completing it.

Three failure modes come up repeatedly:

  • Banned minutes after verifying: Paying Pro and Max subscribers upload their passport and selfie, only to receive a permanent termination notice seconds or minutes later. Often the document was issued by an unsupported jurisdiction (even if the user legally resides in a supported country), or prior IP and billing signals had already flagged the account, leaving KYC as a final confirmation step.
  • Stuck in a verification loop: Selecting the wrong country with no back button, repeated prompts for a second ID, or passing in the browser while Claude Code stays stuck on API Error: 400 Identity verification is required—even after running claude logout, deleting ~/.claude/credentials.json, and logging back in.
  • Slow support queues: Restricted-account appeals frequently sit unanswered for weeks or close with templated replies, leaving only a brief window to export chat history while remaining subscription fees go unrefunded.

From Anthropic's perspective, cracking down on account farms, regional arbitrage, and unauthorized distillation makes sense. For working developers, though, an automated pipeline with a ~10.5% appeal overturn rate turns a personal subscription into a fragile single point of failure.

Three ways forward if you rely on Claude Code

Once API Error: 400 Identity verification is required shows up, you have three practical options:

  • Go through official verification and native setup: If you hold a passport from a supported region, use a clean residential IP, and pay with a local bank card, complete Persona in your browser, run claude logout, clear ~/.claude/credentials.json, and claude login again. If the account is already suspended, expect roughly a one-in-ten chance on appeal.
  • Offload routine tasks to open models: If you have capable local hardware or mostly run simple completions and scripts, shifting part of your workload reduces single-vendor risk, though open models still lag on large multi-file refactors.
  • Switch to a compliant API or fixed-pass gateway: Claude Code only reads ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN. Pointing it at a provider that does not tie your CLI to a consumer subscription removes Persona KYC and personal account ban waves from your daily workflow.
Personal Claude subscription vs. CodingPass
ComparisonPersonal Claude Pro / MaxCodingPass (Go / Plus / Pro)
Personal Anthropic accountRequiredNot required
Verification Portal / Persona KYCEnforced when risk flags triggerNever triggered
Pricing and capsDynamic black-box limits; third-party apps use extra usageMetered at official API rates; public monthly, weekly, and 5-hour caps
Over-limit handlingCan trigger abuse flags or extra chargesBlocked before upstream with HTTP 429; no surprise bills
Tool compatibilityOfficial Claude Code / claude.aiNative support for Claude Code, OpenCode, and Codex

With CodingPass, all traffic runs through compliant enterprise API channels—no personal Anthropic account, no passport upload, and no live selfie. CodingPass Go costs $10 a month with a $60 monthly allowance that works directly with Claude Sonnet 5.5 (Plus and Pro add Opus 5.5 and Fable 5.2). Input, output, and cache reads are metered at official API rates, every 5-hour window and weekly cap is listed on Usage Limits, and hitting a cap returns HTTP 429 with the exact reset time instead of charging extra.

Switching takes two minutes and keeps your existing workflow intact:

  1. Create a key: Pick a plan in CodingPass, open Dashboard → Keys → New key, and copy your cp-live- key.

  2. Set two environment variables in ~/.zshrc or ~/.bashrc and open a new terminal:

    ~/.zshrc
    export ANTHROPIC_BASE_URL="https://codingpass.ai"export ANTHROPIC_AUTH_TOKEN="cp-live-…"
  3. Run Claude Code as usual:

    claude --model claude-sonnet-5-5

Even if your personal account still works today, keeping CodingPass configured as a fallback lets you swap one line and keep shipping if Verification Portal ever pops up mid-sprint.

Boarding

Keep your tools, stop betting on a personal account.

Point Claude Code at CodingPass. No personal Anthropic account, no Verification Portal. Two env vars, transparent metering, cancel anytime.

  • Request ID on every response
  • Full refund if you've used 5% or less
  • No surprise charges
Choose GoClaude Code guide

$10/mo until you cancel.