Quick answer: If your Chase login is not working, the cause is almost always one of five things: a saved password or autofill mismatch, verification codes not arriving, device or session trust issues, app loading or login loop problems, or a temporary lock after failed attempts. Most Chase login problems resolve within five to ten minutes by following the right fix in the right order — which this guide covers.
Important: OnlineBankingHelp.com is an independent educational resource. We do not access accounts, view private information, or perform account actions. If you cannot complete verification or suspect fraud, contact Chase directly using official channels.
Fix Chase login problems now — quickest steps first
Work through these in order. Skipping ahead and retrying failed passwords repeatedly is the most common mistake — it triggers security locks that make the situation worse.
- Try Chase.com on desktop before the app — if the app is behaving strangely, desktop login is usually more stable and helps isolate whether the issue is app-specific or account-level
- Turn off VPN, iCloud Private Relay, or masked networks — these are one of the most common causes of Chase verification loops and silent login blocks; disable them before attempting to log in
- Disable password autofill and type manually — old saved passwords are a major cause of “incorrect password” errors even when you are certain the password is right
- Verification code not arriving? — wait two to three minutes, request the code once more, then switch delivery method (SMS vs email) if Chase offers the option; do not request repeatedly
- App not loading or stuck? — switch between Wi-Fi and mobile data, restart your phone, then check for a pending app update
- Login loop on Chase.com? — turn off private browsing, allow cookies for Chase.com, and clear site data for Chase.com specifically rather than clearing all browser data
- Account locked after failed attempts? — stop entering passwords immediately; use Chase’s official reset flow or call the number on the back of your card
Key signal: If login works on one device but not another, your account is almost certainly fine. That split behavior means Chase is protecting the specific session — not rejecting your credentials.
How to sign in on Chase.com (desktop)
Desktop login is the most stable option when the mobile app is freezing, crashing, or not delivering verification prompts.
- Go directly to Chase.com — type the address manually rather than clicking a link from an email or text
- Click Sign in in the upper right corner
- Enter your username and password — with autofill disabled
- Complete the verification step if prompted
If the Sign in button does nothing when clicked, the cause is usually blocked scripts or cookies. Disable strict tracking protection, allow cookies for Chase.com, and turn off private browsing or “clear cookies on exit” settings for this site specifically.
How to sign in using the Chase mobile app
- Open the Chase app — confirm it is the official Chase Mobile app from JPMorgan Chase
- Tap Sign in
- Enter your username and password
- Complete verification if prompted
If the app is stuck on a loading screen, crashing, or showing a login loop, see how to fix the Chase app when it is not working for the full troubleshooting guide.
Password and username recovery
If you are not completely certain about your credentials, recovery is faster and safer than repeated guesses that trigger security locks.
Forgot Chase password
- On Chase.com, select Forgot username/password?
- Choose Password
- Enter the requested identifying information
- Complete verification through your registered phone number or email
- Create a new password and sign in
For the complete step-by-step guide, see how to reset your Chase password.
Forgot Chase username
- Select Forgot username/password? on Chase.com
- Choose Username
- Complete identity verification
- Retrieve your username and sign in
If recovery fails, the most common reason is outdated contact information on the account. In that case Chase requires identity verification by phone — call the number on the back of your debit card.
Common Chase login problems and what each one means
Incorrect password error even though you’re sure it’s right
Almost always caused by autofill entering an old saved password, or a username mismatch where you are logging into a different account than you think. Disable autofill, type both username and password manually, check Caps Lock, and if you are still getting the error after two clean manual attempts, use the reset flow rather than trying again — three to five failed attempts typically triggers a security lock.
Verification code not arriving
Your password may be entirely correct — the code delivery is the problem. Common causes: carrier short-code blocking (some carriers filter bank verification SMS), spam filters on email, an old phone number or email address on file with Chase, or a VPN masking your location and triggering enhanced security. Fix order: wait two to three minutes, request the code once more, switch delivery method if available, disable VPN, try a different device. If none of these work, your contact information on file with Chase may need to be updated — which requires calling Chase directly.
Chase asks for verification every single login
Chase cannot recognize your session as trusted — which happens when private browsing deletes cookies after every session, when a VPN changes your apparent location on each login, or when browser tracking protection blocks Chase’s session recognition. Fix: use a standard browser window (not private/incognito), allow cookies for Chase.com, and disable VPN during sign-in.
Desktop login works but app fails (or vice versa)
This almost always points to a device-level or network-level issue rather than an account problem. For app-specific failures: update the app, force-close and reopen it, switch between Wi-Fi and mobile data, or uninstall and reinstall. For desktop-specific failures: try a different browser, disable extensions, and clear Chase.com site data specifically.
Account locked after failed login attempts
Stop entering passwords immediately — additional attempts extend the lock period. Use Chase’s official password reset flow first. If the reset flow cannot verify your identity because your contact information is outdated, call the number on the back of your Chase debit card and verify your identity over the phone. Chase can restore access and update your contact information in one call.
Chase login not working today — possible outage
Outages do occur and can affect verification delivery, app login, or specific services without a full site-wide outage. Signals that point to an outage rather than an account issue: both app and desktop fail in the same way, verification codes are delayed across multiple devices, and other users are reporting the same problem simultaneously. Check downdetector.com for real-time Chase outage reports before spending time troubleshooting.
When to contact Chase directly
Contact Chase if verification cannot be completed through any available method, your contact information on file is outdated and recovery fails, your account remains locked after the reset flow, or you notice login activity or transactions you do not recognize. Call the number on the back of your Chase debit card — not a number from a text, email, or search result. Chase fraud and login impersonation scams are common; always initiate contact yourself.
Chase customer service: 1-800-935-9935
Related Chase guides
- Chase app not working — fixes for crashes, loading issues, and login loops
- How to reset your Chase password
- Why your Chase transfer is pending
- Chase mobile and ATM deposit limits
- Chase routing numbers by state
Frequently Asked Questions
Why is my Chase login not working?
The most common causes are an autofill mismatch entering an old saved password, verification codes not arriving due to carrier filtering or an outdated phone number on file, a VPN blocking session recognition, or a security lock from repeated failed attempts. Try disabling autofill and VPN first, then use the official reset flow if the password itself is the issue.
Why is Chase asking for a verification code every time I log in?
Chase cannot recognize your session as trusted — most commonly because private browsing is deleting your session cookies after each login, a VPN is changing your apparent location, or browser tracking protection is blocking Chase’s session recognition. Use a standard browser window, allow cookies for Chase.com, and disable VPN during sign-in to establish a trusted session.
What do I do if my Chase verification code is not arriving?
Wait two to three minutes — codes can be delayed by carrier networks. Then request the code once more and switch delivery method if Chase offers the option (SMS vs email). Disable any VPN. If codes still do not arrive, your phone number or email on file with Chase may be outdated — call the number on the back of your debit card to verify your identity and update your contact information.
My Chase account is locked — what do I do?
Stop entering passwords immediately — additional attempts extend the lock. Use Chase’s official Forgot username/password? reset flow on Chase.com. If the reset flow cannot verify your identity because your contact information is outdated, call 1-800-935-9935 or the number on the back of your Chase debit card. Chase can restore access and update your contact details over the phone after identity verification.
Why does Chase login work on desktop but not the app?
Split behavior between devices almost always indicates a device or network issue rather than an account problem. For app-specific failures: update the Chase app to the latest version, force-close and reopen it, switch between Wi-Fi and mobile data, or uninstall and reinstall. If none of these work, see the full guide at Chase app not working.
Is Chase online banking down right now?
Check downdetector.com for real-time Chase outage reports from other users. Outages can be partial — affecting verification, app login, or specific features without a complete site-wide outage. If both desktop and app are failing in the same way and other users are reporting similar issues, an outage is likely rather than an account-specific problem.
