Messages from the Edge: API Choice

by Peter on June 17, 2010

Choice and Flexibility are Essential for Software Companies when Selecting a Payments API

Early in the life of a Software Company an important decision is made.  This decision is often based on the expertise and preferences of the company’s first technologist and will impact nearly every other decision the company makes; from the developers they hire, to the tools they use to develop their software.  The decision is what development environment and deployment model to employ.

.NET or Java? PHP or Ruby? SaaS or desktop? These questions dominate early discussions because they define the core technology and approach that a Software Company uses to build and, ultimately, deploy their application into the market.  This decision isn’t something that can be taken lightly.   Selecting the wrong technologies can limit choice and hinder growth and utilizing outdated approaches can inhibit a Software Company’s ability to release competitive features.

The Transitioning Payments Industry

The payments industry is a merchant-centric universe deeply rooted in hardware. Consequently, key players have not given due consideration to Software Companies, – tending to approach relationships with a, “you adjust to meet me” mentality in the form of older machine specifications, lopsided value propositions, disparate processing platforms, limited support and poor documentation, (As a tip, Software Companies are not VARS!)

When it comes down to it, every project has unique requirements and you may need different tools to tackle each job. That’s why choice, and flexibility, in APIs are paramount to meeting the needs of the Software Company.

About the Author:

Peter Osberg is the Sr. Vice President, Business Development & Marketing for IP Commerce. With extensive senior-level experience in highly competitive, multi-sided markets, Peter is a well-established entrepreneur with a proven ability to plan, execute and administer successful sales and business development initiatives.

Stay up to date with the conversation and sign up to follow us via Twitter, RSS or bookmark us. We look forward to hearing your thoughts.

  • http://www.paymentsapi.com/2010/06/payments-101-credit-debit/ What is Credit Debit? — PaymentsAPI.com

    [...] payment acceptance solutions. To integrate credit or debit card processing a software company will choose a payment API to integrate to the Acquiring Bank’s payment processing platform to process the Merchant’s card [...]

  • http://www.paymentsapi.com/2010/06/payment-provider-choice-apis/ Payment & Provider Choice in APIs – Taking Care of Customers — PaymentsAPI.com

    [...] choice. Choice in tenders offered and choice in providers leveraged coupled with choice in their development tools. Regrettably, the concept of “open” is foreign to many traditional participants in the [...]

  • http://www.paymentsapi.com/2010/06/payments-101-what-is-ach/ What is ACH? — PaymentsAPI.com

    [...] How a Paper Check Becomes an Electronic Check ACH (automated clearing house) transactions are electronic check transactions that leverage an existing, inter-bank, network between financial institutions to remit payment. Referencing the image below of a traditional ACH workflow, transactions are initiated from the software the Merchant is using (becoming the originator of the ACH file in the process), routed to the Merchant’s underwriting bank (an ODFI- Originating Depository Financial Institution), then transmitted over the ACH network to the customer’s bank (the RDFI- Receiving Depository Financial Institution). Funds are then released to the Merchant’s Bank. To complicate matters, as more third party senders and receivers of ACH files grow, there is the ability for those services to replace the traditional financial institutions in the workflow. That is why it’s important to work with a partner that understands these nuances when selecting a Payment API. [...]

  • http://www.paymentsapi.com/2010/09/valueadded-services-messages-edge/ The Value of Value-Added Services: Messages from the Edge — PaymentsAPI.com

    [...] recurring theme we see among Software Companies in the market today is that the selection of a payment API is initially driven by the desire to meet immediate business objectives. Furthermore, these [...]

Previous post:

Next post: