Difference between revisions of "CreditLine Integration"

From Payment Processing Software Library
Jump to: navigation, search
Line 1: Line 1:
 
{{CreditLine Header|Integration Guide}}
 
{{CreditLine Header|Integration Guide}}
 +
 +
=Integration Options=
 +
==Integration Languages==
 +
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.
 +
 +
==Integration Styles==
 +
There are three major integration styles
 +
#→ (recommended) Integrator uses CreditLine supplied UI (UI Encapsulation).  This is  '''clcUI PCI Friendly Option''
 +
#Integrator provides their own UI
 +
#Integrator uses Encrypted Text Import for manual batch processing
 +
 +
 
=Quick Start Guide=
 
=Quick Start Guide=
 
  This is the best place to get started with your integration: [[QuickStart Integration Guide]]
 
  This is the best place to get started with your integration: [[QuickStart Integration Guide]]

Revision as of 18:52, 29 August 2016

This article is part of the
Payment Processing Software Library

Categories

Get it...

Credit Card Software
Download

Install it...

Installation
Upgrade & Migration

Connect to it...

Point Of Sale Integration

Set it up...

Quick Start Guide
Setup
Processor Setup

Licensing

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...

Contact
Processor Support Contacts

More Info ...

Glossary
Articles

See also...

911 Software
Help

CreditLine Payment Processing Software Integration Guide. This site can also be reached at http://docs.911software.com

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

Integration Options

Integration Languages

There are several integration options for Creditline:

  1. DLL for C#, C++, et
  2. Java Wrapper for Java
  3. OCX for Visual Basic, dotNet, etc
  4. Encrypted Text Import for manual batch processing.

Integration Styles

There are three major integration styles

  1. → (recommended) Integrator uses CreditLine supplied UI (UI Encapsulation). This is 'clcUI PCI Friendly Option
  2. Integrator provides their own UI
  3. Integrator uses Encrypted Text Import for manual batch processing


Quick Start Guide

This is the best place to get started with your integration: QuickStart Integration Guide

PA-DSS Friendly Code and Security Considerations

PCI Council PA-DSS and other security standards place stringent requirements on Point Of Sale software. You have an option to make your code "PCI Friendly" by using both secure tokens and/or external payment info input encapsulation.

There are three ways, in which CreditLine can help your application eliminate exposure to the payment info:

  1. Our application pops up a custom UI for accepting and processing credit cards, debit cards or gift cards, so that your application does not have to.
    All aspects of the UI can be customized
  2. Recurrent credit card data is accepted, stored and processed through our custom UI, as well.
  3. Tokenization UI API is used to reference credit card data that is stored and encrypted within CreditLine, instead of your POS.

This way your application can claim that no credit card data is being stored or processed.

  • Important Notice: This program was called "PCI Exempt". We changed the name to reflect the new policies of the PCI Council. PCI Exempt used to be a convenient term that Point Of Sale developers use to refer to the practice of tokenization and external UI encapsulation. 911 Software does not have the authority to exempt any vendor from PCI requirements. Please, contact your independent PCI auditor for rules applicable to your situation.

For more info, please see PCI Friendly API.