Skip to content

Claude 4.5 / 4.6 Phone Verification 2026: Virtual Number Setup + ID Policy

Need quick verification codes? Start your verification journey now

Start Now

Why Claude verification matters more in 2026

Since Claude Opus 4.7 launched in May 2026, Anthropic has tightened account-level controls. Phone verification remains the entry gate for new accounts, but a new identity verification layer (Persona Identities, live selfie + government ID) now sits behind capability-specific triggers. This guide walks through the virtual-number signup path that still works, the country ranges with the highest pass rates, and what to prepare for the identity verification step that may follow.

Get a high-success Claude verification number on SMS-Act →

How Claude's Phone Verification Works in 2026

Claude's signup verification runs as a three-step pipeline:

  1. Carrier lookup — the entered phone number is checked against Anthropic's anti-abuse database. Numbers resolving to VoIP-flagged ranges, recycled-number pools linked to previously banned Claude accounts, or low-reputation ranges are rejected immediately with "this phone number cannot be used for verification".
  2. IP-region consistency — Claude compares the number's country code against the device's IP geolocation. Significant mismatches (e.g., a US number requested from a Vietnam IP) silently never receive the SMS, even though the request appears to succeed.
  3. Capability-based identity flag — added in April 2026. If the new account immediately requests access to specific features (API key generation, Claude Cowork, Workspaces, or other capabilities Anthropic specifies), the account is flagged for the separate identity verification flow described below.

Steps 1 and 2 are familiar — they match the pattern Google, OpenAI, and other strict platforms use. Step 3 is Claude-specific and is what makes Claude verification different from a generic platform signup.

Anthropic's April 2026 Identity Verification Policy

On 2026-04-15 Anthropic updated its Help Center with a new identity verification policy. The trigger conditions, per the official documentation:

  • Accessing specific capabilities (varies by account)
  • Routine integrity checks
  • Safety or compliance requirements

The verification itself runs through Persona Identities (third-party identity provider) and requires:

RequirementDetail
Government-issued IDPhysical, valid, non-expired. Passport, driver's license, or national ID card. Photocopies, digital IDs, and temporary paper IDs are not accepted.
Live selfieA camera-equipped device for a real-time selfie. Typically completes in under 5 minutes.
Data handlingPersona holds the ID and selfie, encrypted in transit and at rest. Anthropic does not store the documents and the data is not used for model training.

Anthropic's published rationale: "Being responsible with powerful technology starts with knowing who is using it. Identity verification helps us prevent abuse, enforce our usage policies, and comply with legal obligations."

Implication for SMS-verified accounts: phone verification gets you in. The identity verification gate may surface later when you use specific capabilities, perform routine review-triggered re-verification, or trigger Claude's risk engine. Accounts unable to complete identity verification at that point can lose access to gated capabilities (in some cases the whole account).

Practical recommendation: Sign up via virtual number now to get the account active, then have a physical government-issued ID prepared if and when Claude triggers the identity flow. Do not delay signup waiting for "more clarity" — early accounts get more leeway in capability access patterns.

Country Selection: Best Virtual Numbers for Claude

Pass rates differ sharply by country range. Based on SMS-Act order log Q1 2026 for Claude verification specifically:

CountryRange typeFirst-attempt pass rateNotes
United KingdomMobile (EE / O2 / Vodafone range)~92%Highest pass rate; pairs well with EU/UK IP for IP-region consistency
GermanyMobile (Telekom / Vodafone DE range)~90%Equivalent to UK; cleaner stock for new accounts
IndonesiaMobile (Telkomsel / Indosat range)~88%Surprisingly tolerant; good fallback when UK/DE pool depleted
FranceMobile (Orange / SFR range)~85%Reliable; mid-size stock
IsraelMobile (Cellcom / Partner range)~85%Niche but stable for Claude specifically
United StatesMobile (T-Mobile / Verizon range)~80%Works but requires US IP for IP-region consistency; otherwise gate 2 silently blocks
CanadaMobile (Rogers / Bell range)~78%Equivalent to US; smaller stock
RussiaMobile (МТС / Билайн range)~50%Often pushed to identity verification immediately; avoid for new accounts

The UK/DE/ID/FR/IL ranking is Claude-specific and differs from the Google or OpenAI tables because Anthropic's risk model weights certain ranges differently. Avoid using a Russian or Iranian number on Claude — they trigger identity verification on first request even before any capability access.

For country selection across other AI services, see International phone numbers for verification.

Common Verification Errors & Fixes

Error / symptomUnderlying causeAction
"This phone number cannot be used" immediatelyGate 1: carrier blacklistCancel order, switch to UK / DE / ID mobile range
No SMS arrives, no errorGate 2: IP-region mismatchUse VPN matching number country (UK number → UK exit node)
"Verification failed" after entering codeCode expired (>10 min) or entered wrongRequest fresh code; SMS-Act number still valid for 15 min
Identity verification appears immediately after phone verificationGate 3: account already flagged at signupCannot bypass with a different number; prepare physical government ID
Code arrives 5+ minutes lateCarrier delaySwitch sub-range; late codes are often already expired
Account banned within 24h of signupBehavior pattern flaggedReduce automation, use single-account-per-IP, do not generate API key immediately
"Too many attempts"Rate-limit triggeredWait 30 minutes, clear cookies, fresh IP

