This last week I had a client come to me with another interesting situation that needed a solution. My client had previously sought out a cost effective and easy to administer 3rd party solution for taking checking account payments while having the ability to set up automatic recurring billing. They found Transaction Express by TransFirst.
Transaction Express posed a new challenge for me because I had not previously worked with them, nor (obviously) integrating their solution into other software. My client has a homegrown CMS/POS system, part of which is used to sell subscriptions for their services - hence the need for recurring billing.
It took a little digging and the help of Transaction Express' customer service to find the API's documentation, but i was pleasantly surprised when I received it. The docs were thorough, detailed and gave SOAP envelope examples that allow me to rapidly build up my library. Plus the doc's error and troubleshooting information help cut down on email tag with their support team which I'm sure they appreciate as well. When I did have to contact their support team, they were fast and provided accurate answers.
What I did find slightly frustrating was the docs and the support team did not have any examples, documentation or specific support for integrating with any .NET language, only PHP. While they do have a WSDL so I could pull all the objects into Visual Studio, it wasn't exactly self evident how things went together because the objects themselves aren't documented within the WSDL.
After some playing around, (and a totally unrelated, but ultimately useful, .NET example from Transaction Express' tech support) I was able piece together how to fire the Request object. It basically came down to this:
MerchantWebServicesPortTypeClient client =
new MerchantWebServicesPortTypeClient();
Merc m = new Merc();
//set merc properties
Contact contact = new Contact();
//set contact properties
AchEcheck ach = new AchEcheck();
//set ach properties
SendTranRequest request = new SendTranRequest();
//add above objects to request
//finally, trigger call to API
SendTranResponse response = new SendTranResponse();
response = ((MerchantWebServicesPortType)(client)).SendTran(request);
Obviously this is a simplification of the actual code needed to use the Transaction Express API. I found the tricky part was trying to find out that the PortTypeClient needed to be cast as a PortType. Ultimately I was able to figure it out because the PortTypeClient was declared as an interface.
If you'd like to know more about how to integrate Transaction Express by TransFirst into your .NET application, please contact me for more information. I'd be happy to share any other useful tips I may pick up along the way. Or if you need assistance with the actual integration, please contact me with your project details and I can provide you with a quote.
Happy Coding,
Ted Krapf
Click here for the full code, please donate if it was helpful!