This is an XML Gateway question, rather than an API question. They have their own forum here: http://xmlforum.aws.chdev.org/
That said… I think a “fatal” error indicates an envelope/xml/validation type error which, in this case would be that your xml has:
<NameAuthorisation>true<NameAuthorisation>
In it and as such the gateway is expecting the relevant documentation to be attatched as:
<Category>SUPPNAMEAUTH</Category>
And the fact that it’s not there is generating the error.
If it has been manually rejected because it needs some kind of authorisation for the name you should be able to find out what is needed by looking on these lists:
No prob, happy to help! I just went and checked some of our old rejections and am pretty sure if it was the manual thing it wouldn’t be a “fatal” error and the rejection reason would be a lot more comprehensive with regard to what was needed for authorisation.
An example:
The use of ‘Licensing’ in your proposed name implies a connection with a body that protects intellectual property rights or carries out licensing functions under the Licensing Act 2003, such as the licensing of alcohol sales, entertainment or clubs.