Guide · checked September 2026
Does Google Voice work for verification codes and bank 2FA?
A Google Voice number is an internet number. Many services check line type before they send a code, and the ones that filter VoIP filter Google Voice. The ones that don't check will text it happily. Nobody publishes a full list, policies change without notice, and the day you find out is usually the day you needed the code.
By the Cleat team · Updated September 17, 2026
What Google Voice is, to a lookup service
Twilio's Line Type Intelligence documentation uses Google Voice as its example of a nonFixedVoip number: “a virtual phone number obtained online without requiring a physical device” (Twilio). Fixed VoIP is the other internet kind, tied to a physical phone service. A business that filters out VoIP won't send a code to a Google Voice number. How long you've had it makes no difference, and neither does how well you have behaved.
Our guide to non-VoIP numbers explains how these checks work, why they sometimes misread a real carrier line, and what the sellers of internet numbers say about them.
Who publishes a refusal, and who just refuses
This is the distinction that decides what you can plan around. A published rule is a fact you can read before you commit. An unpublished habit is something you discover at a checkout. Both stop the code; only one of them is predictable.
| Who | What they publish | Names Google Voice? |
|---|---|---|
| OpenAI | “We do not support use of landlines, VoIP, Google Voice, or premium numbers at this time. All of those types of phone numbers are often associated with higher instances of fraud or abuse.” | Yes, by name |
| Cash App Taxes | “We do not support non-fixed VoIP phone numbers such as Google Voice or Skype.” It still permits “a US-based mobile or home phone number”. | Yes, by name |
| Login.gov (identity check) | Doesn't accept “Google Voice or similar VoIP (Voice over Internet Protocol) numbers”. Its sign-in rule is separate and says “Do not use web-based (VOIP) phone services or premium rate (toll) phone numbers.”. | Yes, by name |
| Microsoft | “VOIP numbers cannot be added as a way to sign in or get verification codes. Please add a mobile phone number.” | No, but it covers it |
| Steam | “We are unable to accept new VoIP phone numbers on Steam due to them not meeting our security requirements.” | No, but it covers it |
| “Some third-party services may not accept phone numbers which originated from Google Voice, including after they have been ported to Google Fi Wireless.” | Google's own words |
Now the other half, and it is the half most people are actually asking about. PayPal, Venmo, Coinbase and Chime publish no VoIP rule on the help pages we read. Venmo's user agreement asks you to “use a cellular/wireless telephone number that you own”, which is a term of eligibility rather than a verification rule. That is the whole documented record for those four. They are reported refusing internet numbers constantly, and none of them says so in writing, so the only honest description is undocumented and unpredictable. We are not going to invent a policy to fill the gap. What each service actually publishes is the full dated record, silences included.
What people report
These are public reports, not a compatibility list. Services change their rules, and one person's experience isn't a promise about yours.
| Where | What was reported | Source |
|---|---|---|
| A banking app | A thread titled “Banking app won't send verification codes to my Google voice number” | Google Voice Community |
| Microsoft (Azure OpenAI sign-up) | A question quoting the error “Sorry, we do not accept Voice over IP (VOIP) numbers. Try again with a different number.” | Microsoft Q&A |
| Financial institutions, in general | TextNow's own comparison page: “Some companies, especially financial institutions, will not send account verification codes to a VoIP number like Google Voice” | TextNow |
The day the codes stop arriving
Something that worked last month doesn't today, and there is no error message explaining it. Work through this in order. The first two steps are cheap and rule out the causes that aren't a policy change at all.
- Check the Voice spam folder before anything else. Google's own advice is blunt: “If you don't get a text you're expecting, check if it got marked as spam” (Google). A bank's short code looks a lot like bulk messaging, and this is the single most common false alarm.
- Ask for the code by phone call instead. Plenty of services offer a voice option and never mention it until you look. Google Voice answers calls, and a spoken code is a code. Verification by automated phone call covers which services do this and how the call behaves.
- Check the number is still yours. A number kept only for codes is the one most likely to have been reclaimed for inactivity, and receiving texts doesn't count as using it. What happens when Google Voice takes your number back has Google's rule quoted and the 45-day recovery window.
- Look at whether the service wants a reply, not a code. Some confirmations are “reply Y”, and Google Voice cannot send to a short code. The next section covers this; it is the failure people misdiagnose most often.
- Assume a policy change only after those. If the service now filters VoIP, nothing you do to the Google Voice number will fix it. Retrying, waiting and re-adding the number are all the same answer more slowly.
- Get in from another direction while you still can. An authenticator app, a passkey, a security key or backup codes will let you into the account without the number. Do this before you change anything, not after.
- Then change the number on the account, starting with accounts you're still signed in to. A live session is a door that closes on its own schedule. Use it while it is open.
Short codes, and the reply you can't send
Most verification texts come from a five- or six-digit short code rather than a normal number. Receiving from one is usually fine. Replying is not: Google publishes that with Voice, “You can't send texts to five- or six-digit “short code” numbers” (Google).
That matters more than it sounds, because a growing number of confirmations are a reply rather than a code. Reply YES to approve this payment. Reply 1 if this was you. On a Google Voice number those flows dead-end, and the account you are trying to protect reads your silence as a refusal. It is the same limit a receive-only line has, so it is one of the places where Cleat is no better: neither can send the reply.
Two Google Voice rules that catch people out
Quiet numbers can be reclaimed
Google's help centre warns that a Google Voice number can be removed after a period of inactivity. Making calls, sending texts and listening to voicemail count as activity. Receiving a text isn't on Google's list. If your number is removed, you have 45 days to get it back, and “After your number is reclaimed, your messages are still in your Voice account, but you can't get calls or texts” (Google). Your history survives; delivery stops. A number you only use for codes is exactly the kind that goes quiet.
It's a US product
Personal Google Voice is listed as “Available in the US” (Google Workspace). Signing up means verifying an existing phone number that “can get texts” (Google). Living outside the US? See how to get a US number from abroad or Cleat for expats and non-residents.
Moving the number off Google Voice
You can take the digits to a real carrier, and it is cheaper than most people expect. Google publishes the route: unlock the number first, then have the new carrier port it in. “When you unlock your Google Voice number, it costs $3 USD. But if your number was originally ported in from another carrier, there's no charge.” Allow time: “Phone numbers can take up to 48 hours to port.” (Google)
What a port does not reliably buy you is acceptance. On the same page, Google writes that “Some third-party services may not accept phone numbers which originated from Google Voice, including after they have been ported to Google Fi Wireless. We recommend contacting any affected third-party service providers should this issue arise.” That is Google, about its own numbers, on its own network, telling you the stigma can outlive the port. If your reason for porting is a bank that keeps refusing the number, treat the outcome as unknown rather than fixed. Keeping a US number when you move abroad weighs the porting routes against each other.
What to do
- Use an authenticator app or a security key wherever the service offers one. It's stronger than text codes, and your number stops mattering. This is the only step that ends the problem instead of moving it.
- If the service insists on SMS and refuses your number, you need a mobile line: your own SIM, a prepaid US SIM or eSIM (check the phone and activation rules), or a real mobile line delivered online.
- If you keep Google Voice for calls, use it now and then so it isn't reclaimed. One outbound call or text is enough, and receiving nothing counts.
- Don't move ten accounts at once to a number you haven't tested. Move the account that failed, confirm a code arrives, and only then do the rest.
- If coworkers share the account, don't route its codes through one person's phone. See a shared 2FA number for teams.
Where Cleat fits, and where it doesn't
Cleat is a real US mobile line. Texts arrive in a live inbox, by email, on Telegram, or in your own tools by webhook and API. It isn't VoIP, which is what a line-type filter is looking for. Every owner verifies their identity. It costs $24.99 a month, cancel anytime. When a service reads a code out over an automated call, the call is transcribed and the transcript lands in the inbox with the texts. Compare it with Google Voice, or see pricing.
Where it is the wrong answer, plainly. It cannot send a text, so a “reply YES to confirm” flow fails on Cleat exactly as it fails on Google Voice. Cleat Line cannot place calls, and no plan reaches 911. It is a new number: Cleat cannot port your Google Voice number in, and you cannot choose the area code, so if the point is keeping the digits your family knows, the $3 port above is your answer and Cleat is not. And no provider can promise a particular service accepts a particular number, us included.
Keep reading
What happens when Google Voice takes your number back · A Google Voice alternative for codes that refuse VoIP · What each service publishes about VoIP numbers
Questions
Is Google Voice a VoIP number?
Yes. Twilio's documentation uses it as its example of a non-fixed VoIP number, and OpenAI, Cash App Taxes and Login.gov name Google Voice in their own refusals.
Why does my bank say it can't send a code to my Google Voice number?
Most likely it checks line type and refuses VoIP. The awkward part is that the big consumer finance apps don't publish a VoIP rule at all, so nobody can tell you in advance which ones do it.
Does Google admit that services reject Google Voice numbers?
Yes, in one place: its porting page. “Some third-party services may not accept phone numbers which originated from Google Voice, including after they have been ported to Google Fi Wireless.”
Can I reply to a verification text from Google Voice?
Not if it came from a short code. Google publishes that you “can't send texts to five- or six-digit “short code” numbers”, which breaks any “reply Y to confirm” flow.
Will Google take my number away if I only receive codes on it?
It can. Google removes inactive numbers, with 45 days to recover them, and receiving texts isn't among the activity it lists.
Will porting my Google Voice number to a carrier fix the rejections?
Maybe not. Google warns that services may still refuse a number that originated with Voice, even after a port to Google Fi. It costs $3 to unlock and up to 48 hours to port, so it's cheap to try, but treat the result as unknown.
Can I get Google Voice in Brazil or Mexico?
The personal product is listed as available in the US. Google also sells Voice to businesses through Workspace, priced per user.
Does Cleat guarantee my bank will accept it?
No. Most services that refuse VoIP accept a real mobile line, but no provider can promise that every service accepts every number. Try it in your first month and cancel if it doesn't fit.
Can Cleat receive a code and reply to it?
Receive, yes, including transcripts of automated calls. Reply, no: Cleat Line is receive-only, so a “reply YES” confirmation fails on it just as it does on Google Voice.
Sources
Facts about other companies come from their own pages, checked in September 2026.
- Twilio, Lookup Line Type Intelligence https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence
- Google Voice Community https://support.google.com/voice/thread/253470343
- Microsoft Q&A https://learn.microsoft.com/en-us/answers/questions/2127580/
- TextNow, TextNow vs Google Voice https://www.textnow.com/review/textnow-vs-google-voice
- Google Voice Help, inactive numbers https://support.google.com/voice/answer/159519
- Google Voice Help, port your Google Voice number https://support.google.com/voice/answer/1065667
- Google Voice Help, send & get text messages https://support.google.com/voice/answer/115116
- Google Workspace, Google Voice https://workspace.google.com/products/voice/
- Google Voice Help, getting started https://support.google.com/voice/answer/115061
- OpenAI Help Center, can I use a landline, Google Voice or other VoIP number? https://help.openai.com/en/articles/8983024-can-i-use-a-premium-number-landline-google-voice-or-other-voip-phone-number
- Cash App Taxes Help, Google Voice or Skype for phone verification https://taxeshelp.cash.app/s/article/Can-I-use-Google-Voice-or-Skype-for-phone-verification
- Login.gov Help, verify my phone number https://login.gov/help/verify-your-identity/phone-number/
- Login.gov Help, changing your phone number https://login.gov/help/manage-your-account/change-your-phone-number/
- Microsoft, troubleshoot verification code issues https://support.microsoft.com/en-us/accounts-billing/manage/troubleshoot-microsoft-verification-code-issues
- Steam Guard Mobile Authenticator FAQ https://help.steampowered.com/en/faqs/view/7EFD-3CAE-64D3-1C31
- Venmo, US user agreement https://venmo.com/legal/us-user-agreement/