No Verification Email
- Confirm ordinary WHMCS email delivery works for the test mailbox.
- Check that native delivery is enabled and the expected provider matches the configured provider.
- Check that the test client, recipient and account mappings match in pilot mode.
- Wait for any resend cooldown and inspect sanitized mail-provider errors. Do not repeatedly request new codes.
Code Rejected
Use the current code delivered to the account owner. Codes expire after five minutes and cannot be reused after successful verification. Check whether a resend replaced the expected challenge, whether the session belongs to the owner and whether account email details changed. Never send an OTP to support.
Unexpected Verification Behaviour
An existing native verified owner may already satisfy the configured policy. A billing contact is not the same as the main account owner. Check policy scope, login/checkout switches and the persisted policy before assuming the gate is broken.
Activation Fails
Have the server operator verify the private runtime path, ownership, PHP read permissions, canonical root, SystemURL and pinned deployment values. Correct the configuration rather than weakening the validation checks.
Deactivate Or Recover
Deactivation through Addon Modules stops enforcement and retains verification/audit tables. Back up before changes. Customer upgrade and rollback procedures are not yet fully qualified for this development edition; ask HERZA before migrating existing production verification data.