Properties   Methods   Events   Configuration Settings  

The CCCharge component is an advanced tool used to authorize credit card transactions in many both Direct Marketing and Retail environments. Where the CCECommerce and CCRetail components make authorizing credit cards easy, the CCCharge component gives the developer finer, more detailed control over every aspect of the transaction.

NOTE: What follows is a very short description of the component interfaces. For more information, please consult the help files that come with the respective package.

Remarks

This component allows for simple, direct, secure connection to the Vital/TSYS SSL gateway through a standard Internet connection. This component can be integrated into web pages or stand-alone Point Of Sale applications. Because all SSL communications are handled inside the component, any application or web page can be deployed without the need for expensive dedicated SSL servers.

While this component is very similar to the CCRetail and CCECommerce components, it is geared towards the advanced user who has an intimate knowledge of the Vital/TSYS message format. There are many more properties to set, and the component does no checking to make sure you are sending valid data or valid combinations of properties. To begin, first Populate the merchant properties with setup information acquired from your member bank or processor. These include properties such as MerchantBankId, MerchantName, etc.

Next, set customer properties using information gathered directly from the customer. For Direct Marketing (Card Not Present) transactions, these include CustomerAddress, CardNumber, CustomerZip, etc. For Retail (Card Present) transactions, set the CardTrack1Data or CardTrack2Data acquired from the Point Of Sale card reader.

Then set the TransactionAmount to the total for this transaction, and set the TransactionNumber.

Finally authorize the transaction with the Authorize method. The status of the authorization request will be returned in ResponseCode and the other response properties.

Once an authorization request is approved, the money in the customer's account is blocked and tagged for the merchant. This transaction must go through the Batch Settlement process in order for the blocked money to be transferred to the merchant account. This is done by passing the DetailAggregate from this component to the CCSettle component. Usually, a Batch Settlement of all authorized transactions is done at the end of each business day.

/n software suggests that as a matter of good business practices all merchants and third parties that store cardholder data should be aware of the Visa Cardholder Information Security Program (CISP) and the MasterCard Site Data Protection (SDP) program. The purpose of these programs is to help protect the integrity of cardholder information via the use of outside-vendor auditing of systems security and server site security.

Method List

Event List

Configuration Settings