CreditLine OCX Integration

From Payment Processing Software Library
Jump to: navigation, search
This article is part of the
Payment Processing Software Library


Get it...

Credit Card Software

Install it...

Upgrade & Migration

Connect to it...

Point Of Sale Integration

Set it up...

Quick Start Guide
Processor Setup


Learn to use it...

Manual & User Guide
Knowledge Base
Frequently Asked Questions
Compliance Guide
Merchant Account Rates
User Interface Guides

Fix it...

Errors & Troubleshooting
Knowledge Base
Corrupted Install Repair

Get Help...

Processor Support Contacts

More Info ...


See also...

911 Software

CreditLine Payment Processing Software Integration. This site can also be reached at

Looking for better rates?   Get a Free Credit Card Processing Cost Comparison!

Important Programming Rules

PLEASE, read every point below as those are the common points of failure in the integrations. Reviewing these pointers may save you significant amount of time in debugging.

  1. Compile for x86 / 32-bit. Do NOT compile for 64-bit even if the program will be used on a 64-bit OS.
  2. Each API object instance needs to call the initialization function (such as clcInit or Init) themselves and get a unique handle to themselves. This handle can not be shared across objects. However, SEE IMPORTANT WARNING BELOW about multiple object creation!
  3. Do NOT create a new object every time you call our API. This will create resource issues. The API object is meant to be created and shared by your application, unless you need to make multiple requests in parallel or creating multiple terminals to do the same - see below.
  4. Each instance can only make one request at a time, but one process can have multiple instances to make multiple requests.
  5. Each instance needs to have a unique client name or terminal name. For example, instance 1 gets TERM001, and instance 2 gets TERM002. The best way to configure this is by device. The length limit is 7. The server monitors the names for duplication and will do it's own name resolution in case of duplicate client names.
  6. The server name should match what's showing on the title bar of the credit server program.
  7. If using the CreditLine Multiple Merchant Account Setup, you must call clcSetMerchantIndex before every Auth, Edit, Sale, Batch and other transaction related calls. The merchant index is reset to 0 on every call completion.
  8. Some environments, such as VB.NET may lose the automation reference if the same API is called twice too quickly. Avoid calling the same API in tight loops - add a reasonable delay if needed.
  9. The dollar amounts have an implied decimal point. e.g. $2.00 should be submitted to our API as 200, not 2.00
  10. Since you will be calling a "black box" DLL, please avoid redundant and inefficient code. Obscure and hard to debug code may significantly extend your debugging efforts.
  11. Do take a look at our sample code.

The server name should match what's showing on the title bar of the credit server program. We had a NETBIOS interface before, so they must match. However, the file API is not that strict. However, it is a good practice to match them, in case we implement multi-servers that monitor the same message directory.

CreditLine OCX Integration

→ Note: we strongly recommend that you use ATL COM Object for Visual Basic integration.

Note: You must run CMD in "Run as Administrator" mode to register the OCX. Right click on the CMD box and select "Run as Administrator" option

If you already integrated with the OCX, please follow this link OCX Integration Guide