The most common Claude-specific surprise is gate-3 immediately requesting identity verification. This is not about the phone number — it's a server-side risk classification on the IP + browser fingerprint + signup pattern. Switching numbers does not help.

Step-by-Step: Claude 4.5 / 4.6 Verification

Step 1 — Prepare SMS-Act and Claude

  1. Open SMS-Act and sign in.
  2. Top up at least 30 credits (≈ 3-4 attempts) — Claude's identity flow occasionally requires a country switch.
  3. Decide on the IP / region setup: if using a UK number, prepare a UK residential VPN or actual UK IP. IP-region consistency is the highest-impact lever.

Step 2 — Acquire the number

  1. Search Claude or Anthropic in the SMS-Act activation list.
  2. Pick a country from the table above — UK / Germany / Indonesia recommended for first attempt.
  3. Confirm the purchase. The number arrives with a 15-minute countdown.

Step 3 — Submit to Claude

  1. Open claude.ai (with VPN in place if needed) and start signup.
  2. Choose phone verification (not Google / GitHub sign-in — those skip the SMS path).
  3. Paste the SMS-Act number in full E.164 format with country code.
  4. Request the code on Claude.
  5. Return to SMS-Act order page; the code appears typically under 30 seconds.
  6. Enter the code in Claude to complete phone verification.

Step 4 — Lock the account (mandatory before any capability access)

The SMS-Act number expires in 15 minutes, so it is not usable for recovery later. Right after verification:

  1. Set a strong, unique password.
  2. Enable 2FA — use Google Authenticator or Authy, not SMS.
  3. Add a recovery email (different from any other Claude account).
  4. Wait at least 24 hours before any heavy capability use — early activity patterns disproportionately influence Claude's risk classification.

Step 5 — Prepare for identity verification

If your use case may trigger gate 3 (API key generation, Claude Cowork access, certain capabilities):

  1. Have a physical government-issued photo ID ready (passport / driver's license / national ID).
  2. Use a device with a camera.
  3. When Claude requests identity verification, complete it within 24 hours — delaying can result in capability throttling.

FAQ

Q1: Can I use Claude with only phone verification, no identity verification? For most general chat usage, yes. Identity verification is gated on specific capabilities (API key generation, certain higher-tier features). If you only need standard Claude chat, phone verification is sufficient. As capabilities you access grow, identity verification probability increases.

Q2: My SMS-Act number expired. How do I recover my Claude account? Use the email recovery flow + 2FA app. The SMS-Act number is single-use and was only valid for the 15-minute signup window. Do not buy a new SMS-Act number trying to re-verify the same Claude account — it will not work because the new number is not the one Claude has on file.

Q3: Will my Claude account be banned if Anthropic detects a virtual number was used? There is no automatic ban tied to the use of a virtual number itself. The factor that increases ban risk is behavior pattern post-signup: rapid API key generation, automation patterns, IP rotation, multi-account creation. Use the account like a normal user, complete recovery setup, and bans are not pattern-driven.

Q4: What is the cheapest country for Claude verification? The 8 credits per verification is uniform across countries in SMS-Act. The cheapest path is therefore the country with the highest pass rate (fewer retries) — UK or Germany based on Q1 2026 data.

Q5: I'm in a country Claude does not serve. Can SMS-Act still verify me? SMS-Act can provide a number from a Claude-supported country, but Claude's IP-region consistency check will reject the signup if your IP is from an unsupported country. You need both: a UK number AND a UK IP. The number alone is not sufficient.

Q6: How does identity verification handle non-English IDs? Persona Identities supports IDs in most major languages. The selfie + ID match check works on facial features, not text. Non-English passports (Chinese, Japanese, Russian, Arabic, etc.) are accepted as long as they are physical, valid, government-issued.

Disclaimer

This platform is designed to support development testing, business verification, and international service scenarios, helping users complete processes in a reasonable and compliant manner.

Users are expected to ensure that their use of the service complies with applicable laws, regulations, and the policies of third-party platforms. The platform does not participate in or control how the service is used.

Accounts associated with abnormal or improper usage may be subject to restrictions in accordance with platform policies.

Users must be at least 18 years old and acknowledge that they are fully responsible for their own use and any resulting outcomes. If you do not agree with these terms, please discontinue use of the service.

Ready to sign up before Opus 4.7 onboarding capacity tightens? Open SMS-Act and grab a UK or Germany Claude verification number → — failed attempts auto-refund 8 credits.

SMS-Act - Global Leading Online SMS Verification Platform