QuickStart Integration Guide
| This article is part of the
Payment Processing Software Library
|Connect to it...|
|Set it up...|
|Learn to use it...|
|More Info ...|
→ Not finding all the answers? Try Knowledge Base!
- 1 Overview
- 2 CreditLine Client and Server Installation
- 3 Ingegration Options
- 4 Samples Installation and Configuration
- 5 Running The Sample
- 6 Integration Tutorial
- 7 List of API Calls
- 8 Troubleshooting
- 9 Documentation
In this quickstart guide we will help you setup a Sample Demo executable that has the ability to test and troubleshoot CreditLine APIs.
→ Below is a screenshot of extended VB demo in action. There are also simplified demos for other languages.
CreditLine Client and Server Installation
The following samples rely on a known installation structure. If you already installed the software, you might want to uninstall it and follow one of the guides below, to ensure smooth integration experience.
If client and server reside on separate networked machines, please follow CreditLine Networked Client-Server Installation
If client and server reside on the same machine, please follow CreditLine Local Client-Server Installation
There are several integration options for Creditline:
- DLL for C#, C++, et
- Java Wrapper for Java
- OCX for Visual Basic, dotNet, etc
- Encrypted Text Import for manual batch processing.
There are three major integration styles
- → (recommended) Integrator uses CreditLine supplied UI (UI Encapsulation). This is 'clcUI PCI Friendly API Option
- Integrator provides their own UI
- Integrator uses Encrypted Text Import for manual batch processing
Samples Installation and Configuration
The sample directory is located here: CreditLine Integration Samples Repository
→ Note: the following technologies are filed under the legacy directory: VB6, Java, C++, .Net
- Complete the installation steps above.
- Log into the Client
- Download the sample from relevant folder CreditLine Integration Samples Repository, corresponding to the technology that you are using (e.g. C_Sharp for C# or legacyVB6JavaCppDotNet/VB6 for VB6)
- If you copy any files from the sample to CreditLine Client installation path(C:\CLClient\911\api), do not overwrite any files on the client, as what you installed prior will be usually newer.
- Please, read and follow the important steps, outlined in the README file inside the sample directory.
Running The Sample
Every Sample Directory has:
a)Already compiled executable
c)Read me file
- Make sure to read and follow directions in the README file, first
- When you run the sample EXE, make sure, to set the correct path to the server's 911 directory (e.g. c:\CLServer\911\bin or Z:/911, if the server is on another machine and Z is the mapped drive)
- Take a look at the clcapiw.h in c:\CLServer\911\BIN folder for the full list of available functions
- Source code contains all the common API sequences
- The dialogs for different languages may vary.
- The difference between regular calls and CLCUI calls (prefixed with clc), is that clcUI has its own customizable interface to help you avoid handling secure data. For more info see PCI Friendly API
→ Please, see CreditLine Integration Tutorial
List of API Calls
Please see c:\CLServer\911\BIN\CLCAPIW.h
NOTE: OCX/COM/ATL objects simply wrap the standard API DLL, removing "clc" prefix from functions.
- When running the sample application, if you encounter the error “side-by-side…”. Please try to install “vcredist_x86.exe” on your environment.
- For Win7 User, no matter the OS is Win7-32bit or Win7-64bit, we suggest you to enable ‘Is64BitPlatform=YES’ in ClcCs.ini which can be found in C:\911\api.
→ After you have a working sample integration, we suggest that you peruse the CreditLine Integration Guide