Google Login and License Binding

What this guide covers

Agent for WhatsApp uses two different concepts:

• Google login for account identity
• license binding for plan and feature access

They work together, but they are not the same thing.

Google login

Google login is used to identify the user account behind the extension.

It enables:

• account-level settings
• future sync or ownership logic
• a stable identity for license binding

License binding

License binding connects a valid Agent for WhatsApp license to the signed-in account.

When binding succeeds:

• the extension can unlock plan-based features
• entitlement checks can evaluate both license validity and subscription state
• future logins can recognize the linked license faster

What happens if the purchase email is different

This is a common case. The important rule is:

• Google login proves who is using the extension
• the license itself still has to match the purchase record

If those do not align cleanly, the system may ask the user to bind or re-confirm manually.

What happens when a license expires

Paid features are not controlled by the key alone. The backend also considers subscription state.

Typical outcomes:

• active: full access
• past_due or paused: partial or grace access
• expired or cancelled: paid features are blocked

Best practice

For the lowest-friction setup:

• log in with the Google account you want to keep long term
• bind the license immediately after first login
• avoid switching between multiple Google identities on the same browser profile

If login or binding fails

Go to the troubleshooting guide first. The most useful signals are:

• the visible error message
• whether Google login itself succeeded
• whether the license was previously bound
• whether the license is expired, paused, or cancelled