Docs

Configuration & Pilot Validation

Understand scope, native verification and the checks required before enforcement.

Configuration Reference

SettingPurpose
modeemail_pilot for scoped tests; email_required for the reviewed broader policy.
native_email_enabledExplicit switch permitting native email delivery.
email_expected_providerThe configured WHMCS provider identity.
honor_native_email_verificationRecognize existing native owner verification.
enforce_email_login / enforce_email_checkoutSeparate login and checkout enforcement switches.
test_client_ids / email_test_recipients / email_pilot_accountsMatching pilot scope lists and mappings.
email_client_min_idReviewed client boundary for required mode.

Run A Pilot

  1. Use a separate customer session and a test account inside the configured pilot scope.
  2. Request a code and confirm delivery to the intended owner mailbox.
  3. Check a wrong code, an expired code, resend limits and reuse of an already accepted code.
  4. Confirm the correct code completes verification and the intended protected journey is available.
  5. Check an out-of-scope account, a billing-contact mismatch and an already verified native owner.
  6. Repeat relevant checkout, upgrade and integration journeys on the exact target environment.

Change Scope Deliberately

For required mode, the source installation guide calls for a reviewed minimum client ID and empty pilot lists/maps. Policy changes must be synchronized with persisted policy through reviewed reactivation in staging. Do not edit private settings during active enforcement without a recovery plan.

Language

The addon includes English and Indonesian language catalogs. Confirm the rendered language and OTP instructions in the actual client theme rather than changing WHMCS core files.

Need help with this guide? Contact HERZA →

Search Documentation

Search across all products · Esc to close