Library Overview

The SlimCD Library is the easiest avenue for accessing our payment processes services. Offering the same set of functions in a variety of languages and on a range of platforms, the library allows disparate programmers to access our services in a consistent manner. Request and response class names, entry points, and method names have been standardized as much as possible to allow all programmers the same level of easy access, regardless of their coding preferences or the requirements of the job at hand.

The Library is divided into six groups of methods, which might be thought of as name-spaces, entry points, or parent-classes, depending on your chosen programming language. In this documentation, we will refer to them as entry points.

The standard SlimCD entry points

  • Login library access and site information routines
  • Transact routines for processing payments, handling batches and producing receipts
  • Reports routines to search for individual transactions or summarize daily totals
  • Images functions for uploading and downloading signature and check images
  • Sessions supporting functions for the SlimCD Hosted Pages solution

The SlimCD Library

  • The library is currently available in Javascript which can be used on web pages and in phone/tablet development environments which support JavaScript.
  • It is available as an Apple .a library and as a .jar file which can be included into various java-based solutions, including Android and Blackberry phone projects.
  • We also provide the library as a Microsoft.NET portable class lib assembly DLL, which can be linked into Windows desktop, tablet and smartphone projects.
  • Older Microsoft compliant DLL and COM objects are also available for legacy development.

Extensibility

The list of languages and platforms covered by the SlimCD Library is continually growing, so if we haven’t addressed your favorite yet, let us know. In the meantime, you can always access our payment processing services directly via our web services, which are exposed for access via SOAP and HTTP POST/GET using XML, name-value pairs, and/or JSON.