Bank of America SafePass Not Sending Code to Phone? 6 Ways to Fix 2FA SMS Failures

By David Sterling, Senior Financial Systems & Cybersecurity Analyst (CISA) Published: September 2026 | Technical Verification: Telecommunications & 2FA Routing

When attempting to transfer money, enroll a new Zelle recipient, or log in from a new device, Bank of America triggers its proprietary two-factor authentication (2FA) mechanism: SafePass®. You tap "Send Code," the 60-second countdown timer begins ticking away—and your smartphone remains completely silent.

Missing a SafePass code can freeze time-sensitive wire transfers, lock your online banking session, or leave you stranded at a checkout terminal. This guide covers the root telecommunications causes behind missing SafePass SMS messages and outlines 6 concrete fixes to restore instantaneous code delivery.

Basic Troubleshooting First Aid: SafePass Delivery Matrix

Technical Architecture: How Bank of America Routes SafePass Codes

SafePass does not send standard peer-to-peer (P2P) SMS text messages. Instead, Bank of America routes its one-time passcodes through Application-to-Person (A2P) aggregators (such as Twilio, Syniverse, or Infobip) utilizing registered five-digit shortcodes: 73981 and 99217.

When you request a code, your mobile carrier's SMS gateway inspects the sender ID. If the shortcode is flagged as promotional, if your account has a shortcode block enabled, or if your cellular connection has poor signal quality, the message is discarded silently before it ever vibrates your device.

6 Proven Fixes for Missing SafePass Codes

Fix 1: Unblock Bank of America Shortcodes (73981 & 99217)

The fastest and most reliable fix for missing SafePass codes is to force your mobile carrier's gateway to re-establish two-way communication with Bank of America's shortcode servers:

1. Open your smartphone's native Messages app.
2. Create a new message addressed to: 73981.
3. Type the word HELP and press Send.
4. If the gateway is active, you should receive an automated reply within seconds: "Bank of America: For assistance call 1.800.432.1000..."
5. If you receive a reply, immediately send: ALLOW or UNSTOP.
6. Repeat this exact process for the secondary BofA shortcode: 99217.
7. Return to your Bank of America app or browser and request a new SafePass code.

Fix 2: Check iOS and Android Hidden Spam / Junk Folders

Modern mobile operating systems feature aggressive spam protection that categorizes banking shortcodes as junk without firing a notification:

• iPhone (iOS):
  1. Open the Messages app.
  2. Tap Filters in the upper-left corner.
  3. Look inside Unknown Senders and Junk. In many cases, 4 or 5 SafePass codes will be waiting quietly without having triggered an audible alert.
  4. Go to Settings > Phone > Silence Unknown Callers and ensure it is not sending verification phone calls directly to voicemail.
• Android (Google Messages):
  1. Open the Messages app.
  2. Tap your profile icon (top right) > Spam and blocked.
  3. Verify whether messages from 73981 or 99217 have been trapped by the spam filter. Tap the number and select Not Spam.

Fix 3: Request an Automated Voice Call Instead

If SMS delivery remains stalled due to carrier tower congestion, switch authentication channels:

1. On the SafePass prompt screen, look below the "Send Code" button for: "Need another way to verify?" or "Call my phone instead."
2. Select the voice call option.
3. Bank of America's automated IVR system will place a standard voice call to your registered mobile or landline number.
4. Answer the call, press 1 to accept the authorization, and the system will read your 6-digit numeric code aloud.

Fix 4: Verify the Number Is Not Flagged as VoIP

Bank of America strictly adheres to financial anti-fraud protocols that disallow Voice-over-IP (VoIP) numbers for security verifications. SafePass will not send SMS codes to:

• Google Voice
• Skype Numbers
• TextNow / Burner apps
• Vonage or business SIP extensions

If your registered primary number is a VoIP line, the system will appear to send the code on your screen, but the back-end API will drop the transmission without notifying you. You must register a true cellular telephone number linked to a Tier-1 wireless network.

Fix 5: Overcome the 72-Hour Security Hold on Newly Added Numbers

If you recently updated or changed your mobile phone number on Bank of America Online Banking:

• The 72-Hour Anti-Takeover Hold: Bank of America imposes an automatic 3-day hold on newly registered mobile numbers before they can be utilized for outbound SafePass verifications (e.g., initiating Zelle, adding wire recipients).
• During this window, codes can only be dispatched to your secondary registered phone number or verified via a physical SafePass card token.

Fix 6: Resynchronize a Physical SafePass Card Token

If you are an international client, business client, or commercial customer utilizing a credit-card-sized physical SafePass card with an LCD screen:

1. Internal clocks in the card token can drift out of sync with Bank of America's authentication servers over time.
2. Visit the official SafePass management portal: https://safepass.bankofamerica.com/sasuser/Home.do.
3. Sign in with your corporate or personal credentials.
4. From the left navigation menu, select Synchronize Token.
5. Press the button on your physical card to generate two consecutive 6-digit codes and enter them into the fields provided.
6. Once the server recalibrates its counter against your card's microchip, code acceptance is instantly restored.

Escalation: Contacting Technical Support for SafePass Reset

If you have tried all above steps and still receive no codes, your profile may have a backend telecommunications hold placed on it (common after SIM swaps or carrier porting).

• Direct Support Line: 1-800-432-1000 (Consumer) or 1-866-283-4093 (SafePass Dedicated Line).
• Keywords to Tell the IVR: Say "Technical Support - SafePass Verification Issue."
• What to Ask the Agent: Request that the specialist perform an "Out-of-Band Phone Number Verification Reset" in your profile to clear stale carrier routing cache.