We have a custom Dexterity application (rental system) that uses the SecurePay payment API to talk to our bank for taking credit card payments via our application. This has all worked wonderfully for many years and still works today. SecurePay has it's own dll which I have included as a library within our application so I can use it's methods and objects to process payments and refunds. Because it has it's own dll, I do not need to send XML, etc and it doesn't require a website.
However, our Dexterity version is 7.5 and we also run Dynamics v9 which we are currently upgrading to the current version (GP2016). I have recompiled our application into Dexterity version 14 and completely rewritten our integration from our custom software into Dynamics using eConnect.
Again, all of this works well.
However, when I try to run a credit card transaction, our application crashes out completely and shuts down. I have a test payment form which I can use. As soon as it tries to access the SecurePay.dll, the whole system crashes. I know the dll is registered correctly because my test environment is on a terminal server which also has a copy of our live environment, which I have tested and is still working.
Are there any issues with COM objects in Dexterity 14? Is anyone aware of a way to implement a payment gateway in Dexterity without the need to write a .NET application? It appears that most new gateways assume that you are running a webstore via a browser, which is not what we are doing.
Does anyone know how I can debug this crashing COM object in Dexterity?
Regards,
Mark Fraser
IT Applications Manager