...
Companies can be registered with greenID via Web Services in a similar manner to individuals.
| Table of Contents |
|---|
Overview
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.
...
POSTing to the start page
- returnUrl
- cancelUrl
- customerId
- timeoutUrl
- exceptionUrl
- clientId
The sources
Security Options
Unlike the individual registration Web Service methods, the company registration Web Service methods only use Password authentication.
...
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.
If the clientType is "SMSF" the organisation is registered as a self managed super fund and no non-consent checks are performed (we currently don't have a non-consent version of the super fund lookup). The user-centric SMSF source must be used, and so a POST must be done to the start page as below.
POSTing to the start page
- returnUrl
- cancelUrl
- customerId
- timeoutUrl
- exceptionUrl
- clientId