Properties   Methods   Events   Configuration Settings  

The CCRetail component is an advanced tool used to authorize credit cards in a Retail environment, where the customer is purchasing products or services in person. This component makes authorizing these types of transactions very easy. Supported Industry Types include retail stores, restaurants, grocery or food stores, Hotels, and Auto Rental businesses.

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.

The CCRetail component makes authorizing Card-Present transactions (where the customer's card is swiped through a card reader) very easy by adding an additional layer of abstraction between the programmer and the protocol. There is no need to deal with raw sockets, SSL handshakes, or data packet formatting. The steps to setting up the component and authorizing a transaction are outlined below:

First, set the merchant properties with setup information acquired from your member bank or processor. For instance:

component.MerchantBankId = "999995" '(BIN number) component.MerchantCategoryCode = "5999" component.MerchantName = "test merchant" component.MerchantNumber = "123456789012" component.MerchantLocation = "Beverly Hills" component.MerchantState = "CA" component.MerchantStoreNumber = "5999" component.MerchantTerminalNumber = "1515" component.MerchantZip = "90210"

Next, set properties that contain details about the transaction. At the minimum, you must set a TransactionAmount, TransactionNumber, and IndustryType.

component.TransactionAmount = "100" component.TransactionNumber = 1 component.IndustryType = itRetail

Finally, submit the transaction by calling one of the three Authorization methods: AuthorizeTrack1, AuthorizeTrack2, and ManualAuthorize. Most card readers are capable of reading both Track1 and Track2 data off of a credit card. If both are present and correctly read, you should default to sending Track1 data. If your card reader cannot read the card at all, you may manually enter the credit card number and expiration date using the ManualAuthorize method. For instance:

component.AuthorizeTrack1("%B4444333322221111^SMITH/JOHN J ^031210100000033301000000008000000?") 'or component.ManualAuthorize("4444333322221111", 3, 2009) 'Card expires in March 2009

When the component receives a response from the Vital/TSYS servers, the result of the authorization will be displayed in several Response properties. The ResponseCode indicates whether the transaction was approved, and the ResponseAVS indicates whether the customer's billing address on file with his credit card company matches the information presented in the CustomerAddress and CustomerZip properties. The remaining properties provide additional information about the transaction.

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 XML aggregate returned from the GetDetailAggregate method 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