Difference between revisions of "CreditLine Integration"
(→Integration Styles) |
(→Quick Start Guide) |
||
Line 21: | Line 21: | ||
=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:<br><center> [[QuickStart Integration Guide]]</center> |
[[Category:CreditLine Integration|Integration Guides]] | [[Category:CreditLine Integration|Integration Guides]] |
Revision as of 18:59, 29 August 2016
This article is part of the Payment Processing Software Library |
|
Get it... | |
Install it... | |
Connect to it... | |
→ Point Of Sale Integration | |
Set it up... | |
Learn to use it... | |
→ Manual & User Guide | |
Fix it... | |
→ Errors & Troubleshooting | |
Get Help... | |
More Info ... | |
See also... | |
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!
Contents
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 (see below)
- Integrator provides their own UI
- Integrator uses Encrypted Text Import for manual batch processing
Tokenization and PCI Friendly UI Encapsulation (clcUI)
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.
For more info, please see PCI Friendly API.