CreditLine Integration
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!
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:
- 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.
- Recurrent credit card data is accepted, stored and processed through our custom UI, as well.
- 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.