Create and verify your client account

What registration actually creates

A Wavize client account is created with a first name, last name, email address and password. The technical username is generated automatically: there is no additional login identifier to invent or remember.

Manual registration and Google registration lead to the same client area, but their checks differ. Manual registration requires password confirmation and email validation with a six-digit code. Google supplies an already verified address, while Wavize terms must still be accepted before the first account is created.

Key point
Terms are mandatory, their link opens in a new tab, and anti-bot protection may reject a form submitted too quickly or with an expired reCAPTCHA.

Complete the form without triggering a security rejection

Prepare an accessible inbox before starting: it will be used for verification, password recovery and, if enabled later, the second factor.

1. Owner identity

   Enter the first and last name of the person who will administer the account. These values can later be corrected in Settings, unlike a team member email which remains managed by the owner.

2. Unique email address

   Use an address that is not linked to another Wavize account. Recheck the domain after @: a typo prevents code delivery and forces you to start again with the correct address.

3. Confirmed password

   The password must contain at least eight characters and both fields must match. A password manager prevents reuse of a secret already used on another service.

4. Terms and reCAPTCHA

   Open the terms, return to the registration tab, select the checkbox and submit normally. Do not fill any invisible field offered by an autofill tool: it is the anti-bot trap.

Verify the address and enter the correct flow

After manual registration, Wavize opens the session but the account still requires verification. The emailed code is numeric and exactly six digits long.

1. Use the latest email

   Copy the code without spaces. If several messages were requested, use the latest one. Resending is limited for one minute to prevent repeated deliveries.

2. Find a missing email

   Check spam, corporate quarantine and forwarding rules. Add the Wavize sender to allowed contacts before requesting a new code.

3. Understand the redirect

   Successful verification leads to onboarding. Wavize does not create a store or API credentials at this stage: those are handled later according to the selected technology.

Use Google without confusing the button with OAuth configuration

For an existing account, Google only locates the account matching the address. For first registration, Wavize terms must be accepted before redirection.

• Same email, same account

  Choose the exact Google address already registered with Wavize. Another address starts a new flow and does not automatically merge the two accounts.

• 401 or unknown-origin error

  A Google “invalid_client” or “no registered origin” error is not caused by the button design. It means the OAuth client, JavaScript origin or Wavize callback URI is not authorized in Google Cloud.

• Google account already verified

  A successful Google signup marks the address as verified and proceeds directly to onboarding. A local password is not the primary sign-in method until one is set through password recovery.

Checks after creation

Do not consider registration complete until these checks pass.

• Verified address — The code page no longer returns and onboarding opens.
• Consistent language — The interface uses FR or EN according to your choice; it can be changed in Settings.
• No shared secret — Neither Wavize nor support will ask for your password or a complete 2FA code.