Companies can be registered with greenID via Web Services in a similar manner to individuals.

Security Options

Unlike the individual registration Web Service methods, the company registration Web Service methods only use Password authentication.

WSDL Locations

The test environment WSDLs for the company registration methods described below are at the following locations:

https://test-au.vixverify.com/Registrations-Registrations/CompanyVerificationServicesPassword?wsdl

The production environment WSDLs for the company registration methods described below are at the following locations:

https://au.vixverify.com/Registrations-Registrations/CompanyVerificationServicesPassword?wsdl 

Methods

There are two methods that can be used to register a company with greenID:

1. registerCompany
2. registerCompanySimpleAddress

One of these methods must be called as the first step when verification of a company is required. This method establishes a registration with GreenID that can be used as the basis of further checks.

The registerCompany Method

Method Signature

public RichVerificationResult registerCompany (
 String customerId,
     String password,
     String clientId,
     String ruleId,
     String clientType,
     String abn,
     String acn,
     String companyName,
     String state,
     String postcode,
     String email,
     String phone,
     String fax,
     NameValuePair[] extraData)

Parameters

The registerCompanySimpleAddress Method

Method Signature

public RichVerificationResult registerCompany (
 String customerId,
     String password,
     String clientId,
     String ruleId,
     String clientType,
     String abn,
     String acn,
     String companyName,
     SimpleAddress address,
     String email,
     String phone,
     String fax,
     NameValuePair[] extraData)

Parameters

The SimpleAddress Type

Return Value

The return values of the functions are both the same: both methods will return a RichVerificationResult object.  This object is described in detail in the section on Outcome Notification, so the reader is referred to that section for more detail.  In summary, the return value will indicate the current status of the company's registration, and the outcome of any checks that were performed automatically.

Faults

Either method may raise a FaultDetails, inside which can be the following codes:

• SystemFault

About the clientType and how it affects which sources are checked

If you register with a clientType set to anything other than "SMSF" (or alternately don't send down a clientType) then the organisation is treated as a company and two "non-consent" checks are performed.  The entity is checked against the ASIC and ABR sources.  If no match is found via these non-consent sources, then a POST to the start page can be performed to allow the details to be tweaked to achieve a match via the user-centric versions of the ASIC and ABR sources.