The Western Alliance Bank Business login requires three credentials plus multi-factor authentication: a company ID assigned to the organization, a user ID unique to the individual operator, a user-chosen password meeting complexity rules, and a second factor via mobile app push, SMS, email, biometric, or RSA SecurID token. This guide walks through every step — first-time user setup, routine login, MFA enrollment, biometric mobile login, and password reset — with enough detail for treasury teams to train new users without calling support.
This page is a reference guide, not a login form. Always reach the actual business banking login through bookmarked URLs or the bank's official website. Do not follow login links embedded in unexpected emails, SMS messages, or social media — phishing attacks routinely imitate bank sign-in screens. For password resets and account unlock, use the Forgot Password link on the real login page or contact your company administrator through the business portal admin console.
Help Centre Security
Every session follows the same five-step sequence. First-time users complete one-time enrollment before the routine sequence takes over.
Open the Western Alliance Bank Business login page from the bookmarked URL or the bank's official website. Verify the address bar shows the correct domain and a valid HTTPS padlock before entering any credentials. Phishing sites imitate login pages but live on slightly different domains — always check.
Type the company ID assigned to your organization. The company ID creates a namespace boundary so that user IDs can repeat across different companies without collision and so that compromised credentials from one company cannot be tried against another. Treat the company ID as semi-public but protect it alongside other credentials.
Type the user ID unique to the named operator and the user-chosen password meeting complexity requirements (minimum length, complexity rules, rotation on admin roles). Passwords are case-sensitive. After 5 failed attempts the account locks and requires company administrator action to unlock.
The portal presents a second-factor challenge appropriate to company policy. Options: mobile app push (approve with biometric), SMS one-time code, email one-time code, or RSA SecurID hardware token. High-value approvers typically use SecurID to avoid SIM-swap risks. Session cookies issue only after MFA succeeds.
On successful authentication the business portal dashboard opens showing consolidated balances, pending approvals in the treasury queue, positive pay exceptions awaiting review, alerts, and secure messages. Role-based access determines which modules appear for each named user.
After completing at least one full password-plus-MFA login on the mobile app, enable biometric login in app settings. Future logins on that device replace password entry with Face ID, Touch ID, or fingerprint. MFA still applies on new devices and after password reset. Biometric secrets never leave the device.
Every requirement, every MFA option, every technical prerequisite in one table.
| Requirement | Value / Standard | Scope | Reset / Recovery |
|---|---|---|---|
| Company ID | Assigned at onboarding | Organization-wide | Contact treasury management |
| User ID | Per named operator | Individual | Administrator reassigns |
| Password | 12+ chars, complexity, annual rotation (admin) | Individual | Self-service reset or administrator |
| MFA — Mobile push | Biometric-approved notification | Mobile-app users | Re-enroll on new device |
| MFA — SMS | 6-digit code, 5-minute validity | Any user with phone | Update number in settings |
| MFA — Email | 6-digit code, 5-minute validity | Any user with email | Administrator updates email |
| MFA — RSA SecurID | 6-digit time-based one-time password | Privileged and high-value users | Administrator reissues token |
| MFA — Biometric | Face ID, Touch ID, fingerprint | Mobile app post-enrollment | Re-enroll via app settings |
| Session | End of banking day | All sessions | Re-login next day |
| Browser | Current Chrome, Safari, Edge, Firefox | Web portal | Update to supported version |
| Mobile OS | iOS 15+ or Android 10+ | Mobile app | Update device OS |
| Lockout | After 5 failed attempts | All users | Administrator unlocks |
New users added by a company administrator complete a one-time enrollment before the routine login sequence takes over.
When the company administrator adds a new user through the business portal admin console, the portal emails temporary credentials to the address on file. The email includes the company ID, user ID, and a one-time temporary password that must be changed on first login. The email does not include a direct login link — users navigate to the bookmarked login URL manually, type the temporary credentials, and then complete initial MFA enrollment and password reset. This email-without-link pattern reduces phishing risk.
On first successful temporary-password login, the portal prompts MFA enrollment. The user selects a primary second-factor method (mobile push is recommended where available) and registers the phone, email, or RSA SecurID token. A backup method is required so that loss of the primary method does not permanently lock the user out. After MFA enrollment completes, the temporary password must be changed to a permanent password meeting complexity requirements, and only then does the user reach the business portal dashboard.
Most credential issues resolve through self-service or the company administrator without involving bank support staff.
Click Forgot Password on the login page, enter company ID and user ID, complete identity verification via MFA, and receive a reset link by email (60-minute expiry). Create a new password meeting complexity rules. The new password can be used immediately. Self-service reset does not unlock a locked account.
Company administrators reset passwords through the admin console when self-service is unavailable — typically because the email on file is outdated or inaccessible. The admin console issues a new temporary password requiring change on next login. Administrators can also unlock accounts locked after 5 failed attempts through the same console.
Report a lost RSA SecurID token to the company administrator immediately. The administrator deactivates the lost token through the admin console and orders a replacement. Replacement tokens ship within 2-3 business days. Until the new token arrives, the user can typically login with backup MFA methods (mobile app or SMS) depending on company policy.
For self-service password reset, use the Forgot Password link on the business banking login page. For locked accounts, contact your company administrator to unlock through the admin console. For RSA SecurID token replacement, the administrator orders a new token through the portal. For any other issue — MFA not arriving, enrollment problems, biometric login setup — call +1-800-444-7441 Monday through Friday from 7:00 AM to 8:00 PM Mountain Time, or 24/7 for enrolled corporate clients.
Help Centre Contact TreasuryCommon questions about credentials, multi-factor authentication, biometric login, and password recovery.
Three credentials: company ID, user ID, password. Then MFA: mobile push, SMS, email, biometric, or RSA SecurID. New users receive temporary credentials from the company administrator. See security for credential policy.
MFA required every login. After credentials, the portal presents a second-factor challenge. Options include mobile push (biometric approval), SMS/email codes (5-min validity), and RSA SecurID tokens. Session cookies expire at end of banking day. See security.
Complete one full password-plus-MFA login on the device. Open the mobile app settings, select security, enable biometric login, confirm with device prompt. Biometric secret stores in device secure enclave — never on bank servers.
Click Forgot Password on the login page. Enter company ID and user ID. Complete identity verification. Reset link emails to address on file (60-min expiry). If email is outdated, contact company administrator. See help centre.
Yes. iOS and Android. Biometric login, balance check, payment approvals, positive pay exceptions, remote check deposit, wire/ACH release for approvers, alerts. Shares backend with web portal — changes sync instantly. See mobile app.