I have no problem loading the javascript on the payment page. The problem was that the example does not have an HTML form but rather one is generated. I built the WHMCS without problem and without example code or a demo. There were no 'tools' that were included, which allowed very free reign over what I could do. Blesta seems to have certain 'tools' and pre-set variables which are irrelevant to some merchant gateways and I am unsure if I should/could do away with them or if they are mandatory. Or if indeed there are other tools available I could use rather than hard coding into the processes.pdt file.
Well you see this is why my feeling is that Blesta can be quite rigid. It's not so obvious, and the definitions coined by Blesta do not cover the CarrotPay system. At least not in an absolute clear way. I would say it is more NON-MERCHANT than anything else however.
I know I have to create my own 'code' for this but a form is not what I want/need. Again, there is a function within the processes.pdt file that auto generates a form. I do not need a form, so I am not 100% sure if this is something I can simply remove.
In any case, I have made some good progress and should be able to get it working and tested within a couple days.
Sadly, I must say I have found the documentation completely useless. And I'm not convinced that OOP serves any purpose at the gateway module stage. Just over complicates things in my opinion. Ahh what do I know any way. I'm not a developer.