Some domain registries need information beyond the ordinary name, address and email fields. Configure those additional fields before selling the affected extension through the WHMCS connector. A field that appears in the cart is useful only if its submitted key and value match the current upstream requirements.
01 Identify the actual required data
- Read the current TLD requirements and, where appropriate, validate a proposed registration through Domain Nexus's requirements API.
- Record each required field's machine key, allowed values, format and conditions. Distinguish the saved value from the customer-facing label.
- Check whether WHMCS already supplies a matching additional domain field for that TLD.
- For self-hosted WHMCS, place necessary overrides in
resources/domains/additionalfields.php. Use the distribution file as a reference without editing it directly. - Use language overrides for readable translated labels while retaining the field identity expected by the integration.
02 Test the submitted payload
The connector's registration and transfer mappers forward WHMCS additionalfields as additional_fields. They do not automatically turn a generic product custom field or a customer note into a registry attribute.
Use a staging order to check which values reach validation. Test the relevant conditional cases, such as an organisation type requiring an additional identifier. A displayed country name may differ from a required two-letter country code; configure the stored value correctly.
For a rejected field, keep the error code and field name, compare the submitted value with the published requirement and correct the form or mapping. Do not fill a required identity field with a placeholder merely to pass local validation.
Common questions
Can I remove a field to bypass a registry requirement?
Removing it from the cart does not remove the upstream requirement. The registration can still fail. Update the form only when the actual requirement has changed.
Will a WHMCS update preserve my changes?
The custom override file is the supported location for self-hosted installations. Keep it in your configuration backup and review it when the relevant TLD rules change.
What if the registry needs documents instead of a simple text value?
Use the approved upstream review process and tell the customer what evidence is required. Do not treat a free-text form field as a secure document workflow.