Difference between revisions of "PCI Friendly API"
(→Recurrent Charges and Custom Processing) |
(→Requirements) |
||
Line 5: | Line 5: | ||
These API require version CreditLine version 4.1+ | These API require version CreditLine version 4.1+ | ||
− | + | ==Descripption== | |
+ | There are three ways, in which CreditLine can help your application eliminate exposure to the credit card info: | ||
+ | # Our application pops up a custom UI for accepting and processing credit 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 store and reference credit card data that will be stored in CreditLine, instead of your POS. | ||
+ | |||
+ | This way your application can claim that no credit card data is being stored or processed. | ||
==Encapsulation UI== | ==Encapsulation UI== |
Revision as of 17:16, 8 July 2009
This article is part of the Payment Processing Software Library |
|
Get it... | |
Install it... | |
Connect to it... | |
Set it up... | |
Learn to use it... | |
→ Manual & User Guide | |
Fix it... | |
→ Errors & Troubleshooting | |
Get Help... | |
More Info ... | |
See also... | |
CreditLine Payment Processing Software PA-DSS Exempt API. This site can also be reached at http://docs.911software.com
→ Looking for better rates? Get a Free Credit Card Processing Cost Comparison!
Contents
This guide is for developers using the DLL
Requirements
These API require version CreditLine version 4.1+
Descripption
There are three ways, in which CreditLine can help your application eliminate exposure to the credit card info:
- Our application pops up a custom UI for accepting and processing credit 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 store and reference credit card data that will be stored in CreditLine, instead of your POS.
This way your application can claim that no credit card data is being stored or processed.
Encapsulation UI
- clcUIAuth
- pop up UI, get cc data and process a auth
ex.clcSetAmount();
clcUISale(); - clcUISale
- pop up UI, get cc data and process a sale
- clcUICredit
- pop up UI, get cc data and process a credit
- clcUIStoreCard( HCLOBJ hObj )
- store card for monthly charges
We added "clcUI" functions in the client dll. For example, you can use clcUISale instead of clcSale.
So instead of doing this:
clcSetAccountNumber(); clcSetAmount(); clcSale();
You can do this:
clcSetAmount(); clcUISale();
A screen is going to pop up and prompt the user to swipe the card.
This way, the POS application does not have to deal with the credit card data.
Recurrent Charges
To store the card for monthly charges, call clcUIStoreCard. This function also pops up a screen for card number input. It then stores the card on 911 CreditLine Server and returns a tag (token) to the POS application.
Then this tag can be used in place of the actual card number:
clcSetTag(); clcSetAmount(); clcSale();
CreditLine offers tokenization of payment info to make your application "PCI Friendly"
Secure Storage API
These are additional non-UI storage API that can be used in your POS.
Storing Info
- clcSetAccountNum → Sets account number for storage (call before clcStoreCard).
- clcSetExpDate → Sets (format: MMYY). Set the expiration date for storage before calling clcStoreCard.
- clcSesSetValue → Use with CLCKEY_CUSTOMERNAME, CLCKEY_CUSTOMERNUMBER, CLCKEY_CUSTOMERZIPCODE to set the customer info for storage before calling clcStoreCard.
- clcStoreCard → Stores card info in storage. Sets a tag to be pased extracted by clcGetTag() and passed to clcLoadCard for retrieval. Leave the second parameter as "" unless you want to set a custom tag.
- clcGetTag → Retrieves the tag set by clcStoreCard
Loading Info
- clcLoadCard → Loads card info from storage. Accepts the tag returned by clcGetTag and set by clcStoreCard.
- clcGetAccountNum → Gets account number from storage (call after clcLoadCard).
- clcGetExpDate → (format: MMYY). Get the expiration date from storage (call after clcLoadCard).
- clcSesGetValue → Use with CLCKEY_CUSTOMERNAME, CLCKEY_CUSTOMERNUMBER, CLCKEY_CUSTOMERZIPCODE to get customer info from storage after calling clcLoadCard.
Deleting Info
- clcDeleteCard → Deletes card info from storage. Accepts the tag returned by clcGetTag and set by clcStoreCard.