Difference between revisions of "PCI Friendly API"

Revision as of 16:46, 8 July 2009

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!

This guide is for developers using the DLL

Requirements

These API require version CreditLine version 4.1+

The PA-DSS Exempt API pop up a custom UI for accepting credit card data so that your application does not have to. In addition tokenizing API is used to reference the 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

//CLCUI DLLPREFIX TBOOL DLLENTRY clcUIAuth( HCLOBJ hObj ); DLLPREFIX TBOOL DLLENTRY clcUISale( HCLOBJ hObj ); DLLPREFIX TBOOL DLLENTRY clcUICredit( HCLOBJ hObj ); DLLPREFIX TBOOL DLLENTRY clcUIStoreCard( HCLOBJ hObj ); // store card for monthly charges

We added "clcUI" functions in the client dll. For example, 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 and Custom Processing

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();