TSYSECommerce Bean

Properties   Methods   Events   Configuration Settings   Errors  

The TSYSECommerce component is an advanced tool used to authorize credit cards in both Mail Order (Direct Marketing) and eCommerce environments, where the customer is ordering products or services via the telephone or Internet. This component makes authorizing these types of transactions very easy.

Syntax

InPayDirect.Tsysecommerce

Remarks

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

The TSYSECommerce component makes authorizing Card-Not-Present Mail Order and E-Commerce transactions very easy by adding an additional layer of abstraction between the programmer and the protocol. There is no need to deal with raw sockets, TLS/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.MerchantServiceNumber = "800-1234567"
  component.MerchantState = "CA"
  component.MerchantStoreNumber = "5999"
  component.MerchantTerminalNumber = "1515"
  component.MerchantZip = "90210"

Then, set the customer's credit card information, as well as his address and zip code (the address and zip code will be checked by the Vital/TSYS servers to make sure it matches the customer's billing address).

  component.CardNumber = "4444333322221111"
  component.CardExpMonth = 1
  component.CardExpYear = 2009
  component.CardCVVData = "999"
  component.CustomerAddress = "8320 South Hardy Dr."
  component.CustomerZip = "85284"  

Next, set properties that contain details about the transaction. At the minimum, you must set a TransactionAmount and TransactionNumber. However, you may also set the TransactionType if you are doing a Mail Order or Recurring transaction.

  component.TransactionAmount = "100"
  component.TransactionNumber = 1
  component.TransactionType = ttECommerce

Finally, submit the transaction by calling the Authorize method. The component receives a response from the Vital/TSYS servers, the result of the authorization will be displayed in several Response properties. The Code indicates whether the transaction was approved, and the AVSResult 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 TSYSSettle component. Usually, a Batch Settlement of all authorized transactions is done at the end of each business day.

Note: The TSYSECommerce component can be used to pass 3D-Secure authentication data in an authorization to achieve a better interchange rate. To send this data, the ECI, XID, and CAVV configuration variables must be set before calling Authorize. The CAVV authentication result code will be returned in the ResponseCAVV configuration setting.

Further Note: When sending e-commerce transactions, you must send a PurchaseIdentifier (sometimes referred to as Invoice Number) in the settlement. This can be done via the PurchaseIdentifier property of the TSYSDetailRecord component. Failure to set a PurchaseIdentifier for the e-commerce Industry Type may result in a CPS downgrade when the transaction is settled, and can cause higher interchange rates.