TransactionType Property

Indicates transaction type for this detail record.

Syntax

 tsysdetailrecord.getTransactionType([callback])
 tsysdetailrecord.setTransactionType( transactionType, [callback])

Possible Values

  0 (dttCardNotPresent), 
  1 (dttCardPresent), 
  2 (dttOffLineCredit), 
  3 (dttForceCardNotPresent), 
  4 (dttForceCardPresent), 
  5 (dttDebitPurchase), 
  6 (dttDebitRefund), 
  8 (dttFoodStampPurchase), 
  9 (dttFoodStampReturn), 
  10 (dttFoodStampVoucher), 
  12 (dttCashBenefitWithdrawal), 
  13 (dttCashBenefitPurchase)

Default Value

Callback

The 'callback' parameter specifies a function which will be called when the operation completes (or an error is encountered). If the 'callback' parameter is not specified, then the method will block and will not return until the operation completes (or an error is encountered).

The callback for the getTransactionType([callback]) method is defined as:

function(err, data){ }

'err' is the error that occurred. If there was no error, then 'err' is 'null'.

'data' is the value returned by the method.

The callback for the setTransactionType([callback]) method is defined as:

function(err){ }

'err' is the error that occurred. If there was no error, then 'err' is 'null'.

'err' has 2 properties which hold detailed information:

err.code
err.message

Remarks

This property indicates the type of transaction that was originally authorized. The following table explains the Transaction Types in detail:


dttCardNotPresent (0)	This indicates a transaction where no physical card was present. Typically this transaction type is used exclusively for eCommerce or Direct Marketing IndustryType, where instead of a track data, AVS data is sent to verify cardholder identity. However, Retail merchants may also use the dttCardNotPresent transaction type from time to time.
dttCardPresent (1)	This indicates a card-present transaction type. The credit card was swiped through a card reader, and Track1 or Track2 data was sent to the processor. This is typical of a retail environment.
dttOffLineCredit (2)	This transaction type is used to credit money back to a cardholder's account. An Offline Credit is not based on a previous transaction, and you may credit any card for any amount without restriction. Simply set the CardNumber to the customer's card number, and then the AuthorizedAmount to "0" and the SettlementAmount to the amount you wish to refund. No track data or AVS data is sent in an offline credit transaction.
dttForceCardNotPresent(3)	This transaction type is used to force a settlement without a previous authorization. This is generally used when an authorization response indicates that the merchant should call the cardholder's bank to verify the funds transfer. The merchant will then be given an authorization code over the phone, with which to settle the transaction.
dttForceCardPresent(4)	Same as above, but for retail (card-present) environments.
dttDebitPurchase (5)	This transaction type is used for debit card sales authorized via the TSYSDebit class.
dttDebitRefund (6)	This transaction type is used for debit card refund transactions authorized via the TSYSDebit class.
dttFoodStampPurchase (8)	This transaction type is used for EBT card Food Stamp purchases authorized via the TSYSBenefit class.
dttFoodStampReturn (9)	This transaction type is used for EBT card Food Stamp returns authorized via the TSYSBenefit class.
dttFoodStampVoucher (10)	This transaction type is used for EBT card Food Stamp vouchers authorized via the TSYSBenefit class.
dttCashBenefitWithdrawal (12)	This transaction type is used for EBT card Cash Benefit withdrawals authorized via the TSYSBenefit class.
dttCashBenefitPurchase (13)	This transaction type is used for EBT card Cash Benefit purchases authorized via the TSYSBenefit class.

Data Type

Integer