HISE documentation
HISE Claim Email Verification
Pending claims, owner proof, completion, and safe recovery.
Why verification is required
Verification proves access to the identity used by a supported serial claim. A pending claim is not permission to unlock the product. A known owner and a new unclaimed serial can require different customer actions.
An unknown serial or owner mismatch should not produce a new ownership claim merely by collecting an email address. Existing accounts use the supported login/recovery path.
SoundSync
Complete and return
-
Request the supported verification
Use the package's claim/activation flow and customer identity.
-
Check the message
Verify that the link corresponds to the intended product/claim, without publishing the token.
-
Complete the verification
Follow the supported confirmation page/code step.
-
Return to the plugin
Refresh claim status or continue activation using the current returned state.
-
Handle expiry or mismatch
Use supported resend/recovery behavior; do not repeatedly create identities or ignore a confirmed denial.
Support safely
Report the claim stage, product/package version, and safe error code. Redact verification URLs, serials, private email addresses, and tokens from screenshots. Transactional verification mail is distinct from permission to add the customer to marketing.
