Google Voice Number for Verification in 2026: Which Apps Reject It and How to Fix Missing Codes

A Google Voice number for verification works on some services and fails silently on others, and the difference is rarely random. Google Voice is a virtual number, and many services that send one-time codes check what kind of number you entered before they send anything. This guide covers how that check works, which services tend to reject Google Voice, what a flagged number looks like, how to avoid reclamation, and how to fix missing codes.

It’s written for legitimate account verification, not for getting around fraud controls or bank identity checks. If a service says it doesn’t accept VoIP numbers, use a different verification method, not a workaround.

Why a Google Voice number for verification sometimes never gets its code

The common mistake is treating a missing code as a glitch and hitting resend five times. Most failures fall into one of three buckets, and each has a different fix.

Failure 1 — The service refuses VoIP before it sends. A line-type lookup sees a virtual number, and the service shows an error or never sends the code. Nothing you change inside Google Voice alters that.

Failure 2 — The sender won’t reach Google Voice. Many banks and payment apps send codes from 5- or 6-digit short codes, and Google’s help center says some websites, such as banks, won’t send texts to Google Voice numbers. That is the sender’s decision.

Failure 3 — The problem is your Voice account. The number is still waiting on identity verification, it has been reclaimed, you’re signed into a different Google account, or the text landed somewhere you didn’t look.

Identify the bucket before you change anything.

How apps detect VoIP numbers

Line-type lookups. Before sending a code, a service can query a phone-intelligence API for the carrier and line type. Twilio’s Lookup Line Type Intelligence sorts numbers into 12 line types, including mobile, landline, fixed VoIP and non-fixed VoIP, and names Google Voice as its example of non-fixed VoIP: an online virtual number with no physical device requirement. A 2022 Twilio blog post recommends filtering them out of SMS one-time-password flows because they correlate with bots.

Number-intelligence databases. Fraud-prevention vendors keep their own classifications. IPQualityScore says its phone validation can flag a line type as Google Voice, and that its VoIP blocklist covers Google Voice among other providers.

Reputation and history. Risk systems can also weigh how a number has been used before. Google itself limits how many accounts each phone number can create, and its help page gives that limit as the reason for its “This phone number cannot be used for verification” error, without mentioning VoIP.

Standards pressure. NIST SP 800-63B revision 3 said methods that don’t prove possession of a specific device, such as VoIP or email, shall not be used for out-of-band authentication. Revision 4, published in July 2025, dropped that explicit VoIP sentence but still classifies phone-network codes as a restricted method. That guidance was written for US federal systems, but it is widely referenced and may help explain why regulated services lean strict.

Ported numbers are harder to predict, so don’t assume a ported number keeps or loses its old classification; test before you rely on one.

Which services accept or reject a Google Voice number for verification

Read this as a map of categories, not a promise, because policies change quietly. Named examples are limited to what each service publicly documents.

The more money or fraud exposure a service carries, the more likely it has a hard VoIP rule, while many low-risk sign-ups never run a line-type lookup at all. Test on the actual service before you depend on it.

What a flagged number looks like

An error at entry. The form rejects the number with a message about VoIP, virtual, landline or unsupported numbers, or simply asks for a valid mobile number. That is policy, and resending won’t change it.

Accepted, then silence. The form says a code was sent and nothing arrives: a quiet line-type filter, a short-code sender that doesn’t route to VoIP, or a Voice account problem. Steps 2 and 4 below help tell them apart.

A voice-call fallback. Some services offer to call you with the code. Google Voice receives calls, so it’s worth trying, though a service may apply the same line-type rule to calls, and call options can carry their own conditions: Telegram’s FAQ, for instance, says login codes by phone call are only available for accounts with two-step verification enabled.

A later request for another number. A service may accept the number at sign-up, then ask for a different one at a later security check.

The 2026 identity check on new Google Voice numbers

Google’s help center says people who request a new Google Voice number can’t send or receive calls or texts until they complete identity verification with a legal name, a government-issued ID and an address. Decisions are instant or go to a manual review of up to 3 business days, with a limited number of attempts. Security-news coverage reports the requirement took effect on January 30, 2026; Google’s page doesn’t state a date.

A number stuck in review won’t receive a code from any service, so check that status first. Free personal Google Voice and the Voice Starter and Standard standalone plans are also US-only.

Keeping your Google Voice number active

Google’s Acceptable Use Policy says a number may be reclaimed if it isn’t used as intended, such as placing calls or sending texts, for 3 months. The reclaim help page adds that you get a warning with a reclaim date, that a call, a text or listening to voicemail before that date keeps the number, and that there’s a 45-day window to get it back afterwards. Behavior differs for the Voice Starter and Standard plans.

Receiving verification texts isn’t among the activities Google lists, so a number used only to catch codes can drift toward reclamation, taking every account’s recovery path with it.

The routine: one outbound text or short call per number on a monthly reminder, and act on any reclaim warning the day it arrives. PVAVRT gives its buyers the same advice: use or warm each number at least once a month. The 30-day warming playbook has a fuller warm-up sequence.

Google Voice for 2FA: lockout risk and the code scam

Lockout. Google Account Help warns against using Google Voice to receive 2-Step Verification codes, because signing back in to Voice can require a code that is sent to Voice itself.

Better options. Where a service offers an authenticator app or a passkey, use it and keep the phone number as a backup.

The code scam. The FTC warns about strangers, often answering a for-sale listing or a lost-pet post, who ask you to read back a Google Voice verification code so they can set up a Google Voice number tied to your phone. Never share a verification code with someone who contacted you first.

Troubleshooting Google Voice not receiving verification codes

Work through these in order and stop when one explains the failure.

1. Confirm the number is live. Sign into the Google account that holds it and look for pending identity verification or a reclaim warning.
2. Send yourself a test text from another phone. If it doesn’t arrive, the problem is on the Voice side (Failure 3). If it does, look at the service or the sender.
3. Read the error, if there is one. A rejection that mentions VoIP, landlines or mobile-only numbers is a line-type block (Failure 1). Stop resending.
4. Check the sender. If codes come from a short code, delivery to Google Voice is up to that sender, so look for a voice-call or email option (Failure 2).
5. Check where the text went. Look for a spam folder or blocked-numbers list in Voice, and open the Voice inbox directly if you rely on forwarding.
6. Space out resends. Rapid repeat requests can run into a service’s own limits.
7. Switch methods. Use a voice call, an authenticator app, email, or a carrier mobile number in your own name.

If a number from PVAVRT fails at step 2, the 7-day replacement guarantee covers any Google Voice account that fails first login or first SMS receive; a service’s VoIP rule is a separate issue no replacement can fix. See the replacement guarantee explainer.

When a real mobile number is the better choice

Use a carrier mobile number registered in your name when:

• the service publicly documents that it rejects VoIP numbers, like the bank, WhatsApp, Azure and OpenAI examples above
• the number would be the 2-Step Verification number for the Google account that holds your Voice number
• the account holds money, identity documents or anything regulated
• you’ve already hit a hard rejection, because cycling through other virtual numbers doesn’t change a policy, and dodging a fraud or identity check can breach the service’s terms

Google Voice still fits lower-risk sign-ups, business texting and secondary contact numbers.

Pre-verification checklist

• Checked the service’s help center for a VoIP or mobile-only rule
• Number active in Voice, identity verification complete, no reclaim warning
• Test text from another phone arrived
• Know whether the code comes from a short code, and whether a voice-call option exists
• Not the 2-Step Verification number for the Google account that holds this Voice number
• Authenticator app, passkey or backup codes set up wherever the service offers them
• Monthly outbound text or call on the calendar
• Never shared a code with anyone who contacted you first

Where PVAVRT fits

A Google Voice number from any source, PVAVRT included, is still a Google Voice number: a line-type lookup can classify it as non-fixed VoIP, and the strict services above may reject it. Because Google’s policy prohibits selling or transferring Voice accounts and ties a new number’s identity verification to the person who requested it, a purchased account can also be suspended, so don’t make it the only recovery or 2FA route for anything important. What we control is account quality before delivery.

• Real US Google Voice number with a linked Gmail — SMS receive and send enabled out of the box, voicemail with transcription, call forwarding, and SMS-to-email forwarding from a single login
• Hand-checked before delivery — every account is login-tested before it ships
• 7-day replacement on first-login or first-SMS failures — send the failing details on Telegram and we replace within an hour
• Fast delivery — most orders ship within 4 hours of payment confirmation, delivered in your Telegram thread
• 24/7 Telegram support — average response under 5 minutes
• A clear use policy — accounts are sold only for legitimate marketing, automation, QA testing and persona-research purposes, and we refuse and refund orders where the intended use looks like fraud, harassment or impersonation

Buying Google Voice accounts is not illegal in most jurisdictions, but it does violate Google Voice’s Terms of Service, and Google’s Acceptable Use Policy prohibits selling Voice accounts and creating multiple accounts. Downstream use is your responsibility; our legality guide covers the detail.

Brief us on Telegram with the services you plan to verify, how many numbers you need and your timeline, or start from the contact page. See Google Voice accounts for current options, the Google Voice numbers guide for which option suits which use case, or the FAQ for payment and delivery details.