Commerce Software Development: Integration Simplified
by tyler
Using Commerce Toolkit for Applications, we integrated bank card processing services with our point-of-sale application in less than three weeks and with no prior payment integration experience," said MartinJaramillo, president of Buildernet Software. “The Toolkit also made bank card security requirements
easier to navigate."
As many of you are already aware, one of the main products that IP Commerce develops is the Commerce Toolkit for Applications. This toolkit is designed to allow software companies to quickly create secure, commerce-enabled applications. I’m pleased to announce that we have just released a new version of the toolkit.
The new release includes a slew of usability enhancements as well as a tutorial application. These improvements are designed to continue to make commerce development simpler and more intuitive. Using the toolkit, .NET developers are able to code to a single interface that provides multiple commerce services (Credit, Debit, ACH, Gift, Remote Deposit, etc.) and multiple service providers. Consumption of this toolkit reduces time, cost, and complexity to bring commerce solutions to market. I’ve blogged in greater detail about this release here. A few of the most interesting additions, and there are others enumerated at the blog above, are: That link above is to the developer blog on "Commerce Lab." This online resource, launched simultaneously with the toolkit, allows for developers to join a community of other developers building commerce software. It is, in essence, a "one stop shop" for code samples, blogs by myself and the IP Commerce development and architecture team, FAQs, knowledge base, and initiating the certification process. Again, it is all about reducing complexity (even though the toolkit is one of the easiest methods of building commerce applications). If you are interested in the Commerce Toolkit for Applications, there a few resources to peruse: What’s your perspective? Agree? Disagree? Anything to add? Critiques? The comment form is below. . .




