The official web login for Wave is hosted through Wave at my.waveapps.com.
Wave currently supports sign-in using a primary email address as well as Google or Apple authentication. Depending on the login experience assigned to an account, an email user may first enter the address and then continue to a password or passcode step. MFA can also be required when it has been enabled.
This publication is independent from Wave. We do not operate a Wave sign-in form and will never ask for your Wave password, verification code, recovery key, or banking credentials.
An Important August 2026 Login Change
One recent change is especially relevant to existing Wave users.
Wave states that as of August 19, 2026, additional email addresses can no longer be used to sign into a Wave account.
Users must instead sign in with the account’s primary email address or another supported authentication method associated with the account.
This means a login that previously worked through a secondary address may stop working even though the underlying Wave account still exists.
For a long-time user, that can look like an account-loss problem when it is actually an authentication change.
Email, Google and Apple Are Different Sign-In Paths
Wave supports several ways of authenticating an account.
If the account was established with an email and password, use the appropriate email sign-in flow.
If it was created with Google or Apple, using that same provider can be important when trying to locate an existing account.
Wave’s own troubleshooting guidance specifically recommends checking whether the correct Google or Apple account is selected when a user has several accounts with the same provider.
That is a better first diagnostic step than repeatedly creating new Wave accounts.
Why Someone May See an Empty or Different Account
A particularly confusing situation occurs when a user believes all of their Wave information has disappeared.
Wave notes that one possible cause is accidentally choosing Sign Up rather than Sign In, creating or entering a different account instead of returning to the existing one.
Other possibilities include:
using a different email address, selecting the wrong Google or Apple identity, or signing into another Wave account associated with a different business.
A Wave account can also contain several business profiles, so signing into the correct account does not necessarily mean the correct business is currently selected. Wave supports up to 15 business profiles in one account.
Google Sign-In and my.waveapps.com
Some users become suspicious when Google authentication references my.waveapps.com rather than the marketing homepage.
Wave specifically documents my.waveapps.com as the correct Wave destination when connecting a Google login.
That is useful phishing context because account-security decisions should be based on the actual domain, not merely on whether a page uses Wave colors or branding.
A third-party page can visually resemble a login service.
The domain matters more.
Password Resets
If an email-and-password user forgets a password, password recovery should be initiated through Wave’s official login system.
Wave advises users who do not receive the reset email to check junk or spam folders, verify the primary email address, and consider whether the account actually uses Google or Apple authentication instead of a Wave password.
Creating another account is usually not the first troubleshooting step.
MFA and Recovery Keys
Wave supports two-factor authentication as an additional login-security layer.
Wave currently documents verification by text message or authenticator application and provides recovery keys when 2FA is configured. Each recovery key is intended for one-time use.
Those codes and recovery keys should be treated like credentials.
Never send them to:
an independent guide website, an advertiser, someone claiming to “verify” a Wave account through social media, or an unsolicited caller or email sender.
Wave itself advises users not to share verification codes.
Do Not Share One Login Among Several People
Wave recommends against multiple users sharing the same credentials.
Where a business needs several people to work inside Wave, collaborator or additional-user functionality is a safer model because each person can use individual credentials rather than passing around the owner’s password and MFA access.
For standard new Wave businesses, adding additional users is associated with Pro, although certain legacy accounts have different treatment based on their pre-2024 setup.
Employees Using Wave Payroll
An employee invited by an employer using Wave Payroll may also have a Wave account, but that does not make the employee the owner of the employer’s business profile.
Wave provides a Personal profile through which eligible employees can access or update payroll-related information.
In the US, Wave documents employee access to personal information, direct-deposit information, and tax forms. Some payroll details differ between US and Canadian employee accounts; for example, Wave currently states that US employee pay stubs are not available directly through the employee Wave profile and must be provided by the employer.
That distinction can help an employee avoid searching endlessly for an option that is not available in their version of the portal.
When to Contact Wave
Account recovery becomes a support issue when the normal sign-in methods, correct primary email, password reset, and authentication-provider checks do not solve the problem.
Wave’s Help Center and automated Mave support system are available broadly, while live-agent eligibility depends on the products or subscriptions associated with the business.
Wave says approved online-payments users and customers subscribing to services including Payroll, Pro, Receipts, or Wave Advisors can qualify for human support.
For a real account-access problem, use Wave directly.
A third-party publication cannot see which email owns an account, disable MFA, recover a password, or restore business data—and any site claiming that it can should be treated cautiously.