I apologize for the problems you are encountering. As you may know, we prefer to not encode files so that our customers may make changes to their communities in situations where hooks or apps won't do what's needed. However with Nexus, the files need to be encoded for security purposes. On the company forums, someone else may have developed an understanding of how to develop a custom gateway and may be willing to help you with what you need. Also, if you post in the Nexus Feedback forum about what you need in the documentation, that will let the developer know what information you need so it can be looked into.
James D. Kessler
Invision Power Services, Inc.
I was asked to post this by support.
The documentation does not show what is expected or explain what fields need to be passed back and forth between the coreGateway. It keeps saying look at the code which is encoded. So it can't be done.
WHat is needed is a real explanation of what the program expects to receive as input and what you get for input.
A sample code showing the interface (like in the Subscriptions package) would be very useful.
Please update the documentation.