Quick Answer
AUT002 is an error code that Scotiabank customers have reported seeing while trying to log in through the mobile app or online banking. Scotiabank has not published an official explanation for this specific code, but its “AUT” prefix and the circumstances users describe point to an authentication or sign-in verification failure rather than a full outage. In most cases it clears up after updating the app, clearing cache, or resetting your password; if it doesn’t, Scotiabank’s support team can check your account directly.
TL;DR
- AUT002 is a user-reported code, not one Scotiabank has officially documented in detail.
- It appears tied to login/authentication rather than a site-wide outage.
- Updating the app and clearing its cache resolves it for most people.
- A password reset or switching between app and browser can also help.
- If it persists, contact Scotiabank support directly rather than guessing further.
On this page
What is the AUT002 error code?
AUT002 is a short alphanumeric error code that Scotiabank customers have reported encountering while signing in to online banking or the mobile app. It’s worth being upfront about what is and isn’t confirmed here: Scotiabank has not published a public knowledge-base entry that defines exactly what AUT002 means or what triggers it. What we do know comes from customer reports, including a message posted to Scotiabank’s support account on social media flagging the exact code by name.
The “AUT” prefix is a common convention banks use for authentication-related error families, which lines up with what affected users describe: the error tends to show up during login, not while browsing an already-authenticated account. That’s a reasonable inference based on naming pattern and user reports, not an official confirmation from the bank.
Important points to check first:
- Confirm whether the error appears only when logging in, or also once you’re already signed in.
- Check if it happens on both the app and the website, or just one of them.
- Note whether it started right after a password change, app update, or new device setup.
- Try a different network (Wi-Fi vs. mobile data) to rule out a local connectivity issue.
Why AUT002 happens
Based on the pattern of reports and how banking authentication systems typically work, a handful of causes are most likely behind this error.
Temporary server-side maintenance or load
Scotiabank’s own sign-in help pages note that ScotiaConnect and related services can be briefly unavailable during routine maintenance, which can present as a login failure until the maintenance window ends.
Outdated app version
Banking apps update their authentication flow frequently for security reasons. An older app version can fall out of step with the current login process and throw an authentication error like AUT002.
Session or token conflict
If you’re logged in on multiple devices, recently changed your password, or have a stale session cached in the app, the authentication token your device is sending may no longer match what the server expects.
Network or security software interference
VPNs, strict corporate firewalls, or browser privacy extensions can sometimes block or alter the authentication request before it reaches Scotiabank’s servers, producing a login error that has nothing to do with your account itself.
Step-by-step fixes
Try these in order. Most people resolve AUT002 within the first four steps.
- Force-close and reopen the app, or fully refresh the browser tab if you’re on the website.
- Check for a Scotiabank maintenance notice. Their sign-in help pages sometimes note scheduled downtime for services like ScotiaConnect.
- Update the app to the latest version from your device’s app store.
- Clear the app cache (Android) or offload and reinstall (iOS) to remove a stale login session.
- Log out completely and log back in with your current credentials.
- Reset your password if the error persists, since an expired or mismatched credential is a common trigger.
- Disable VPNs or browser extensions temporarily and try again on a plain connection.
Fixes by platform
Mobile app (iOS and Android)
- Confirm the app is updated to the current version listed in the App Store or Google Play.
- On iPhone, use Offload App under Settings, then reinstall; on Android, clear the app’s cache under Settings > Apps.
- Restart your device before trying to log in again, which clears any stuck background session.
Online banking (browser)
- Clear cookies and cached data for the Scotiabank sign-in domain, or try a private/incognito window.
- Temporarily disable ad blockers or privacy extensions that may interfere with login scripts.
- Make sure your browser itself is updated to a current version.
ScotiaConnect / business banking users
If you’re signing in through ScotiaConnect specifically, Scotiabank’s own help documentation notes that unassigned user privileges or an unregistered security token can also block sign-in with a related authentication error. In that case, your company’s Super User or Administrator needs to assign the correct access group before the error will clear.
Scotiabank login error reference table
A quick way to compare AUT002 against related login issues customers have reported.
| Situation | Likely Cause | Suggested Fix |
|---|---|---|
| AUT002 on app login only | Outdated app or stale session token | Update app, clear cache, log back in |
| AUT002 on both app and website | Server-side maintenance or account-level issue | Wait and retry, then contact support if it continues |
| Error right after password change | Credential mismatch during propagation | Wait a few minutes, log out fully, retry |
| ScotiaConnect sign-in blocked | Unassigned user privileges or missing token | Ask your company Super User to assign access |
| Error only over VPN or work Wi-Fi | Network or firewall interference | Switch network, disable VPN, retry |
Before you contact Scotiabank support, have this ready:
- The exact error code and a screenshot if possible.
- Whether it happens on the app, the website, or both.
- Your device type and app version, or browser and version.
- Roughly when the error started and what you were doing at the time.
Frequently asked questions
Does AUT002 mean my Scotiabank account has been compromised?
Not necessarily. Nothing in the available reports or Scotiabank’s own documentation ties AUT002 specifically to fraud or account compromise; it presents as a login/authentication failure, which is far more commonly caused by an outdated app, cached session, or maintenance window than by unauthorized account access. If you’re concerned, contact Scotiabank support directly rather than relying on unofficial sources.
Is there an official Scotiabank explanation for this error code?
Not that has been publicly published as of this writing. Scotiabank’s general sign-in help pages describe related issues, such as maintenance downtime or unassigned ScotiaConnect privileges, but they don’t list “AUT002” by name. This article is based on customer reports and general authentication-troubleshooting logic rather than an official bank statement.
Why does the error only happen on my phone and not on my computer?
This usually points to something specific to the app: an old version, a corrupted cache, or a stuck login session. Since the browser version authenticates independently, it isn’t affected by the same local app data.
What should I do if none of these steps fix it?
Reach out to Scotiabank’s support team directly with your device details and a screenshot of the error. Account-specific authentication issues are best resolved by their support staff, who can check your account status rather than relying on general troubleshooting.
For Scotiabank’s own guidance on related sign-in problems, see their official Sign In Help page. For other real-time app and banking service status checks, browse our full Outage Tracker section.
Reviewed and published by Anup V Naick, Games and Technology Editor. Scotiabank has not published an official explanation of the AUT002 code at the time of writing; this guide is based on verifiable customer reports and general authentication-troubleshooting practice, and will be updated if Scotiabank issues further clarification.
