BILLmanager is integrated with HostMaster, one of the popular domain name registrars.

The integration module supports the following features:

FunctionSupported
Import of domains from the registrar

Transfer of domain names

Change of name servers

Change of domain contact information

Domain name verification

WHOIS data protection management

Information about account balance on the registrar side 

Integration with HostMaster

Integration is set up when a new processing module is added in BILLmanager. This module can be added in Integration → Processing modules → button Add.

  • Step 1 — Product type. Select a product type. Please select Domains for integration with HostMaster.
  • Step 2 — Processing module. Select a processing module. You need to select HostMaster.
  • Step 3 — Integration settings. Enter information for integration with HostMaster.
  • Step 4 — Processing module parameters. Set up the internal parameters of the module.

Settings

  • EPP server — for real orders: sslv3://epp.hostmaster.ua:700. For tests: sslv3://test-epp.hostmaster.ua:700;
  • User — username for access to API HostMaster;
  • Password — user password for access to API HostMaster;
  • Contract number  — the number  of the contract between the registrar and the public domain administrator;
  • Path to the certificate file — path to the security certificate file. The certificate is provided by HostMaster.
  • Path to the key file — path to the security certificate key file. Key is provided by HostMaster;
  • Check domain status via API — check the domain status on the registrar side. Disable to option to run the check via WHOIS. Enable the option to check via the registrar's API;
  • Disable clientHold status check for domains  — the clientHold status is set by the registrar and it means that the domain has expired and has been placed into a hold state;
    • Enabled — when the clientHold status check is disabled a client won't receive the domain expiration notification. Resource records will be active for 29 days. Later a new customer can buy the domain.
    • Disabled — when the clientHold status check is enabled a client will receive the domain suspension notification. The domain will be suspended after the expiration date and will be activated after payment. The owner won't be changed. 

Connection test

On the last step, BILLmanager tries to connect to the registrar with the data you have specified.

If connection ends up with the error: Cannot connect to the processing module, we recommend to check that:

  • connection data is correct.
  • The URL address of the registrar is accessible from the server with BILLmanager.
  • you can execute API calls from the IP address of BILLmanager from your account in the registrar system.
  • The security certificate has not expired.

You can check it by executing the following command:

openssl x509 -noout -text -in  <path to the certificate file>
CODE

The output:

Certificate:
Data:
Version: 3 (0x2)
Serial Number: 6 (0x6)
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=RU, ST=Moscow, L=Moscow, O=Hostmaster Ltd., OU=NOC, CN=hostmaster.net.ua/emailAddress=help@hostmaster.ua
Validity
Not Before: May 16 10:10:10 2016 GMT
Not After : May 16 10:10:10 2017 GMT
Subject: C=RU, ST=Moscow, L=Moscow, O=ISPsystem Ltd, OU=EPP Client, CN=ispsystem.com/emailAddress=admin@ispsystem.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
...
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Key Identifier: 
...
X509v3 Authority Key Identifier: 
...
X509v3 Basic Constraints: 
CA:TRUE
Signature Algorithm: sha1WithRSAEncryption
...
CODE


Not Before — date of certificate issue.

Not After — certificate expiry date.

  • Key corresponds to the certificate.

You can check it by executing the following commands:

openssl x509 -noout -modulus -in <path to certificate file> | openssl md5
openssl rsa -noout -modulus -in <path to certificate key file> | openssl md5
CODE

Each command will return data hash If the values correspond to each other, it means that the key corresponds to the certificate.

Logging

Log of interaction between HostMaster and the billing system is recorded in file '/usr/local/mgr5/var/pmhostmaster.log'.

You can add string 'pmhostmaster.* 9' to file '/usr/local/mgr5/etc/debug.conf' to display more information in the log.